From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 33A5E2E83 for ; Fri, 24 Apr 2015 19:53:02 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 329D980BD84; Fri, 24 Apr 2015 10:51:24 -0700 (PDT) Date: Fri, 24 Apr 2015 10:51:24 -0700 From: Matthew Hall To: Jay Rolette Message-ID: <20150424175124.GA30624@mhcomputing.net> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D1A917@IRSMSX102.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Beyond DPDK 2.0 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: Fri, 24 Apr 2015 17:53:02 -0000 On Fri, Apr 24, 2015 at 12:39:47PM -0500, Jay Rolette wrote: > I can tell you that if DPDK were GPL-based, my company wouldn't be using > it. I suspect we wouldn't be the only ones... > > Jay I could second this, from the past employer where I used it. Right now I am using it in an open source app, I have a bit of GPL here and there but I'm trying to get rid of it or confine it to separate address spaces, where it won't impact the core code written around DPDK, as I don't want to cause headaches for any downstream users I attract someday. Hard-core GPL would not be possible for most. LGPL could be possible, but I don't think it could be worth the relicensing headache for that small change. Instead we should make the patch process as easy as humanly possible so people are encouraged to send us the fixes and not cart them around their companies constantly. Perhaps it means having some ReviewBoard type of tools, a clone in Github or Bitbucket where the less hardcore kernel-workflow types could send back their small bug fixes a bit more easily, this kind of stuff. Google has been getting good uptake since they moved most of their open source across to Github, because the contribution workflow was more convenient than Google Code was. Matthew.