DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>, web@dpdk.org
Subject: Re: [dpdk-web] [PATCH] Added CI community meetings page
Date: Wed, 27 May 2020 14:56:35 +0200	[thread overview]
Message-ID: <3489324.a8K9Ouf8lv@thomas> (raw)
In-Reply-To: <CAOE1vsNitQ15H1ZY9t7_ebDCx6wVm=HswfU=u_hf6T8piB8KLw@mail.gmail.com>

27/05/2020 14:27, Lincoln Lavoie:
> Hi Thomas, comments below.
> 
> On Tue, May 26, 2020 at 5:22 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > Hi,
> >
> > Thanks for starting a new web page for archiving CI meetings minutes.
> > I have few comments below.
> >
> >
> > 26/05/2020 19:35, lylavoie@iol.unh.edu:
> > > --- /dev/null
> > > +++ b/content/testing/ci_meetings.md
> >
> > What about "testing/meetings.md"?
> >
> 
> See next comment.
> 
> >
> >
> > > @@ -0,0 +1,20 @@
> > > ++++
> > > +title = "Community CI Minutes"
> > > ++++
> >
> > I feel "Community" refers to "Community Lab".
> > Do we agree that the scope of these meetings are about the CI
> > of the DPDK project in general?
> > If so, I think "CI Meeting Minutes" would be a good header.
> > For the title of the page, appearing in the menu under "Testing",
> > I think "Meetings" would be short and good enough.
> >
> 
> I was trying to differentiate the page from the tech board meetings page,
> which is called just "Minutes."  My opinion is, it's bad form to have a
> bunch of pages named the same title, as their context is then taken only
> from their location in the site map and not the page itself.

The "title" appears in the menu in the context of its parent "Testing".
It also appears at the top of the page as a kind of image,
followed by the headline which can be different and longer, like "CI Meetings".


> > > +
> > > +## Community CI Meeting Minutes
> > > +
> > > +### Schedule & Joining
> > > +Calls are currently biweekly, on Tuesday, at 9am Eastern USA Time.  To
> >
> > Please prefer UTC time.
> >
> 
> I can make this change, but with UTC time, the meeting time will "change"
> multiple times for different groups of people, in Europe and North America,
> as UTC never changes for daylight savings time.  I've seen this cause
> conflicts and issues over the several weeks in other groups.  If we
> "anchor" to a timezone that does at least observe UTC, the meeting time
> does "move" for some, but then "moves back" when their zone also changes
> to/from daylight savings.

I don't know what is best.
In techboard we chose UTC.


> > > +join the calls, your company must be a gold or silver level DPDK
> > > +[member](//www.dpdk.org/ecosystem/#members).  Reach out on the
> > > +[ci@dpdk.org](mailto:ci@dpdk.org) to be added to the meeting calendar
> > > +invite.
> >
> > Trishan, do you confirm this exact rule, regarding Linux Foundation
> > membership?
> >
> > > +
> > > +### Minutes
> > > +
> > > +Meeting minutes are sent to the mailing list following each meeting.
> > Links
> > > +to the message in the email archieve are listed below.
> >
> > s/archieve/archive/
> >
> > > +
> > > +* [2020-05-03](//mails.dpdk.org/archives/ci/2020-May/000630.html)
> > > +* [2020-05-19](//mails.dpdk.org/archives/ci/2020-May/000643.html)
> >
> > I propose a reverse chronological order so the most recent one is at the
> > top.
> >
> 
> No problem, I can make this change.




  reply	other threads:[~2020-05-27 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 17:35 lylavoie
2020-05-26 21:22 ` Thomas Monjalon
2020-05-26 21:48   ` Trishan de Lanerolle
2020-05-27 12:27   ` Lincoln Lavoie
2020-05-27 12:56     ` Thomas Monjalon [this message]
2020-05-27 15:29       ` Trishan de Lanerolle
2020-06-02 17:09 ` [dpdk-web] [PATCH v2] [PATCH v2] " lylavoie
2020-06-02 20:11   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3489324.a8K9Ouf8lv@thomas \
    --to=thomas@monjalon.net \
    --cc=lylavoie@iol.unh.edu \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).