4 ms·
The Django ecosystem is almost entirely made up of BSD/MIT licensed software. My guess is that licensing this as LGPL is going to hurt its adoption. Jacob Kapl
by ipmb 13y ago
The Django ecosystem is almost entirely made up of BSD/MIT licensed software. My guess is that licensing this as LGPL is going to hurt its adoption.
Jacob Kaplan-Moss has a good talk on licensing here, http://www.youtube.com/watch?v=vhuF0oalOi8 http://www.youtube.com/watch?v=vhuF0oalOi8
- specialist 13y agoThanks. I'll watch. I'm utterly ambivalent about which license(s) to use for my open source projects. I'm happy to follow the consensus.
- mixmastamyk 13y agoTL;DR "The GPL is not appropriate for Django Apps. ...our community doesn't use it. If your code isn't 'bsd mit lgpl apache mpl' I can't use it." That's a statement with considerable consequences. I wish he'd spent more than 1.5 seconds on the explanation. I tend to like both the gpl and django.
- ra 13y agoI am not a lawyer. IIUC GPL is fine unless you want to make something that 'links to' the GPL licensed code, then the code you made has to be GPL as well. The way I understand that is if, in your python app, you 'import gpl_licensed_lib' ... then you are boud by GPL to redistribute your source under GPL. That would be OK, if you were permitted to sell GPL based software without giving away the source under GPL, which you are not. TLDR: GPL is infectious, which is great for protecting GNU software like Linux, but it also makes it complicated for people to build and sell commercial software on Linux. I build Django apps for clients, and I avoid any python library that's GPL only.