On Fri, May 13, 2011 at 12:13 PM, Thomas Weholt <thomas.weh...@gmail.com> wrote: > And the point you're making about the non-legal isssues are just as > important for me as I want to "use" the community to make my own > software better. Hmmm ... as one of those copylefters it's somewhat of > a bitter pill to swallow not to use the GPL. Still - I'm a > django/python-user and if I want to succeed and increase my userbase I > might have to put the thinking and philosophy that got me into linux > and open source initially aside and use a license most compatible with > the framework and community I want to contribute to.
I went through a similar process with the Lua community: first i released several code snippets in GPL, but soon saw that most old-timers used MIT. The reason is that Lua is heavily used in the game industry, so very few people could use GPL'ed code. since i hadn't invested too much time (yet) i switched licensed, with the reservation that i'd use GPL if i started any 'big' project. but with time, and knowing a little more about the people there, i found that some of them worked with big companies, and even them tried to always contribute back to any OSS project they were using. of course, the community is very small, so the 'honor system' works very well. in the end, i found myself using MIT for everything Lua-related that doesn't start as a paid work. On other spaces (mostly C and C++), i still use GPL; but my presence there is far smaller. -- Javier -- 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.
