DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Ed Warnicke <hagbard@gmail.com>,
	Jaswinder Singh <jaswinder.singh@nxp.com>
Cc: Michael Dolan <mdolan@linuxfoundation.org>,
	"Ed Warnicke (eaw)" <eaw@cisco.com>,
	"moving@dpdk.org" <moving@dpdk.org>,
	Vincent JARDIN <vincent.jardin@6wind.com>
Subject: Re: [dpdk-moving] DPDK + Linux Foundation - summary of fees
Date: Tue, 17 Jan 2017 22:28:46 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722AA9DE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAFVSqg01oQJTtu1p3i1552wochtGWa_-M5BKVTY6n+iV0sFK=A@mail.gmail.com>

> From: Ed Warnicke [mailto:hagbard@gmail.com] 
> Jaswinder,
> The fd.io infrastructure is for use by fd.io projects.  
> DPDK would be welcome as a fd.io project.
> If the goal is for DPDK to move somewhere neutral and open with best of breed governance and resourcing for open CI then becoming a fd.io project might be the simplest route.   Most of the participants in discussions around DPDK moving are already fd.io members.
> fd.io’s governance is compatible with what we have been discussing.  Should DPDK join fd.io it would, as all fd.io projects, maintain its own internal technical governance.

We discussed this in Dublin. There was a strong preference for keeping DPDK as an independent project. Dave summarized this in the minutes:

"I said that Red Hat is happy with the technical operation of the
project, and we don't want to see the community disrupted with toolset
changes - and it's possible to work with projects like fd.io, OVS, and
OPNFV to do testing of DPDK.

Representatives from Brocade, Cavium, and Linaro all voiced a preference
for a stand-alone lightweight project"


  reply	other threads:[~2017-01-17 22:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 12:21 Vincent JARDIN
2017-01-11 15:12 ` Michael Dolan
2017-01-17 14:16   ` Jaswinder Singh
2017-01-17 20:10     ` Ed Warnicke
2017-01-17 22:28       ` O'Driscoll, Tim [this message]
2017-01-17 23:46         ` Vincent JARDIN
2017-01-18 17:11           ` George Zhao
2017-01-18 17:14             ` Michael Dolan
2017-01-18 17:19               ` George Zhao
2017-01-18 18:47                 ` Vincent Jardin

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=26FA93C7ED1EAA44AB77D62FBE1D27BA722AA9DE@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=eaw@cisco.com \
    --cc=hagbard@gmail.com \
    --cc=jaswinder.singh@nxp.com \
    --cc=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \
    --cc=vincent.jardin@6wind.com \


* 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).