Here are some of my rules of thumb: 1) If it is trivial, put it in the public domain (config files, etc.).
2) If you are trying to create a standard of some sort, use the Apache 2 license. 3) If you are trying to contribute to an existing community, use whatever license they use. 4) If you are trying to push software freedom, use the AGPLv3. 5) If you want to release code, but have some protection against competition, use AGPLv3. 6) If you want to play nice with the Free Software community, but want to make money off traditional licensing, use AGPLv3 or GPLv3 and ask contributors assign copyright to you so you can sell alternate licenses. As an example, I am using the AGPLv3 for my current project ( http://pagekite.net/) at the moment for reasons 4) (and a bit of 5 and 6), but am strongly considering a switch to a BSD style license at some point for reason 2). Other random points: Generally speaking, I prefer the more recent, modern licenses (GPLv3 instead of GPLv2, Apache instead of BSD) because they do a better job covering issues like patents. Some would argue that putting things in the public domain is "dangerous" because it doesn't explicitly disclaim liability. On Fri, May 13, 2011 at 11:52 AM, Tom Evans <tevans...@googlemail.com>wrote: > 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. > > -- Bjarni R. Einarsson The Beanstalks Project ehf. Making personal web-pages fly: http://pagekite.net/ -- 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.
