From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <simon.kagstrom@netinsight.net>
Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.21])
 by dpdk.org (Postfix) with SMTP id 51B43C64A
 for <dev@dpdk.org>; Mon,  4 May 2015 08:53:03 +0200 (CEST)
Received: from [10.100.1.152] (unverified [10.100.1.152]) by
 ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0029788377@ernst.netinsight.se>;
 Mon, 04 May 2015 08:52:57 +0200
Message-ID: <55471747.5030705@netinsight.net>
Date: Mon, 04 May 2015 08:52:55 +0200
From: =?EUC-KR?B?U2ltb24gS2EqZ3N0cm8ibQ==?=
 <simon.kagstrom@netinsight.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dev@dpdk.org
References: <D1690998.1E825%keith.wiles@intel.com>
In-Reply-To: <D1690998.1E825%keith.wiles@intel.com>
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 <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: Mon, 04 May 2015 06:53:03 -0000

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.

>   - 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.

// Simon