DPDK website maintenance
 help / color / mirror / Atom feed
From: lylavoie@iol.unh.edu
To: web@dpdk.org
Cc: thomas@monjalon.net, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: [dpdk-web] [PATCH v2] [PATCH v2] Added CI community meetings page
Date: Tue,  2 Jun 2020 13:09:45 -0400	[thread overview]
Message-ID: <20200602170945.13667-1-lylavoie@iol.unh.edu> (raw)
In-Reply-To: <20200526173553.3834-1-lylavoie@iol.unh.edu>

From: Lincoln Lavoie <lylavoie@iol.unh.edu>

* Updated to UTC timezone for call
* Updated participation requirements for the call
* Cleaned up the file and page names
* Added link to June 2 minutes

Signed-off-by: Lincoln Lavoie <lylavoie@iol.unh.edu>
---
 content/testing/ci_meetings.md | 20 --------------------
 content/testing/meetings.md    | 21 +++++++++++++++++++++
 2 files changed, 21 insertions(+), 20 deletions(-)
 delete mode 100644 content/testing/ci_meetings.md
 create mode 100644 content/testing/meetings.md

diff --git a/content/testing/ci_meetings.md b/content/testing/ci_meetings.md
deleted file mode 100644
index 91cf7da..0000000
--- a/content/testing/ci_meetings.md
+++ /dev/null
@@ -1,20 +0,0 @@
-+++
-title = "Community CI Minutes"
-+++
-
-## Community CI Meeting Minutes
-
-### Schedule & Joining
-Calls are currently biweekly, on Tuesday, at 9am Eastern USA Time.  To 
-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.
-
-### Minutes
-
-Meeting minutes are sent to the mailing list following each meeting. Links
-to the message in the email archieve are listed below.
-
-* [2020-05-03](//mails.dpdk.org/archives/ci/2020-May/000630.html)
-* [2020-05-19](//mails.dpdk.org/archives/ci/2020-May/000643.html)
\ No newline at end of file
diff --git a/content/testing/meetings.md b/content/testing/meetings.md
new file mode 100644
index 0000000..1f107c4
--- /dev/null
+++ b/content/testing/meetings.md
@@ -0,0 +1,21 @@
++++
+title = "Minutes"
++++
+
+## Community CI Meetings
+
+### Schedule & Joining
+Calls are currently biweekly, on Tuesday, at [1pm UTC](//mytime.io/1pm/UTC).  
+The calls and discussions are open to all in the community.  Reach out on the 
+[ci@dpdk.org](mailto:ci@dpdk.org) to be added to the meeting calendar 
+invite.  To submit hardware into the Community CI Lab, your company must 
+be a gold or silver level DPDK [member](//www.dpdk.org/ecosystem/#members).
+
+### Minutes
+
+Meeting minutes are sent to the mailing list following each meeting. Links
+to the message in the email archive are listed below.
+
+* [2020-06-02](//mails.dpdk.org/archives/ci/2020-June/000650.html)
+* [2020-05-19](//mails.dpdk.org/archives/ci/2020-May/000643.html)
+* [2020-05-03](//mails.dpdk.org/archives/ci/2020-May/000630.html)
-- 
2.26.2


  parent reply	other threads:[~2020-06-02 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 17:35 [dpdk-web] [PATCH] " 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
2020-05-27 15:29       ` Trishan de Lanerolle
2020-06-02 17:09 ` lylavoie [this message]
2020-06-02 20:11   ` [dpdk-web] [PATCH v2] [PATCH v2] " 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=20200602170945.13667-1-lylavoie@iol.unh.edu \
    --to=lylavoie@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --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).