DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: tdelanerolle@linuxfoundation.org
Cc: web@dpdk.org, govboard@dpdk.org, techboard@dpdk.org
Subject: [dpdk-web] [PATCH v2 2/4] update Technical Board responsibilities
Date: Tue, 28 Nov 2017 19:39:15 +0100	[thread overview]
Message-ID: <20171128183917.17742-3-thomas@monjalon.net> (raw)
In-Reply-To: <20171128183917.17742-1-thomas@monjalon.net>

The Governing Board asks to replace "shall" by "is"
for technical decision responsibility.

It is also asked to state that the Charter prevail on Technical Board
self description.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 about/charter.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/about/charter.html b/about/charter.html
index 3af8309..b73cda8 100644
--- a/about/charter.html
+++ b/about/charter.html
@@ -211,7 +211,7 @@
 
 <h4 id="techscope">Scope</h4>
 <p>
-	The Technical Board shall be responsible technical decision making
+	The Technical Board is responsible for technical decision making
 	for the DPDK project.
 	Its scope does not include the other sub-projects
 	hosted on dpdk.org (Pktgen, SPP etc.).
@@ -282,6 +282,7 @@
 	<li>
 		The composition of the Technical Board is documented at
 		<a href="/about/techboard#members">dpdk.org/about/techboard#members</a>.
+		In the case of a conflict, the terms of this Charter prevail.
 	<li>
 		To be added to or removed from the Technical Board:
 	<ol>
-- 
2.15.0

  parent reply	other threads:[~2017-11-28 18:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 19:16 [dpdk-web] Updated charter for upload Trishan de Lanerolle
2017-10-17 20:24 ` Thomas Monjalon
2017-10-17 22:23   ` Trishan de Lanerolle
2017-10-18 15:04     ` [dpdk-web] [PATCH 0/3] update charter Thomas Monjalon
2017-10-18 15:04       ` [dpdk-web] [PATCH 1/3] update Governing Board responsibilities Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:04       ` [dpdk-web] [PATCH 2/3] update Technical Board responsibility wording Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:40         ` Dave Neary
2017-10-18 15:41           ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:04       ` [dpdk-web] [PATCH 3/3] update license policy wording Thomas Monjalon
2017-10-18 15:43         ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:47         ` [dpdk-web] " Thomas Monjalon
2017-11-28 18:39       ` [dpdk-web] [PATCH v2 0/4] update charter Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 1/4] update Governing Board responsibilities Thomas Monjalon
2017-11-28 18:39         ` Thomas Monjalon [this message]
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 3/4] update license policy wording Thomas Monjalon
2017-11-29  5:34           ` [dpdk-web] [dpdk-govboard] " Hemant Agrawal
2017-11-29  9:25             ` Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 4/4] remove references to Xen dom0 files Thomas Monjalon
2017-12-11 22:09         ` [dpdk-web] [dpdk-techboard] [PATCH v2 0/4] update charter 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=20171128183917.17742-3-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=govboard@dpdk.org \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=techboard@dpdk.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).