DPDK community structure changes
 help / color / Atom feed
From: Matt Spencer <Matt.Spencer@arm.com>
To: "moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] description of technical governance
Date: Fri, 28 Oct 2016 16:52:11 +0000
Message-ID: <AM5PR0801MB20515A4AA7B1B7CE2A9C9F0395AD0@AM5PR0801MB2051.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA676091C7@IRSMSX108.ger.corp.intel.com>

[-- Attachment #1.1: Type: text/plain, Size: 7603 bytes --]

Hi Guys


I have a few thoughts on the TSC membership as is outlined by the OVS model that we appear to be wanting to adopt.  The information I have here is taken from a snapshot of the MAINTAINERS file in the latest release of DPDK, and does not take into account what Tim mentions below.


Attached is a spreadsheet that shows how the TSC would look if we were to adopt the OVS model today, and I believe it highlights why a variation of the model be adopted.  As it stands today, it would be heavily biassed towards one company to the point that one organisation would have a virtual veto within the TSC.  I also believe that there would be too many members of the TSC which would hinder it from being an effective governing body for DPDK.


I would the therefor like to put forward a few additional models for suggestion:


1 - we adopt the model as is - one TSC member per committer

       o As this stands today, that would give us 56 TSC members, with almost half of them from one company


2 - we adopt the model as is - one TSC member per committer - to a maximum of 20% membership of the TSC

       o This would ensure that no one company can 'own' the TSC - 56 committers, so max TSC membership from one company would be 11


3 - Maximum one member of TSC per committing company, plus one TSC assignee per paid member

       o This would keep the TSC to a manageable level, give companies an incentive to join, but not require membership to be on the TSC


4 - Something else?


My current thoughts are with 3 because we should end up with a representative cross section of the stakeholders of the project, whilst still incentivising membership of the foundation.


My 2c, let me know what you think.


Regards


Matt

________________________________
From: moving <moving-bounces@dpdk.org> on behalf of O'Driscoll, Tim <tim.odriscoll@intel.com>
Sent: 28 October 2016 10:13:51
To: O'Driscoll, Tim; Thomas Monjalon; moving@dpdk.org
Subject: Re: [dpdk-moving] description of technical governance


> -----Original Message-----
> From: moving [mailto:moving-bounces@dpdk.org] On Behalf Of O'Driscoll,
> Tim
> Sent: Wednesday, October 26, 2016 11:22 AM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>; moving@dpdk.org
> Subject: Re: [dpdk-moving] description of technical governance
>
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Tuesday, October 25, 2016 3:00 PM
> > To: moving@dpdk.org
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > Subject: Re: [dpdk-moving] description of technical governance
> >
> > 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.
>
> Yes, it's the additional detail that I was asking about. If you look at
> what we have at the moment (http://dpdk.org/dev), it's quite brief.
> Other projects typically have more detail, for example:
> - FD.io Technical Community Charter: https://fd.io/governance/technical-
> community-charter
> - OvS technical governance including committer responsibilities and
> process for adding and removing committers:
> http://openvswitch.github.io/contributors/
> - ODL TSC Charter: https://www.opendaylight.org/tsc-charter
>
> We don't necessarily need as much detail as they have, but I think we do
> need a bit more than we have at the moment. From a brief discussion with
> Mike Dolan during our previous engagement with the LF earlier in the
> year, the LF would simply be looking for DPDK technical governance to be
> properly documented, and for it to be meritocratic (e.g. committers
> chosen based on history of contributions rather than the company they
> work for).
>
> Matt also had some thoughts during our discussion in Dublin on things
> he'd like to see added to the technical governance. Perhaps he can
> comment further on what he'd like to see.
>
> In terms of where this is documented, I don't think that matters, and
> adding some additional detail to the existing Development page seems
> like a good solution to me.

I haven't seen anybody else comment on aspects of the technical governance that should be clarified, so here are a few comments/questions from me that might help to prompt some discussion.

We have a few different types of maintainers: 1) those responsible for reviewing changes in individual libraries who are identified in the MAINTAINERS file; 2) sub-tree maintainers who submit pull requests to the main tree; 3) stable release maintainer; 4) main tree maintainer; 5) maintainers for other projects hosted on dpdk.org (pktgen, spp etc.). We should document the responsibilities of each of these, and the process for adding and removing them.

At the moment, the MAINTAINERS file doesn't identify the sub-tree maintainers or the stable release maintainer. I think they should be included.

At the moment, other projects hosted on dpdk.org (pktgen, spp etc.) don't have a MAINTAINERS file. I think this should be mandatory for all sub-projects within DPDK.

Should every repo have more than one person with commit rights so that we're not dependent on a single person? They would obviously have to coordinate on who does what, which could involve sharing the workload or operating on an active/backup basis.

