From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by dpdk.org (Postfix) with ESMTP id 9A1577CE1 for ; Mon, 5 Jun 2017 09:47:17 +0200 (CEST) Received: by mail-wm0-f52.google.com with SMTP id x70so5821603wme.0 for ; Mon, 05 Jun 2017 00:47:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=6PBytzbEZQsZeUIjfOJum6g0idQzzvUjyUwMhPvh2rc=; b=ygfbZ5L2wNoD8KP7uylfvCfKv8pEH9RDEVXJfLcl70RL+yVTCHlChSR9B+Q7EDhdo2 v5sX4QI8mODHDA5ALpwyTW7sJKGvSNxZZWEdys8b2mjjeb6Zmb1piFhdWOWoF9+fCLHX SfD/N0N/DtsmDM/7d0JeLPRWh1y/JSQXEMCyp13c3oYt4fXYw4kkkDHMA1P72mKsyAIc /GeOeJvyFqn/5WrOELAmtSl7O9R7SBHxWUBz6pqwVev4xy9/1Y7hwhsR66Bzy9/h65dm WvfVUgUEq4Rpufi1xQksUwaHMCATiF/LDE5f1Bf14fLQdjCQVUNfX8NCNfxrGWqUF1Pq UOcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=6PBytzbEZQsZeUIjfOJum6g0idQzzvUjyUwMhPvh2rc=; b=nMoOTGl0sY18kuvuAX4bh8gKijbuT6MpNEKoK27JbhG/rJU9tWTmPZcigi0b4PyQra HyqwMcFm5KiS8+nnzUEIOJL7jJ6CAaHA4KIv1P+59Y0IwJBi6ykel6nCaeCN78VdPAxE rvqUDNBPdSgiW8K39ePYYA+uRe9pvVD/cN56vhgFNxqVp+S/UFlKwSL5pFtnkybdh9tI 93u2P493CtML8tEkJMRVAOLEpZgE/yJ6Otf+BrBfNT07AcPX0/ThvkXvkKqvYJ6Qo6aL LBKL23xDmr5JYuJYI353nfDda0rXTG2cr0TmgqtSc43TnAj1LnxIO0qiKdfcai1WVgRi tvcQ== X-Gm-Message-State: AODbwcCDZncB0MGzp62ntRvFomUE30XWK0m3G9UZRU6rdVNgkhJLwJK8 K9yMGLsz8q6TfyKV X-Received: by 10.28.155.65 with SMTP id d62mr7409065wme.78.1496648836912; Mon, 05 Jun 2017 00:47:16 -0700 (PDT) Received: from platinum (2a01cb0c03c651000226b0fffeed02fc.ipv6.abo.wanadoo.fr. [2a01:cb0c:3c6:5100:226:b0ff:feed:2fc]) by smtp.gmail.com with ESMTPSA id v22sm981521wra.19.2017.06.05.00.47.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 05 Jun 2017 00:47:16 -0700 (PDT) Date: Mon, 5 Jun 2017 09:47:14 +0200 From: Olivier Matz To: Stephen Hemminger Cc: "Dumitrescu, Cristian" , Thomas Monjalon , "Bie, Tiwei" , "dev@dpdk.org" , "Richardson, Bruce" , "yuanhan.liu@linux.intel.com" , "Ananyev, Konstantin" Message-ID: <20170605094714.7abe63c5@platinum> In-Reply-To: <20170602133758.27f5b8a1@xeon-e3> References: <20170601050730.GA5765@debian-ZGViaWFuCg> <136058706.0Fjdze3SFe@xps> <3EB4FA525960D640B5BDFFD6A3D891267BA643D3@IRSMSX108.ger.corp.intel.com> <20170602133758.27f5b8a1@xeon-e3> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Mon, 05 Jun 2017 07:47:17 -0000 On Fri, 2 Jun 2017 13:37:58 -0700, Stephen Hemminger wrote: > On Fri, 2 Jun 2017 18:37:40 +0000 > "Dumitrescu, Cristian" wrote: > > > > Why? Do you need to host a repo on dpdk.org to try a new idea? > > > > > > > Prototyping new DPDK-related ideas and sharing them with DPDK > > community, with some of them likely to eventually make their way > > into DPDK once accepted and mature enough. > > > > > > > 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. > > > > We could have a single project called sandbox mentioned in this > > list; whoever interested, needs to drill down into this one? > > > > > > 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? > > > > Easier to share DPDK related ideas on dpdk.org rather than other > > places. > > Let's not distract Thomas and others with lots of effort to run > servers. Having dpdk.org be the server for development and stable > should be more than enough. > > Running a secure server for user repositories is hard. If you want an > example, look follow some of the two factor auth stuff being done at > kernel.org. > > Another option would be to have an official clone of dpdk.org on > github and let users do what they need to there. This keeps project > out of the forge business. > +1 I'm not convinced about why having those repos hosted at a place or another would help to share ideas. It will generates a long list of obsolete directories. For instance, in my opinon, the repo list on kernel.org brings more noise than useful info: https://git.kernel.org/ As Stephen said, administrating these new repos/ml/patchwork/... would imply a maintenance work (Thomas), knowing there are plenty other ways to have a public git repo. Instead, what about adding a link on dpdk.org website that would point to a place for dpdk.org related projects on github/gitlab/... This could be either to a public forge, or to a dedicated server administrated by people that needs this feature, avoiding another work load for Thomas ;) Olivier