On Friday, May 13, 2011 07:34:35 am 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.
The big problem with the GPL is that it requires source code disclosure, so people who want to include your code in a commercial product feel like they are giving away the farm instead of selling some eggs. Look at it this way: If you want to force contribution back to your project, then AGPL or GPL3. This limits participation of people who want to use your code in their products or SAAS services because it forces them to release their customizations for free. If you want to allow SAAS, but ensure that people can get access to code, use GPL2 or if appropriate LGPL. If you don't care and just want to share and share alike, look at BSD or many other more permissive open source licenses. If you want businesses to pay you, but individuals to be able to use your software, Creative Commons has a few good, tested licenses. If you want to get paid every time someone installs your software, use a commercial license. > > Do people really care? Should I care? I think so. What do you people > think; How to choose a license and why? -- Mike Seidle -- 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.
