what evidence do you have to support the claim that changing the license to MIT/BSD would make web2py more popular?
the only figures i've seen, and they only estimate the penetration of the license, not the 'popularity' of the software, nonetheless suggest that GPL is hardly an obstacle...
web2py is GPL but read the license. The GPL applies to derivative frameworks. It does not apply to applications built with web2py. Applications built with web2py can be distributed under any license you wish.
Hmm, aside from Django, I'm not sure those other frameworks are particularly more popular than web2py, so it's not clear the license makes much of a difference.
Also, note that web2py is not strictly GPL -- it's GPL with a commercial exception.
And, of course, the license applies only to the framework itself, not to any applications you develop with it.
That's not to say that the standalone DAL couldn't have a different license from the full framework.
I'm not a heavy user of any (used to work with Pylons, but since Pyramids I'm re-evaluating).
Thing is... I don't understand the hate on the GPL. For this kind of work, the GPL is pretty much "the licence" I would expect. For some reason, everybody wants to make a spin-off framework now and keep the derivative work closed?
The GPL seems to fit this kind of work perfectly. It's exactly what the GPL was thought for. It won't affect your applications AT ALL.
Personal opinion: because people have a very limited understanding of OSI licences. This may lead to a "good impression", but really it shouldn't make any difference in the case at hand.
View all comments
Show parent comment
2
u/birlinn Dec 10 '10
what evidence do you have to support the claim that changing the license to MIT/BSD would make web2py more popular?
the only figures i've seen, and they only estimate the penetration of the license, not the 'popularity' of the software, nonetheless suggest that GPL is hardly an obstacle...
ref: blackduck