[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libbitcoin license - AGPL with clauses added by SFLC and FSF

Quoting Turkey Breast (2014-05-21 14:22:23)
> I've made a Bitcoin library, and am seeking inclusion into Debian. We 
> (me and the mentor) are seeking guidance going forwards over a license 
> issue.
> The basic issue is that this project uses an AGPL license with several 
> additions, which we were given to me by the SFLC and vetted by the 
> FSF. They fix an issue with the AGPL which is unique to Bitcoin 
> (ability to distribute the source code when using a service), add a 
> lesser clause and an OpenSSL exception (although we are currently 
> transitioning away from OpenSSL).
> The full text is here:
> https://github.com/libbitcoin/libbitcoin/blob/master/LICENSE
> Emails from SFLC and FSF:
> https://wiki.unsystem.net/index.php/Libbitcoin/License
> Explanation of why this is necessary:
> http://lists.dyne.org/lurker/message/20140513.150838.39b61dfb.en.html
> http://lists.dyne.org/lurker/message/20140513.153343.b480ed75.en.html
> Debian developer's (Jonas is in CC) grievances here:
> https://github.com/spesmilo/libbitcoin/issues/5
> Anyway if the issue is intractable, we can migrate to vanilla LGPL for 
> inclusion into Debian. But I'm seeking here guidance on the best path 
> for everyone in terms of software quality and our users.
> Here is the relevant ITP Debian bug report with discussion:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670701

I notice now an update to the license done in December 2013: 

I apologize if you've already brought that change to my attention - I 
had the (wrong) impression from both debian and upstream issue trackers 
that licensing had _not_ been changed to reflect the concerns I raised 
and which it seems Richard Stallman agrees with me about.

Great.  Let's move on...

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

Reply to: