User: Password:
|
|
Subscribe / Log in / New account

The next GPL: Why it's being shaped on GitHub (InfoWorld)

The next GPL: Why it's being shaped on GitHub (InfoWorld)

Posted Jul 8, 2012 5:10 UTC (Sun) by jra (subscriber, #55261)
Parent article: The next GPL: Why it's being shaped on GitHub (InfoWorld)

It's license proliferation, no matter who is doing it (and I like Richard a lot).

http://google-opensource.blogspot.com/2008/05/standing-ag...

IMHO the best thing to do is ignore it, and hope it dies a deservedly ignominious death.


(Log in to post comments)

The next GPL: Why it's being shaped on GitHub (InfoWorld)

Posted Jul 8, 2012 5:50 UTC (Sun) by rahulsundaram (subscriber, #21946) [Link]

Licensing proliferation only becomes a problem due to incompatibilities. There are dozens and dozens of revised BSD variants and nobody is bothered about them for instance. As long as copyleft.next has the compatibility provisions or better yet, becomes a successor to GPLv3 in some way, there isn't a reason to shoot it down just yet.

The next GPL: Why it's being shaped on GitHub (InfoWorld)

Posted Jul 8, 2012 13:28 UTC (Sun) by rfontana (guest, #52677) [Link]

There may be multiple valid concerns about license proliferation, but the concern about introduced license incompatibilities is certainly one of them. The experimental Copyleft.next license document is already compatible with all present and future versions of the GNU GPL and GNU AGPL and all licenses compatible with those licenses (with one marginal category of exception). One GNU GPL-incompatible license I'd like Copyleft.next to achieve compatibility with is the Eclipse Public License 1.0, but I think this will require an approach somewhat like that taken by MPL 2.0 or by GNU GPLv3/AGPLv3 to achieve cross-compatibility.

The marginal category of exception is the set of GNU GPLv3 + limited badgeware licenses; Copyleft.next is currently designed to remove compatibility with such terms. A notable example is the license of SugarCRM Community Edition.

The next GPL: Why it's being shaped on GitHub (InfoWorld)

Posted Jul 8, 2012 13:30 UTC (Sun) by rfontana (guest, #52677) [Link]

Actually you could get around that by relicensing under GNU GPLv3/AGPLv3, I suppose. I'm not sure if that's a bug or a feature.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds