DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "moving@dpdk.org" <moving@dpdk.org>
Subject: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, December 20th
Date: Wed, 21 Dec 2016 15:55:34 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA72299670@IRSMSX108.ger.corp.intel.com> (raw)

Here are my notes from Tuesday's call. Please feel free to correct any errors or to add additional details.

Attendees: Ed Warnicke (Cisco), Hemant Agrawal (NXP), Jan Blunck (Brocade), Jaswinder Singh (NXP), John McNamara (Intel), Keith Wiles (Intel), Kevin Traynor (Red Hat), Olga Shern (Mellanox), Stephen Hemminger (Microsoft), Thomas Monjalon (6WIND), Tim O'Driscoll (Intel), Vincent Jardin (6WIND), Yoni Luzon (Mellanox). Note that there may have been others, but as people joined at different times it was difficult to keep track.

Firstly, here are some links to help keep track of things:
Project Charter: https://docs.google.com/document/d/1x43ycfW3arJNX-e6NQt3OVzAuNXtD7dppIhrY48FoGs
Summary of discussion at Userspace event in Dublin: http://dpdk.org/ml/archives/dev/2016-October/049259.html
Minutes of October 31st call: http://dpdk.org/ml/archives/moving/2016-November/000031.html
Minutes of November 8th call: http://dpdk.org/ml/archives/moving/2016-November/000058.html
Minutes of November 15th call: http://dpdk.org/ml/archives/moving/2016-November/000061.html
Minutes of November 22nd call: http://dpdk.org/ml/archives/moving/2016-November/000085.html
Minutes of November 29th call: http://dpdk.org/ml/archives/moving/2016-November/000099.html
Minutes of December 6th call: http://dpdk.org/ml/archives/moving/2016-December/000121.html
Minutes of December 13th call: http://dpdk.org/ml/archives/moving/2016-December/000124.html
Technical governance, including info on Maintainers and sub-trees: http://dpdk.org/doc/guides/contributing/index.html & http://dpdk.org/dev.

1. Status of charter doc:
- The only remaining comment on the doc is Matt's suggestion for a Contributor member level. We need both Mike Dolan (who opposes this) and Matt present on the same call to disposition this.
- People should conduct a final review of the charter before the next meeting (Tuesday 10th Jan). Issues can either be raised as comments in the doc or raised on the moving@dpdk.org mailing list. Please refer to the previous discussion/resolution if you're raising an issue that's been covered before so that we don't simply repeat previous discussions

2. Technical Governance:
- John and Thomas described the recent changes to the Contributor's Guidelines which now includes a section on Maintainers and Sub-Trees. See http://dpdk.org/doc/guides/contributing/patches.html#maintainers-and-sub-trees. Again, people should review and raise any additional comments/concerns on the dev@dpdk.org mailing list.

3. Technical Board:
- Ed asked what happens if the Technical Board make a decision on a disputed patch set but a Maintainer/Committer refuses to comply with that decision. In reality, it's not expected that this situation will occur, but I've added text to section 3.2.1 point iv to clarify that the Tech Board has the right to make any changes necessary to enforce its decision in this situation.
- We discussed the need to review membership of the Tech Board. Proposals for how to do this included: a) ask the Tech Board to review and update its own membership; b) define some membership criteria and hold a vote. We didn't reach a definite conclusion on this. I'd suggest that we ask the current Tech Board to determine the most efficient process to update its membership. I'll submit a request to techboard@dpdk.org to ask that they do this and that they provide an update at a future meeting.

4. Membership:
- Ed's guidance from FD.io was that the process of recruiting members could take up to 6 months. We have done a lot of prep work during these meetings so we hope to do it faster than this and will target 3 months. This would allow for a project launch in Q2. We'll use our first meeting in Jan to work out the next steps on this.
- Potential member companies should make sure that their decision-makers for joining and funding DPDK are aware of these discussions and of the status of the charter doc.

Next Meeting:
We'll resume again on Tuesday January 10th at 3pm GMT, 4pm CET, 10am EST, 7am PST. We'll cover any additional (and hopefully final) comments on the charter, and discuss next steps for determining project members.

             reply	other threads:[~2016-12-21 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 15:55 O'Driscoll, Tim [this message]
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
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:

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

  git send-email \
    --in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BA72299670@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=moving@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK community structure changes

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/moving/0 moving/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 moving moving/ http://inbox.dpdk.org/moving \
	public-inbox-index moving

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git