From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: moving@dpdk.org
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-moving] description of technical governance
Date: Tue, 25 Oct 2016 16:00:12 +0200 [thread overview]
Message-ID: <4939831.0LCNYxqha0@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com>
2016-10-25 11:27, O'Driscoll, Tim:
> We also have a gap in terms of documenting technical governance.
> Even ignoring the move to LF, Matt in particular was looking for
> more clarity on this.
> Thomas: would you be willing to create and post a proposal on this?
The technical governance is consensus-based.
The board was built in case a consensus is not found.
There are several projects with their own git trees.
DPDK and the web site are two of them.
The DPDK project is organized around some git subtrees
and the mainline gathers every contributions accepted in the subtrees.
The component maintainers are quality responsibles for the code and
the git history. They coordinate how improvements and fixes are done.
The git tree committers are responsibles of the pace, giving time for
reviews and tests while releasing in time. They also do the last checks
or call for help when there is no progress on a patch.
Is it the kind of information you are looking for?
I think the technical governance must be described on the web site
in the "development" page.
It is already partly described but it may requires more details and updates.
next prev parent reply other threads:[~2016-10-25 14:00 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 ` Thomas Monjalon [this message]
2016-10-26 10:21 ` [dpdk-moving] description of technical governance 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
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:
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=4939831.0LCNYxqha0@xps13 \
--to=thomas.monjalon@6wind.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).