DPDK website maintenance
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, tdelanerolle@linuxfoundation.org
Cc: web@dpdk.org, govboard@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-web] [PATCH 2/3] update Technical Board responsibility wording
Date: Wed, 18 Oct 2017 11:40:39 -0400	[thread overview]
Message-ID: <5b844cbe-19ed-df6e-4955-3ed5a3c88ab4@redhat.com> (raw)
In-Reply-To: <20171018150431.17200-3-thomas@monjalon.net>

Hi,

I had a concern about this one expressed to me, which I sent to the
govboard list and did not see any response - "shall be" is more rigorous
language than "is" - changing this does not improve the document at all,
and creates potential legal loopholes/confusion.

I would prefer this specific change not to be made.

Thanks,
Dave.

On 10/18/2017 11:04 AM, Thomas Monjalon wrote:
> Linux Foundation asks to replace "shall" by "is"
> for technical decision responsibility.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  about/charter.html | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/about/charter.html b/about/charter.html
> index 7308384..235ebba 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.).
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

  parent reply	other threads:[~2017-10-18 15:40 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 [this message]
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         ` [dpdk-web] [PATCH v2 2/4] update Technical " Thomas Monjalon
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=5b844cbe-19ed-df6e-4955-3ed5a3c88ab4@redhat.com \
    --to=dneary@redhat.com \
    --cc=govboard@dpdk.org \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=techboard@dpdk.org \
    --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).