From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?EUC-KR?B?U2ltb24gS2EqZ3N0cm8ibQ==?= Subject: Re: GitHub sandbox for the DPDK community Date: Mon, 04 May 2015 08:52:55 +0200 Message-ID: <55471747.5030705@netinsight.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 7bit To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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