From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id BB930C616 for ; Mon, 4 May 2015 11:05:51 +0200 (CEST) Received: from [172.16.250.156] (unknown [172.16.250.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id 6F3E5A3B2C for ; Mon, 4 May 2015 11:05:51 +0200 (CEST) Message-ID: <5547366D.8090701@bisdn.de> Date: Mon, 04 May 2015 11:05:49 +0200 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: dev@dpdk.org References: <55471747.5030705@netinsight.net> In-Reply-To: <55471747.5030705@netinsight.net> Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2015 09:05:52 -0000 On 04/05/15 08:52, Simon Ka*gstro"m wrote: > On 2015-05-01 17:56, Wiles, Keith wrote: >> I believe the DPDK community would benefit from moving to GitHub as the >> primary DPDK site. http://github.com >> [...] > While I'm really mostly a DPDK outsider, I'd like to express my support > for this suggestion. For my part, I'm mostly interested in the general > development discussion on dpdk-dev, not details about changes in e.g., > the i40 PMD code. Architecture discussions, usage questions etc tend to > get drowned in an endless flow of patches. Indeed. I was proposing in this mail: http://dpdk.org/ml/archives/dev/2015-April/016909.html to have dpdk-users and dpdk-dev. >> - GitHub has a per pull request discussions area, which gives a clean >> way to review all discussions on a specific change. > ... and I think this is one of the great features of github. For an > example on how discussions on merge requests can look, take a look at > e.g., one of the rust-lang merge requests: > > https://github.com/rust-lang/rust/pull/25058#discussion_r29548050 > > which shows nice git commit links, discussions about relevant parts of > the commits, automatic test results etc. Bug reports also get very > nicely integrated into the workflow. > > > I used to be more of a command-line guy, but I'm starting to see the > benefits of the github way of doing things, and I think it would be a > nice improvement for DPDK to start using it as well. I agree that patch/bug discussion gets slightly improved, and scoped (which is good and bad). I think we need to find a good integration with the mailing list in order to both coexist. Discussions cannot be broken into ML and GH. marc > > // Simon