DPDK community structure changes
 help / color / mirror / Atom feed
From: Jan Blunck <Jan.Blunck@brocade.com>
To: "Matt.Spencer@arm.com" <Matt.Spencer@arm.com>,
	"mdolan@linuxfoundation.org" <mdolan@linuxfoundation.org>,
	"tim.odriscoll@intel.com" <tim.odriscoll@intel.com>
Cc: "moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] description of technical governance
Date: Mon, 31 Oct 2016 18:31:44 +0000	[thread overview]
Message-ID: <1477938704.2463.48.camel@brocade.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6760A4D3@IRSMSX108.ger.corp.intel.com>

On Mo, 2016-10-31 at 16:56 +0000, O'Driscoll, Tim wrote:
> We do have a Technical Board (effectively a TSC with a different
> name) for DPDK in place already (see http://dpdk.org/dev#board). We
> deliberately populated this board based on the most significant
> contributors to the project, and made sure that it was balanced so
> that no single company had a majority. Current composition is 2
> members from Intel, 2 from 6WIND, 1 from Cavium, 1 from Red Hat and 1
> from Microsoft.
> My proposal would be that we keep this board in place rather than
> create a new TSC. I do think we need to more clearly define the scope
> of the board and how people are added to/removed from it, but I don’t
> see a reason to change or replace it.


Right now I do not see enough reason to replace the technical board. On
the other hand I do understand Matts point that for anyone not
attending DPDK Userspace Summit 2015 it is hard to understand how the
board was chosen. Therefore I believe it is necessary to define and
document a transparent process to mandate the technical board.

I don't think that mixing the governance of the financial and technical
aspects of the project is the right thing to do though. Especially the
technical architecture should not be defined by committee (technical
board) but through collaboration in-the-open (on the development
mailing list). This is a transparent process with low entrance
boundaries that is proven to work also for other projects than DPDK.


  parent reply	other threads:[~2016-10-31 18:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25  8:58 [dpdk-moving] [Topics] Francois Ozog
2016-10-25 11:27 ` O'Driscoll, Tim
2016-10-25 14:00   ` [dpdk-moving] description of technical governance Thomas Monjalon
2016-10-26 10:21     ` O'Driscoll, Tim
2016-10-28  9:13       ` O'Driscoll, Tim
2016-10-28 16:52         ` Matt Spencer
2016-10-28 19:22           ` Thomas Monjalon
2016-10-28 22:54             ` Vincent Jardin
2016-10-31 15:20               ` Matt Spencer
2016-10-31 16:07                 ` Michael Dolan
2016-10-31 16:18                   ` Matt Spencer
2016-10-31 16:33                     ` Michael Dolan
2016-10-31 16:43                       ` Matt Spencer
2016-10-31 16:52                         ` Michael Dolan
2016-10-31 16:56                           ` O'Driscoll, Tim
2016-10-31 16:58                             ` Michael Dolan
2016-10-31 18:31                             ` Jan Blunck [this message]
2016-10-31 19:41                               ` Vincent JARDIN
     [not found]                   ` <DB5PR04MB1605482F1C67F9B797EB9AE289A60@DB5PR04MB1605.eurprd04.prod.outlook.com>
2016-11-08  8:11                     ` Jaswinder Singh
2016-11-08  9:37                       ` O'Driscoll, Tim
2016-12-20 14:41       ` Thomas Monjalon
2016-10-25 14:55 ` [dpdk-moving] [Topics] Dave Neary
2016-10-26 12:47 ` Dave Neary
2016-10-26 15:00   ` Francois Ozog

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=1477938704.2463.48.camel@brocade.com \
    --to=jan.blunck@brocade.com \
    --cc=Matt.Spencer@arm.com \
    --cc=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \
    --cc=tim.odriscoll@intel.com \


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