It will partly depend on who you would like to be able to use your code.
The corporate mandate at my previous employer, a very large software company, was "No GPL". LGPL was tolerated, but not encouraged. The reason for the mandate was that GPL required the user to also make their code available, which is not what this software company wanted. This was a few years ago, so the situation may have changed, but I'd expect it hasn't.
Cheers, Alistair On 13/05/11 13:34, Thomas Weholt wrote:
I've released three django-related packages the last few months, all under the GPL license. Recently somebody asked me about my license choice; "Why not BSD, the same as django?". My reason for choosing GPL is based on the fact that I'm a strong supporter of free software as defined by FSF and GPL is the de facto standard license for that. But the question got me thinking and I wonder what kind of problems I might run into using the GPL, and not the BSD license. Do people really care? Should I care? I think so. What do you people think; How to choose a license and why?
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
