DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, November 29th
Date: Wed, 30 Nov 2016 22:08:10 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67626FA5@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1520761.A9r9uhvuWc@xps13>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, November 30, 2016 5:10 PM
> To: moving@dpdk.org
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>
> Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, November 29th
> 2016-11-30 16:01, O'Driscoll, Tim:
> > - For voting, agreed that the quorum for a meeting for either board is
> 50% of the members. Majority required to pass a vote is 50% of the total
> board except for: a) changes to the charter require 2/3 of the GB; b)
> licensing exceptions require 2/3 of the GB.
> The current quorum for the TB is 6/7. 50% is a big change.

I'm not sure where 6/7 was agreed,  but I'd be against that for a few reasons:
- Requiring a 6/7 majority makes it very difficult to pass a vote because almost everybody has to be available, in attendance and in agreement.
- It means that companies that have two representatives on the board (currently Intel and 6WIND) effectively have a veto.
- A minor point, but whatever level we decide on should be expressed as a percentage so that it's applicable if/when the board size changes.

> > - I've updated the charter (section 3 - Project Governance) to reflect
> these changes.
> I wonder what part of the TB process must be in this charter.
> I think we agreed that the TB process must be documented elsewhere?

All the other LF project charters that I've looked at include the composition/responsibilities/process of their Tech Board/TSC. If this body is responsible for technical oversight of the project, then I think it needs to be agreed and documented in the charter.

My proposal is that we include the Tech Board in the charter doc, but leave the lower-level details of the day-to-day governance (maintainers, how they're added/removed etc.) to the Contributor's Guidelines. We can discuss and agree how much needs to be in the charter at the next meeting.

  reply	other threads:[~2016-11-30 22:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 16:01 O'Driscoll, Tim
2016-11-30 17:10 ` Thomas Monjalon
2016-11-30 22:08   ` O'Driscoll, Tim [this message]
2016-12-01  9:20     ` Thomas Monjalon
2016-12-01  9:40       ` O'Driscoll, Tim
2016-11-30 17:39 ` Michael Dolan
2016-11-30 20:55   ` Dave Neary
2016-12-01 17:40   ` O'Driscoll, Tim
2016-12-01 17:46     ` Ed Warnicke
2016-12-01 18:01     ` Michael Dolan
2016-12-01 18:41     ` Dave Neary
2016-12-01 18:50       ` Dave Neary
2016-12-01 19:09         ` Francois Ozog
2016-12-01 19:44           ` Michael Dolan
2016-12-01 20:20             ` O'Driscoll, Tim
2016-12-01 20:47               ` Wiles, Keith
2016-12-01 21:33           ` O'Driscoll, Tim
2016-12-02  9:00             ` Francois Ozog
2016-12-01 20:33       ` 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=26FA93C7ED1EAA44AB77D62FBE1D27BA67626FA5@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=moving@dpdk.org \
    --cc=thomas.monjalon@6wind.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).