From: Thomas Monjalon <email@example.com> To: firstname.lastname@example.org, Matt Spencer <Matt.Spencer@arm.com> Subject: Re: [dpdk-moving] description of technical governance Date: Fri, 28 Oct 2016 21:22:39 +0200 Message-ID: <2677739.KbWyRmNgFH@xps13> (raw) In-Reply-To: <AM5PR0801MB20515A4AA7B1B7CE2A9C9F0395AD0@AM5PR0801MB2051.eurprd08.prod.outlook.com> 2016-10-28 16:52, Matt Spencer: > 1 - we adopt the model as is - one TSC member per committer > 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 > 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 > 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. Thanks for sharing your view. I'm an Open Source guy and I might lack some politician skills. So please excuse me if I take the freedom to talk really frankly :) First of all, this email thread was dedicated to the technical governance. And Matt is introducing money in this topic by talking about incentives. I think it is a very interesting point that we must discuss. >From the beginning, everybody were saying that we must keep technical governance and legal structure separate. However one question has still no good answer: what is the incentive for contributing money in the structure? Is money going to biase the desired meritocratic system? My second comment is about having one company controlling the technical governance. I won't enter into the number details, and it's true that Intel provides at least 50% of the contributions nowadays. Intel is also the biggest contributor to Linux. No surprise. I understand that a voice from ARM is requiring to mitigate this fact. I would prefer ARM related companies working to achieve the same level of commitment as Intel. They are increasing their contribution pace but may never really compete with a giant like Intel. That's why I second Matt to say that we must give a chance to every vendors to influence the technical decisions. Introducing a membership threshold looks to be a good idea. Having said that, I must state that the DPDK reality is a lot more complex than a competition between vendors. We are proving that a consensus based model works very well without the need of a TSC or a board. We can create such organization, but please keep in mind that it should not be really helpful in the day-to-day job.
next prev parent 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 2016-10-28 19:22 ` Thomas Monjalon [this message] 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=2677739.KbWyRmNgFH@xps13 \ --email@example.com \ --cc=Matt.Spencer@arm.com \ --firstname.lastname@example.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 \ email@example.com 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