For now trunk only. This will propagate to stable since 1.91.1 Reason for the change?
- Eliminate some ambiguities with the current license + exception - Allow web2py to incorporate Apache code if needed (Google releases under Apache) - Give you the ability to use web2py modules in non-web2py apps (the new dal for example) - Expand the user base What does it mean for you again? - If you simply use web2py to develop web2py apps nothing changes. The LGPLv3 just makes more clear than the GPL+exception that the web2py license does not extend to your app but only to the web2py libraries, even if you import web2py libraries in your app. You can release your apps open or closed source under any license you like, with or without official web2py code, whether source or binary. - If you want to use web2py modules into non-web2py apps - for example use dal.py or template.py with a different framework, you can now do so without worries, as long as you do not change the source of the web2py modules. You simply need to state that your app includes web2py modules. - If you need to modify web2py code you have to release the modifications under LGPLv3 (before you had to release modifications under GPL2). What you cannot do is what you could not do before: modify web2py, include it a commercial product or closed source product and not release your changes to web2py open source. Merry Christmas
