git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Brandon Casey <drafnel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: permission to re-license strbuf subsystem as LGPL
Date: Fri, 23 Sep 2011 17:16:11 -0500	[thread overview]
Message-ID: <20110923221611.GA2548@elie> (raw)
In-Reply-To: <CA+sFfMcmsKkKM7C0g4vKmjmCCNqRHuvz-hwEHAm=+stqnOPpAw@mail.gmail.com>

Brandon Casey wrote:

> Jonathan Nieder suggested using a more permissive license than LGPL.
> BSD seems to have the most support.  If the remaining contributors
> agree, then I'm fine with licensing under BSD.

A few words of clarification.  My opinion shouldn't matter much here
--- I am more of a bystander and user than a contributor to strbuf. :)

The main reason I suggested a permissive license is that the strbuf
lib contains some inline functions and I do not want it to be
complicated to use them.  To comply with the LGPL, in addition to
releasing any changes made to the library, distributors usually do one
of a few things:

 a. offer the source code for your work that uses the library in
    addition to any binaries,

 b. use dynamic linking, or

 c. provide object files for your work that uses the library, so it
    can be re-linked against a modified version of the library.

(b) and (c) don't handle inline functions.  Luckily, there is a way out:

 d. only use the inline functions from within a subset of your work
    for which you are willing to provide source.  Dynamically link to
    it or provide object files to allow re-linking.

With that in mind, I have nothing against the use of the LGPL here
(and one of the two main authors of the strbuf lib explained a good
reason to prefer it over the BSD license).  The inline functions in
the strbuf lib are pretty small, so the above was probably not too
important in the first place.

Thanks, and sorry for the unnecessary noise.

Regards,
Jonathan

      parent reply	other threads:[~2011-09-23 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+sFfMeRDQiqGhO9Y=k3tEnzdXjMx59huFE_fx6Y14cJxj1J=Q@mail.gmail.com>
2011-09-23 15:01 ` Fwd: permission to re-license strbuf subsystem as LGPL Brandon Casey
2011-09-23 15:36   ` Michael Witten
2011-09-23 17:12   ` Fwd: " Jakub Narebski
2011-09-23 22:50     ` Brandon Casey
2011-09-24  6:05       ` Jeff King
2011-09-23 22:16   ` Jonathan Nieder [this message]

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=20110923221611.GA2548@elie \
    --to=jrnieder@gmail.com \
    --cc=drafnel@gmail.com \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).