DPDK community structure changes
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	Dave Neary <dneary@redhat.com>
Cc: moving@dpdk.org
Subject: Re: [dpdk-moving] Reminder on Today's Meeting and Updated Charter
Date: Thu, 24 Nov 2016 14:26:43 +0100	[thread overview]
Message-ID: <1540534.G53vByIeVs@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67623D9E@IRSMSX108.ger.corp.intel.com>

2016-11-24 12:46, O'Driscoll, Tim:
> From: Dave Neary [mailto:dneary@redhat.com]
> > Fourthly, do we need to make a distinction between DPDK the software
> > project and the DPDK Project, the entity which will come into being
> > under the LF? I ask, because participation in the DPDK software project
> > is clearly not to be limited to paying members, while participation in
> > the DPDK Project under the LF is limited to paying companies, for the
> > most part.
> 
> The aim was that this was clear from point 4.a in the Membership section. At last week's meeting somebody (Matt I think) suggested adding a membership category of Contributor to make this clearer, but most people felt this was over-kill.
> 
> Do you think this is clear from point 4.a, or do you still think something further is required?

I think the membership section must be part of the governing board section.
So it makes clear that we are talking about members of the governing board.

  reply	other threads:[~2016-11-24 13:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 11:08 O'Driscoll, Tim
2016-11-22 14:47 ` Vincent JARDIN
2016-11-23 22:26 ` Dave Neary
2016-11-24 12:46   ` O'Driscoll, Tim
2016-11-24 13:26     ` Thomas Monjalon [this message]
2016-11-24 14:16       ` Matt Spencer
2016-11-24 17:27         ` O'Driscoll, Tim
2016-11-24 18:07           ` Vincent Jardin
2016-11-24 18:20             ` Ed Warnicke
2016-11-24 19:05               ` Vincent Jardin
2016-11-24 18:13           ` Ed Warnicke
2016-11-29 13:20         ` Francois Ozog
2016-11-29 13:50           ` Thomas Monjalon
2016-11-29 14:25             ` Francois Ozog
2016-11-29 14:50               ` Vincent JARDIN

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=1540534.G53vByIeVs@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dneary@redhat.com \
    --cc=moving@dpdk.org \
    --cc=tim.odriscoll@intel.com \
    /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).