We should document how members of the Tech Board get added/removed. We should also clarify the scope. Is the scope of the Tech Board just DPDK itself (http://dpdk.org/browse/dpdk/tree/), or does it also cover the other projects hosted on dpdk.org (http://dpdk.org/browse/)? If it's just DPDK, then who provides the technical oversight for the other projects? My preference would be for the existing board to cover all sub-projects.

We should document the process for adding a new sub-project like pktgen or SPP. At the moment I think it's proposed on the dev mailing list and added if there's a consensus. Should it be mandatory that new project proposals are reviewed and approved by the Tech Board, to make sure there's consistency and nothing gets missed in a flood of email?

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #1.2: Type: text/html, Size: 9890 bytes --]

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
	{margin-top:0;
	margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Guys</p>
<p><br>
</p>
<p>I have a few thoughts on the TSC membership as is outlined by the OVS model that we appear to be wanting to adopt. &nbsp;The information I have here is taken from a snapshot of the MAINTAINERS file in the latest release of DPDK, and does not take into account
 what Tim mentions below.</p>
<p><br>
</p>
<p>Attached is a spreadsheet that shows how the TSC would look if we were to adopt the OVS model today, and I believe it highlights why a variation of the model be adopted. &nbsp;As it stands today, it would be heavily biassed towards one company to the point that
 one organisation would have a virtual veto within the TSC. &nbsp;I also believe that there would be too many members of the TSC which&nbsp;would hinder it from being an effective governing body for DPDK.</p>
<p><br>
</p>
<p>I would the therefor like to put forward a few additional&nbsp;models for suggestion:</p>
<p><br>
</p>
<p>1 - we adopt the model as is - one TSC member per committer</p>
<p>&nbsp; &nbsp; &nbsp; &nbsp;o As this stands today, that would give us 56 TSC members, with almost half of them from one company</p>
<p><br>
</p>
<p>2 - we adopt the model as is - one TSC member per committer - to a maximum of 20% membership of the TSC</p>
<p>&nbsp; &nbsp; &nbsp; &nbsp;o This would ensure that no one company can 'own' the TSC - 56 committers, so max TSC membership from one company would be 11</p>
<p><br>
</p>
<p>3 - Maximum one member of TSC per committing company, plus one TSC assignee per paid member</p>
<p>&nbsp; &nbsp; &nbsp; &nbsp;o This would keep the TSC to a manageable level, give companies an incentive to join, but not require membership to be on the TSC</p>
<p><br>
</p>
<p>4 - Something else?</p>
<p><br>
</p>
<p>My current thoughts are with 3 because we should end up with a representative cross section of the stakeholders of the project, whilst still incentivising membership of the foundation.</p>
<p><br>
</p>
<p>My 2c, let me know what you think.</p>
<p><br>
</p>
<p>Regards</p>
<p><br>
</p>
<p>Matt</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> moving &lt;moving-bounces@dpdk.org&gt; on behalf of O'Driscoll, Tim &lt;tim.odriscoll@intel.com&gt;<br>
<b>Sent:</b> 28 October 2016 10:13:51<br>
<b>To:</b> O'Driscoll, Tim; Thomas Monjalon; moving@dpdk.org<br>
<b>Subject:</b> Re: [dpdk-moving] description of technical governance</font>
<div>&nbsp;</div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
&gt; -----Original Message-----<br>
&gt; From: moving [<a href="mailto:moving-bounces@dpdk.org">mailto:moving-bounces@dpdk.org</a>] On Behalf Of O'Driscoll,<br>
&gt; Tim<br>
&gt; Sent: Wednesday, October 26, 2016 11:22 AM<br>
&gt; To: Thomas Monjalon &lt;thomas.monjalon@6wind.com&gt;; moving@dpdk.org<br>
&gt; Subject: Re: [dpdk-moving] description of technical governance<br>
&gt; <br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: Thomas Monjalon [<a href="mailto:thomas.monjalon@6wind.com">mailto:thomas.monjalon@6wind.com</a>]<br>
&gt; &gt; Sent: Tuesday, October 25, 2016 3:00 PM<br>
&gt; &gt; To: moving@dpdk.org<br>
&gt; &gt; Cc: O'Driscoll, Tim &lt;tim.odriscoll@intel.com&gt;<br>
&gt; &gt; Subject: Re: [dpdk-moving] description of technical governance<br>
&gt; &gt;<br>
&gt; &gt; 2016-10-25 11:27, O'Driscoll, Tim:<br>
&gt; &gt; &gt; We also have a gap in terms of documenting technical governance.<br>
&gt; &gt; &gt; Even ignoring the move to LF, Matt in particular was looking for<br>
&gt; &gt; &gt; more clarity on this.<br>
&gt; &gt; &gt; Thomas: would you be willing to create and post a proposal on this?<br>
&gt; &gt;<br>
&gt; &gt; The technical governance is consensus-based.<br>
&gt; &gt; The board was built in case a consensus is not found.<br>
&gt; &gt;<br>
&gt; &gt; There are several projects with their own git trees.<br>
&gt; &gt; DPDK and the web site are two of them.<br>
&gt; &gt;<br>
&gt; &gt; The DPDK project is organized around some git subtrees<br>
&gt; &gt; and the mainline gathers every contributions accepted in the subtrees.<br>
&gt; &gt; The component maintainers are quality responsibles for the code and<br>
&gt; &gt; the git history. They coordinate how improvements and fixes are done.<br>
&gt; &gt; The git tree committers are responsibles of the pace, giving time for<br>
&gt; &gt; reviews and tests while releasing in time. They also do the last<br>
&gt; checks<br>
&gt; &gt; or call for help when there is no progress on a patch.<br>
&gt; &gt;<br>
&gt; &gt; Is it the kind of information you are looking for?<br>
&gt; &gt; I think the technical governance must be described on the web site<br>
&gt; &gt; in the &quot;development&quot; page.<br>
&gt; &gt; It is already partly described but it may requires more details and<br>
&gt; &gt; updates.<br>
&gt; <br>
&gt; Yes, it's the additional detail that I was asking about. If you look at<br>
&gt; what we have at the moment (<a href="http://dpdk.org/dev">http://dpdk.org/dev</a>), it's quite brief.<br>
&gt; Other projects typically have more detail, for example:<br>
&gt; - FD.io Technical Community Charter: <a href="https://fd.io/governance/technical-">
https://fd.io/governance/technical-</a><br>
&gt; community-charter<br>
&gt; - OvS technical governance including committer responsibilities and<br>
&gt; process for adding and removing committers:<br>
&gt; <a href="http://openvswitch.github.io/contributors/">http://openvswitch.github.io/contributors/</a><br>
&gt; - ODL TSC Charter: <a href="https://www.opendaylight.org/tsc-charter">https://www.opendaylight.org/tsc-charter</a><br>
&gt; <br>
&gt; We don't necessarily need as much detail as they have, but I think we do<br>
&gt; need a bit more than we have at the moment. From a brief discussion with<br>
&gt; Mike Dolan during our previous engagement with the LF earlier in the<br>
&gt; year, the LF would simply be looking for DPDK technical governance to be<br>
&gt; properly documented, and for it to be meritocratic (e.g. committers<br>
&gt; chosen based on history of contributions rather than the company they<br>
&gt; work for).<br>
&gt; <br>
&gt; Matt also had some thoughts during our discussion in Dublin on things<br>
&gt; he'd like to see added to the technical governance. Perhaps he can<br>
&gt; comment further on what he'd like to see.<br>
&gt; <br>
&gt; In terms of where this is documented, I don't think that matters, and<br>
&gt; adding some additional detail to the existing Development page seems<br>
&gt; like a good solution to me.<br>
<br>
I haven't seen anybody else comment on aspects of the technical governance that should be clarified, so here are a few comments/questions from me that might help to prompt some discussion.<br>
<br>
We have a few different types of maintainers: 1) those responsible for reviewing changes in individual libraries who are identified in the MAINTAINERS file; 2) sub-tree maintainers who submit pull requests to the main tree; 3) stable release maintainer; 4)
 main tree maintainer; 5) maintainers for other projects hosted on dpdk.org (pktgen, spp etc.). We should document the responsibilities of each of these, and the process for adding and removing them.<br>
