From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0A84E7D01 for ; Fri, 2 Jun 2017 17:29:49 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6E08920AEF; Fri, 2 Jun 2017 11:29:49 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 02 Jun 2017 11:29:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ASwj4Jb4S8ZZYte aJGGL0M+RsMpqen40jBcMK+Mwpz8=; b=o3WmHsH/y8F7ppq1y9PjfxpXn7zxqqq AmuW5tc+wFRRS9RvY1cCX0UWYCqQxoWCjz7cn38jXm/JuCvuZp1j4OFRYPDvS9M/ HPN7Cp3HiwFPH5qzP05tqQzXy/D90lYNVRCAV67fTjSEBxN8e0MgHbwXttE/sJ5r myylvBOZk1Vg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=ASwj4Jb4S8ZZYteaJGGL0M+RsMpqen40jBcMK+Mwpz8=; b=Ej6yGPRU OvEm1pWHIlG7dKnrf6ahIFI9Gosb96wjYSFIFWhGDlpKFvr73pXFxjIJEbp5OJ+c hrSESDHlQyh4vDM/NBhjXS5tC145J5PZ0/BQyncEVIAWg3bz+nFiausYpYxdf1qr GqQKnfO+IIm8azMP5T3TlesA7MARCrPnu4n3M487lDt3E7D1WniH4qmM4qdTbKcU EYYjSfCPufNGN3q55iIV+qn/tz3Fg8R4O2hdpB1rei7YhlzLnoJfHUyOS2i/5ap7 4HIifJIp6nsuc1GmSOPg2XKn6Em1ggLC9XJUCUu/5Cyl5+FTa/SYvULp7prJ2et9 Tw6tM5GVqxgpsg== X-ME-Sender: X-Sasl-enc: r6hQAFKvRfb8qP82MSYtH9vpB/I4lUnwFgFwb71tBRSJ 1496417389 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2538B24009; Fri, 2 Jun 2017 11:29:49 -0400 (EDT) From: Thomas Monjalon To: Tiwei Bie Cc: dev@dpdk.org, bruce.richardson@intel.com, yuanhan.liu@linux.intel.com, konstantin.ananyev@intel.com Date: Fri, 02 Jun 2017 17:29:48 +0200 Message-ID: <136058706.0Fjdze3SFe@xps> In-Reply-To: <20170601050730.GA5765@debian-ZGViaWFuCg> References: <20170601050730.GA5765@debian-ZGViaWFuCg> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC] proposal of allowing personal/project repos on DPDK.org X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 15:29:50 -0000 01/06/2017 07:07, Tiwei Bie: > Hello everyone, >=20 > We'd like to make a proposal of making DPDK.org allow hosting > some personal/project repos, which could be very useful when > someone wants to try some experimental projects in DPDK. Many > formal/mature opensource communities allow this. Such as: [...] So you are asking for a forge. It requires some maintenance effort. > But currently on DPDK.org, for the repos of DPDK, besides the main > repo, there are just one repo for stable release, few old repos > which are obsoleted, and some "-next" repos which are mainly used > as the preparation of pull requests for different subsystems of DPDK. Yes they are the official DPDK repos. > Some =E2=80=9C-next=E2=80=9D repos may be developed individually for a sh= ort time > when they are created, but will always be merged to the main repo > after few releases. We think they are too formal/limited to try > new ideas. Why? Do you need to host a repo on dpdk.org to try a new idea? > What we want to proposal is to make DPDK.org allow hosting some > DPDK based repos which may be very experimental, which even not > be planned to be merged back to the main repo directly, and may > be deleted directly if it proves that no one really cares about > it. Just like what other opensource communities did, allow some > core developers/vendors create their own repos and try ideas on > DPDK.org without too many restrictions. We think it can provide > people a very convenient way to try ideas in DPDK community and > eventually help DPDK grow. >=20 > Allowing it won't have any negative impact on the existing repos > of DPDK, instead, it can help to keep them tidy and clean when > someone wants/needs to try some very experimental and big ideas > publicly in DPDK as he/she can start it in an experimental repo. > An experimental repo can be merged back to the main repo when it > proves to be mature and useful, or could just be deleted when no > one really cares about it any more. >=20 > Please share your thoughts on this. Many thanks! :-) I am against adding some user repos in this list: http://dpdk.org/browse/ I think the list of official repos must be kept light for good visibility. But we can imagine a forge for users at a different location like http://dpdk.org/users/ However why not using another public forge for this need?