> 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.
Well, I think that's my main motivation for releasing my code as GPL; people are free to use it, modify it, redistribute it, even sell it as part of a larger piece of software, but the only thing I want in return is that their modifications of "my" code are made public for me to use as well so I can benefit from bug fixes, added features etc. So I still believe GPL is the right license for me to use. -- Mvh/Best regards, Thomas Weholt http://www.weholt.org -- 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.
