From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Hobywan Kenoby <hobywank@hotmail.com>
Subject: Re: [dpdk-users] Project Governance and Linux Foundation
Date: Mon, 17 Oct 2016 14:40:54 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA675F707A@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <56798548.UUDuXfq43Z@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, October 17, 2016 1:41 PM
> To: users@dpdk.org; dev@dpdk.org
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Hobywan Kenoby
> <hobywank@hotmail.com>
> Subject: Re: [dpdk-users] Project Governance and Linux Foundation
>
> 2016-10-17 11:52, O'Driscoll, Tim:
> > From: Hobywan Kenoby
> > > The current DPDK version can run on virtually all processors (Intel,
> IBM
> > > and ARM) and leverage all NICs: is there **really** anyone
> questionning
> > > openness of the community?
> >
> > I still hear concerns on this, and based on discussions with others
> who
> > put their names to the post below, they do too.
> > I think it's a perception that we need to address.
>
> It is simple to address this perception with fact checking.
> The next releases will provide even more code for ARM and NPUs.
> If someone submits some good code and is ignored, it is easy enough
> to ping the mailing list and make it visible.
> If someone sees any regression on his architecture, we care.
> Please let's stop maintaining confusion on this topic.
>
> DPDK *is* truly open.
Well, to be a little more specific, the concern I've heard on many occasions is that 6WIND control the infrastructure for the project and so effectively have a veto over what's accepted into DPDK. Your argument is that you've never exercised that veto, which is true, but you still have the ability to do so. That's not a characteristic of a truly open project. As stated in the original post on this:
> - The infrastructure for a project like DPDK should not be owned and controlled by any single company.
next prev parent reply other threads:[~2016-10-17 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 8:33 O'Driscoll, Tim
2016-10-17 10:23 ` Hobywan Kenoby
2016-10-17 11:52 ` O'Driscoll, Tim
2016-10-17 12:40 ` Thomas Monjalon
2016-10-17 14:40 ` O'Driscoll, Tim [this message]
2016-10-18 13:22 ` Thomas Monjalon
2016-10-17 21:23 ` [dpdk-users] [dpdk-dev] " Dave Neary
2016-10-18 11:34 ` Jerin Jacob
2016-10-18 13:27 ` Thomas Monjalon
2016-10-18 16:26 ` Jerin Jacob
2016-10-19 8:04 ` O'Driscoll, Tim
2016-10-19 8:40 ` Dave Neary
2016-10-19 9:56 ` Thomas Monjalon
2016-10-19 9:09 ` Jerin Jacob
2016-10-18 4:16 ` Liu Yuan
2016-10-18 10:29 ` [dpdk-users] [dpdk-dev] How to printout PMD logs to console yingzhi
2016-10-18 10:58 ` Kavanagh, Mark B
2016-10-18 12:51 ` [dpdk-users] [dpdk-dev] Project Governance and Linux Foundation Thomas Monjalon
2016-10-21 14:00 ` Dave Neary
2016-10-21 17:20 ` Wiles, Keith
2016-10-22 19:27 ` Thomas Monjalon
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=26FA93C7ED1EAA44AB77D62FBE1D27BA675F707A@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=dev@dpdk.org \
--cc=hobywank@hotmail.com \
--cc=thomas.monjalon@6wind.com \
--cc=users@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
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).