From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <cristian.dumitrescu@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 597222BB4
 for <dev@dpdk.org>; Wed, 22 Feb 2017 19:39:40 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 22 Feb 2017 10:39:39 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.35,195,1484035200"; d="scan'208";a="827313370"
Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75])
 by FMSMGA003.fm.intel.com with ESMTP; 22 Feb 2017 10:39:39 -0800
Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by
 IRSMSX153.ger.corp.intel.com ([169.254.9.160]) with mapi id 14.03.0248.002;
 Wed, 22 Feb 2017 18:39:38 +0000
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>
Thread-Topic: [dpdk-dev] decision process to accept new libraries
Thread-Index: AQHSiQ9wf27zg1K60E+lz3/idhyOGKFzf9OAgAAPmACAAdQXcA==
Date: Wed, 22 Feb 2017 18:39:37 +0000
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126527526AB@IRSMSX108.ger.corp.intel.com>
References: <59AF69C657FD0841A61C55336867B5B035B99794@IRSMSX103.ger.corp.intel.com>
 <3736276.ftqFo2Af7c@xps13>
 <20170221134658.GA208676@bricha3-MOBL3.ger.corp.intel.com>
 <1746585.AAhpvkiIzm@xps13>
In-Reply-To: <1746585.AAhpvkiIzm@xps13>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTZjMTgzN2EtNzBiZi00NGMwLTkyMjctYzdhNDQyYTExMGU5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiIrSjdTdTRSSG1GNm04RW5hV0k4bktZV1hUYVFUS2swZ2Q2TnJNYXBWWXVFPSJ9
x-ctpclassification: CTP_IC
x-originating-ip: [163.33.239.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] decision process to accept new libraries
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 18:39:41 -0000

...<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 wil=
l
> 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?
>=20
> 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
>=20

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