DPDK community structure changes
 help / color / mirror / Atom feed
From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Dave Neary <dneary@redhat.com>,
	"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, December 20th
Date: Wed, 11 Jan 2017 14:09:20 +0100	[thread overview]
Message-ID: <5c225c4b-314a-e83e-cbb9-2f3df9c23f0e@6wind.com> (raw)
In-Reply-To: <316115b3-35ee-d99b-6965-21b2b088aa76@redhat.com>

Le 11/01/2017 à 14:04, Dave Neary a écrit :
> It seems that if the review of the technical governance is now complete,
> and the DPDK developer community (and in particular the current
> technical board) is OK with any changes proposed, the biggest remaining
> item will be the budget proposal and setting of membership fees.

Hi Dave,

I agree that we are close, but there are still some few topics that were 
raised based on some reviews of the charter during the seasonal:
   - meetings of the Governing board should be opened, I heard from Mike 
that there are some issues because some people do not like 'open board'. 
Please, they need to be explained.

   - there will be a fee for the lab, it shall be the *same fee* for 
everyone so everyone share the same constraints and benefits for the 
same fee.

I guess, they can be solved quickly.

Best regards,
   Vincent

  reply	other threads:[~2017-01-11 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 15:55 O'Driscoll, Tim
2017-01-11  8:25 ` Thomas Monjalon
2017-01-11 11:41   ` O'Driscoll, Tim
2017-01-11 13:04 ` Dave Neary
2017-01-11 13:09   ` Vincent JARDIN [this message]
2017-01-11 22:23     ` 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:
  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=5c225c4b-314a-e83e-cbb9-2f3df9c23f0e@6wind.com \
    --to=vincent.jardin@6wind.com \
    --cc=dneary@redhat.com \
    --cc=ktraynor@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).