From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?U2ltb24gS8OlZ3N0csO2bQ==?= Subject: Re: GitHub sandbox for the DPDK community Date: Wed, 06 May 2015 10:30:04 +0200 Message-ID: <5549D10C.7010300@netinsight.net> References: <20150501164512.GB27756@hmsreliant.think-freely.org> <20150501173108.GA24714@mhcomputing.net> <533710CFB86FA344BFBF2D6802E602860466B524@SHSMSX101.ccr.corp.intel.com> <20150504174857.GA27496@mhcomputing.net> <924D0FD1-4A1F-4C3E-929C-38C29AED61D7@netgate.com>, <20150505135542.GB27259@hmsreliant.think-freely.org> <0CA4031C-561F-4BB9-8B14-674D6D99EE6E@intel.com> <5549CCEC.8090606@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <5549CCEC.8090606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 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-06 10:12, Panu Matilainen wrote: > On 05/05/2015 07:43 PM, Wiles, Keith wrote: > >> GitHub offers a different set of processes and >> tools, which we do not have to create. Moving to GitHub is a change >> for the community and I feel a good change for the better. > > Like quite a few others in this thread, I dont care if the git repo > moved to the end of internet as long as email continues to be a > first-class means for patch submissions, reviews and other > communication. It doesn't have to be the only way as clearly many people > prefer otherwise. Perhaps something like pull-request-mailer could be used to tend to both camps? I.e., sending out github pull requests to the mailing list for review: https://github.com/google/pull-request-mailer Anyway, for me personally (as a DPDK outsider), what I feel would be the main improvement with using github would be that they have a very well-integrated bug reporting system that keeps track of e.g., the commit that fixes the bug etc. I recently submitted a build issue to the mailing list, which Olivier Matz promptly fixed with a patch (but which haven't been merged as far as I can tell). In the gihub workflow, I'd submitted a bug report ("Issue #13" for example), Olivier would have fixed this through a merge-request ("Issue #13: scripts: fix relpath.sh output when build dir is a symlink") and I'd acked that fix in the bug report. When the merge request was merged to the git repo, the bug report would be closed. I'm also interested in the architecture discussions etc (or the github debate!) on the list, but I really don't read patches sent to the list. So if I had a vote (which I shouldn't have :-)), I'd vote for a gradual move to github and a mailing list split. // Simon