From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 225799E3; Tue, 20 Jun 2017 09:21:37 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 710BD20BDA; Tue, 20 Jun 2017 03:21:35 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 20 Jun 2017 03:21:35 -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=jUsQ9ZyB8JAcln3 SoMzZtTD78qDmhJ4Zaury9tv3cNk=; b=XIR6nHCfDmrvBHg21//JQqmO6G71or2 5O17+v1HWVVj+rKMUBEDC8tVy/WYAPxVHZMBUdPbm36ViXdZYQerowntqaIqRGCU Gnk2cwVJ5/MmlwI1UazoHBCVfAUoYqZRbOafADpTe2LnlK9q+XF5CNgruyrr5pel OM8ikAdeFcs4= 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=jUsQ9ZyB8JAcln3SoMzZtTD78qDmhJ4Zaury9tv3cNk=; b=FDwZUcdM NMRO9oSVpJhQ9A2lK6Ip7ovJ5h4cI116UmRSyjJCouAs++YN6xDgv8WGpBOS5wh5 yJlkWhhXHY3fAOnZaB36Fw0JctmCYkZOL6Gs0/VTw/6fT4O0RVKfjmBJ2WYz+hJ8 Vtd4hJr7PFiM58BO0K9oHijKchma/EE2Mqd1bo5HltryE5fEqRAZmLY2lfTHQtGx 4jAXO6FAdV8/hzTofuXfC4DQ2Ks1KOMx0UBnoQMc7+UNIoBotmhlriKumzaz+CGl Bs8d58JocaOtrZd3Rpc5RuHcWvzqorS0WXo/8UlvXwjXiyp9y8XqqaoPIRkBXoyD 2WSZiD3ioNAaqw== X-ME-Sender: X-Sasl-enc: 2PKH7EF49cBSA313h7eXwXijCvlN9uCFpQpfU5UDcAxa 1497943295 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 28DD224033; Tue, 20 Jun 2017 03:21:35 -0400 (EDT) From: Thomas Monjalon To: Tiwei Bie Cc: dev@dpdk.org, techboard@dpdk.org Date: Tue, 20 Jun 2017 09:21:34 +0200 Message-ID: <2183495.DK3t6yERKa@xps> In-Reply-To: <20170620061618.GA14527@debian-ZGViaWFuCg> References: <20170601050730.GA5765@debian-ZGViaWFuCg> <11265330.F2tAlQhP2k@xps> <20170620061618.GA14527@debian-ZGViaWFuCg> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Tue, 20 Jun 2017 07:21:38 -0000 20/06/2017 08:16, Tiwei Bie: > On Mon, Jun 19, 2017 at 03:29:29PM +0200, Thomas Monjalon wrote: > > Hi, > > > > 01/06/2017 07:07, Tiwei Bie: > > > 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. > > > > It has been discussed during the last technical board meeting. > > The board was not convinced by this idea, but would like to better > > understand what is the problem to be solved with this proposal? > > > > If there is something to solve, we could decide one these proposals: > > 1/ let users free to choose their forge > > 2/ advise for gitlab > > 3/ advise for github (and fight to recover the name DPDK) > > 4/ pay a sysadmin to host and secure our own forge in dpdk.org domain > > > > Anyway, I don't think it's a bad idea to get the name DPDK back > on github if possible. Any thoughts? I've already tried to get it two years ago. I will try again requesting help from the Linux Foundation.