From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 233E812A8 for ; Tue, 5 May 2015 18:43:20 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP; 05 May 2015 09:43:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,373,1427785200"; d="scan'208";a="721066669" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by fmsmga002.fm.intel.com with ESMTP; 05 May 2015 09:43:10 -0700 Received: from orsmsx154.amr.corp.intel.com (10.22.226.12) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 5 May 2015 09:43:10 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by ORSMSX154.amr.corp.intel.com (10.22.226.12) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 5 May 2015 09:43:09 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.26]) by fmsmsx156.amr.corp.intel.com ([169.254.13.121]) with mapi id 14.03.0224.002; Tue, 5 May 2015 09:43:09 -0700 From: "Wiles, Keith" To: Neil Horman Thread-Topic: [dpdk-dev] GitHub sandbox for the DPDK community Thread-Index: AQHQhCdlg1RCyqklQ0KpSAVz9bdNYJ1skjqAgAAoJICAAHjOAIAAsDcA//+5cHg= Date: Tue, 5 May 2015 16:43:08 +0000 Message-ID: <0CA4031C-561F-4BB9-8B14-674D6D99EE6E@intel.com> 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> In-Reply-To: <20150505135542.GB27259@hmsreliant.think-freely.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" 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: Tue, 05 May 2015 16:43:21 -0000 Sent from my iPhone > On May 5, 2015, at 6:56 AM, Neil Horman wrote: >=20 >> On Mon, May 04, 2015 at 10:25:00PM -0500, Jim Thompson wrote: >>=20 >>> On May 4, 2015, at 10:12 PM, Wiles, Keith wrote= : >>>=20 >>>=20 >>>=20 >>>> On 5/4/15, 10:48 AM, "Matthew Hall" wrote: >>>>=20 >>>>> On Mon, May 04, 2015 at 12:43:48PM +0000, Qiu, Michael wrote: >>>>> What mail client do you use? I think mail client supporting thread m= ode >>>>> is important for patch review. >>>>=20 >>>> Like many UNIX people, I use mutt. >>>>=20 >>>> My concern is that, if we're making the widespread adoption, usage, an= d >>>> contributions for DPDK dependent on selection or debate of the feature= s >>>> of=20 >>>> various MUAs, I'm not sure that we're looking at this from the right >>>> angle. >>>>=20 >>>> I'm just trying to figure out how to get DPDK in the place where the m= ost >>>> eyeballs are, rather than trying to drag the eyeballs to the place whe= re >>>> DPDK=20 >>>> is. >>>=20 >>> +1, I agree with this statement completely and I feel discussions about= an >>> MUA is non-productive and out of scope. >>=20 >> +1. I=92ve avoided the whole discussion, because =85 ok, =93non-product= ive and out of scope=94 is a polite way of saying it. >>=20 >> jim >=20 > Very well, since you seem to want to avoid talking about ways to get what= you > want in a workflow, lets go back to where the conversation started: >=20 > http://dpdk.org/ml/archives/dev/2015-May/017225.html >=20 > We got into this debate because you wanted to move the project to github,= and as > supporting reasons, listed a plethora of features that you liked about th= e site. > This entire subtread has been meant to illustrate how you can have the fe= atures > you want that you see as adventageous in the github environment without a= ctualy > moving to github. We've focused on email quote collapsing because we kep= t > responding to one another, though I'm sure we could have the same debate = on any > one of the workflow features github offers. >=20 > Can we all agree then, that for the list posted in your email above, any = github > environmental feature can be recreated with proper tooling, available tod= ay, > without forcing the github environment on everybody? Further, can we agr= ee > that, given that those features are not unique to github, they are not > compelling reasons to move the project there? Neil (I had to type this on my phone so please forgive any typos or other s= tatements that may sound odd. I am not trying to be rude in anyway) I feel you are taking everything out of context here. The email client bein= g able collapse threads is not the point here and I have tried to redirect = you politely to the points moving DPDK to github.=20 As I and others have pointed out GitHub offers a huge number eyes for DPDK = community. GitHub offers a different set of processes and tools, which we d= o not have to create. Moving to GitHub is a change for the community and I = feel a good change for the better.=20 For your statements above I say NO we do not agree as much as your argument= s around a single feature of an email client is not a compelling reason to = accept your statements.=20 Github gives us the DPDK community a better and more widely accepted place = to allow DPDK to grow and become the open source project we all want IMO.=20 I want to be polite here and we are not going to agree with keeping DPDK as= it is today. We need to grow and change is the only way, I believe moving = to GitHub gives the best support and eyeballs on DPDK to grow.=20 The tools supported on GitHub are different and yes you may need to change.= The day to day development will remain the same and as we know that is the= bulk of the work. The pushing of patches will change, which should be easi= er for move people to understand plus use.=20 We could spend a lot of time and money to update the current system, but wh= y when we could start the move to GitHub today and use those tools for free= .=20 I do not want this to become a flame war or something like it. I want us to= try and figure out how we can improve the DPDK community. I can see keepin= g DPDK the way it is today, but this will stagnate DPDK IMHO and no one wan= ts this to happen.=20 I do not want to split the DPDK community or try alienating any one.=20 Please take a breath and relax as we all want the best for DPDK.=20 Regards, ++Keith >=20 > Neil >=20