DPDK community structure changes
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: moving@dpdk.org
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, March 7th
Date: Wed, 08 Mar 2017 15:45:01 +0100	[thread overview]
Message-ID: <2433082.cJ3p5dltz2@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA72319828@IRSMSX108.ger.corp.intel.com>

2017-03-08 13:44, O'Driscoll, Tim:
> Adding the charter to the website:
> - Thomas proposed on the mailing list that we post the charter on the website and manage changes in git (http://dpdk.org/ml/archives/moving/2017-March/000191.html). Agreed that this is a good idea.
> - We need to agree which mailing list should be used for future discussion on the charter once it's baselined. Agreed that the best approach is to rename moving@dpdk.org to charter@dpdk.org when the project is launched, and use it for any future discussion. The archives will still contain the history of discussions on moving to LF.

I think any changes in the charter or in the structure could be discussed on moving@dpdk.org.
Why renaming?

> - After it's baselined, proposed changes to the charter should be made on the charter@dpdk.org list. They can then be discussed in public on the list, and will also be discussed and voted on at a governing board meeting. A member of the board will indicate on the list if the board approves the proposed change.

The changes must also be posted to web@dpdk.org.

> - We can also set up a private mailing list for the governing board once its members are known, similar to techboard@dpdk.org.
> Membership:
> - Mike is working on the membership agreement and expects to have a draft in the next day or two. He'll distribute this as soon as it's available.

Is this agreement going to change anything in the charter?
If not, I'm going to send a patch for charter integration in the web site.

  reply	other threads:[~2017-03-08 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 13:44 O'Driscoll, Tim
2017-03-08 14:45 ` Thomas Monjalon [this message]
2017-03-08 16:37   ` O'Driscoll, Tim

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:

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

  git send-email \
    --in-reply-to=2433082.cJ3p5dltz2@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=moving@dpdk.org \


* 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).