On Fri, May 13, 2011 at 12:34 PM, Thomas Weholt <thomas.weh...@gmail.com> 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? >
BSD license allows the most re-use of your work. If you want your code to be used by as many people as possible, use the BSD license. GPL license is almost as permissive as a BSD license for web server deployed packages, since a user is never distributing the library, only utilizing it to generate content. There is the Affero GPL, which disallows this behaviour. If you use this license, then anyone using your library must make their code AGPL as well. This would lead lots of potential users to not use your work. The choices are up to you Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