<br>
At the moment, the MAINTAINERS file doesn't identify the sub-tree maintainers or the stable release maintainer. I think they should be included.<br>
<br>
At the moment, other projects hosted on dpdk.org (pktgen, spp etc.) don't have a MAINTAINERS file. I think this should be mandatory for all sub-projects within DPDK.<br>
<br>
Should every repo have more than one person with commit rights so that we're not dependent on a single person? They would obviously have to coordinate on who does what, which could involve sharing the workload or operating on an active/backup basis.<br>
<br>
We should document how members of the Tech Board get added/removed. We should also clarify the scope. Is the scope of the Tech Board just DPDK itself (<a href="http://dpdk.org/browse/dpdk/tree/">http://dpdk.org/browse/dpdk/tree/</a>), or does it also cover
 the other projects hosted on dpdk.org (<a href="http://dpdk.org/browse/">http://dpdk.org/browse/</a>)? If it's just DPDK, then who provides the technical oversight for the other projects? My preference would be for the existing board to cover all sub-projects.<br>
<br>
We should document the process for adding a new sub-project like pktgen or SPP. At the moment I think it's proposed on the dev mailing list and added if there's a consensus. Should it be mandatory that new project proposals are reviewed and approved by the
 Tech Board, to make sure there's consistency and nothing gets missed in a flood of email?<br>
<br>
</div>
</span></font>IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use
 it for any purpose, or store or copy the information in any medium. Thank you.
</body>
</html>

[-- Attachment #2: TSC Members by company.xlsx --]
[-- Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Size: 54665 bytes --]

  reply index

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 [this message]
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 publically 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=AM5PR0801MB20515A4AA7B1B7CE2A9C9F0395AD0@AM5PR0801MB2051.eurprd08.prod.outlook.com \
    --to=matt.spencer@arm.com \
    --cc=moving@dpdk.org \
    /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

DPDK community structure changes

Archives are clonable:
	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 \
		moving@dpdk.org
	public-inbox-index moving


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.moving


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