Community mailing list archives
Re: Enterprise: Is it allowed to use AGPL community modules?by
Libertus Solutions, Alan Bell
On 05/10/15 17:27, Dominique Chabord wrote: > Alan, > > "it is as simple as that" > - may I point you to http://www.law.washington.edu/lta/swp/Law/derivative.html > > as you can read it is everything but simple. A court is the only one > entitled to answer about what "dependency" means. yup, read that and many many other things on the topic! Most of the GNU/FSF/SFLC stuff is written from a perspective of compiled code and translated into legalese. The python stuff we are using isn't compiled (kinda, I know about .pyc files) and doesn't perfectly fit the model, and you are absolutely right that defining what is a derivative could end up deciding things along some kind of line. The thing is we have a perfectly serviceable existing mechanism where all modules already define what other things they must have in place in order to be loaded. It is pretty clear that if another module is being depended upon then you have a derived work because your code would be useless without the dependency. The situation is somewhat covered in the GPL FAQ https://www.gnu.org/licenses/gpl-faq.html and there was a stack exchange discussion about that general scenario here http://programmers.stackexchange.com/questions/110380/call-gpl-software-from-non-gpl-software and yes, there will be as many opinions as there are participants, but I completely agree with the OCA/ODOO meeting conclusions and the diagrams here https://odoo-community.org/blog/oca-news-1/post/oca-odoo-meeting-on-licenses-21 Alan.