DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] decision process to accept new libraries
Date: Wed, 22 Feb 2017 18:39:37 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126527526AB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1746585.AAhpvkiIzm@xps13>

...<snip>
> > > 1/
> > > I suggest that each new library must be developed in a separate
> repository
> > > on dpdk.org. Then it can be asked to integrate it in the main project/repo.
> > > Such discussion must happen on the mailing list and the techboard will
> vote
> > > for the integration of the *existing* library.
> > > I suggest such vote should be done by majority as stated in the LF
> charter.
> >
> > That sounds a reasonable starting point. Are you suggesting that each
> > library go in a separate repo, or that we have a common staging area
> > repo for all new libs?
> 
> I suggest adding a new repo for each new lib or group some of them if
> relevant.
> Examples: dpdk-qos, dpdk-metrics, dpdk-extra-examples
> 

Are these repos still going to make it into the DPDK release package or left outside?

  reply	other threads:[~2017-02-22 18:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 10:22 [dpdk-dev] DPDK Technical Board Meeting, 2017-02-15 Richardson, Bruce
2017-02-17 11:16 ` [dpdk-dev] decision process to accept new libraries Thomas Monjalon
2017-02-21 13:46   ` Bruce Richardson
2017-02-21 14:42     ` Thomas Monjalon
2017-02-22 18:39       ` Dumitrescu, Cristian [this message]
2017-02-22 19:06       ` Dumitrescu, Cristian
2017-02-24 11:33         ` Remy Horton
2017-02-24 13:10           ` Thomas Monjalon
2017-02-24 13:17           ` Olivier Matz
2017-02-24 13:25             ` Bruce Richardson
2017-02-24 14:26               ` Olivier Matz
2017-02-24 13:07         ` Thomas Monjalon
2017-02-24 13:17           ` Bruce Richardson

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=3EB4FA525960D640B5BDFFD6A3D89126527526AB@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).