All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
	Hefty Sean <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-core] Improve global COPYING files
Date: Thu, 29 Sep 2016 11:53:31 -0400	[thread overview]
Message-ID: <57ED38FB.4060006@redhat.com> (raw)
In-Reply-To: <20160923174848.GC13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2174 bytes --]

On 9/23/16 1:48 PM, Jason Gunthorpe wrote:
> On Fri, Sep 23, 2016 at 05:23:29PM +0000, Hefty, Sean wrote:
> 
>> If this combined repo is intended to support the plumbing for the
>> linux-rdma subsystem, then I think it must support code that is
>> submitted under GPL only.
> 
> Hum, I don't think that follows.
> 
> My expectation in the kernel is that the entire RDMA subystem and
> drivers follows the overall licensing model of the kernel and does not
> require userspace to follow any specific license, and certainly does
> not require userspace to follow the GPLv2.
> 
>> Much of the tradition code can remain dual-license, but new provider
>> code, for example, should be submit-able under GPL.
> 
> I do not support that recommendation.
> 
> The FSF has made very clear their position on GPL licensing of plugins
> (see https://www.gnu.org/licenses/gpl-faq.en.html), and allowing a
> GPLv2 only plugin or library code would break our community's promise
> to our customers - that the library core is usable in any application.
> 
> It would be a complicated discussion if someone proposed a GPLv2 only
> provider.
> 
> A LGPLv2-only provider would be more acceptable, and I would encourage
> anyone who wishes to have the protections of the GPLv2 in their
> provider to go that route. I suspect it would still be controversial.
> 
> I would prefer to see us continue with the dual license approach, and
> obviously all OFA member companies have agreed to do that.

I agree with Jason here.  Dual license or at least LGPL is needed on
providers because they will be linked to by other programs.  Libraries
shouldn't taint user programs.  But we do have some leaf code in the
overall rdma-core repo.  Things like iwpmd and ibacm.  These could be
licensed GPL only and still be OK.  So I think it's OK for the repo to
support GPL only, we just have to be clear about the fact that GPL only
is not the default as this repo is more about libraries than leaf utilities.


-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>    GPG Key ID: 0E572FDD
  Red Hat, Inc.
  100 E. Davie St
  Raleigh, NC 27601 USA


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 907 bytes --]

  parent reply	other threads:[~2016-09-29 15:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23  4:13 [PATCH rdma-core] Improve global COPYING files Jason Gunthorpe
     [not found] ` <20160923041340.GA11269-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23  8:06   ` Leon Romanovsky
     [not found]     ` <20160923080655.GM4088-2ukJVAZIZ/Y@public.gmane.org>
2016-09-23 15:24       ` Jason Gunthorpe
     [not found]         ` <20160923152412.GB11269-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23 17:10           ` Leon Romanovsky
     [not found]             ` <20160923171003.GR4088-2ukJVAZIZ/Y@public.gmane.org>
2016-09-23 17:23               ` Hefty, Sean
     [not found]                 ` <1828884A29C6694DAF28B7E6B8A82373AB08E66F-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-09-23 17:48                   ` Jason Gunthorpe
     [not found]                     ` <20160923174848.GC13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-29 15:53                       ` Doug Ledford [this message]
2016-09-23 17:34               ` Jason Gunthorpe
     [not found]                 ` <20160923173421.GB13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-05 12:49                   ` Leon Romanovsky
     [not found]                     ` <20161005124939.GF9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-06  4:30                       ` Leon Romanovsky
2016-09-23 16:58   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A82373AB08E609-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-09-23 17:03       ` Jason Gunthorpe
     [not found]         ` <20160923170314.GA13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23 17:12           ` Leon Romanovsky
2016-09-29 16:00   ` Christoph Hellwig
     [not found]     ` <20160929160053.GA11879-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-09-29 16:16       ` Jason Gunthorpe
     [not found]         ` <20160929161659.GA774-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-29 16:26           ` Doug Ledford
     [not found]             ` <57ED40C8.901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-29 22:55               ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57ED38FB.4060006@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.