[dpdk-dev] decision process to accept new libraries

Dumitrescu, Cristian cristian.dumitrescu at intel.com
Wed Feb 22 19:39:37 CET 2017


...<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?



More information about the dev mailing list