Community mailing list archives
Re: FW: access to code under AGPL v3by
Camptocamp SA, Joël Grand-Guillaume
If you trust us, then leave this endless topic ;)
If the OCA CLA states that we can change the license, sure one day it might happen that some contributions are re-licensed. But it won't be made lightly, because the essence of the OCA is to serve and defend the contributors interest. If you don't trust that, then please let us be and pass your way.
If the OCA states in the CLA (or bylaws) that we can't change the license chosen by our contributors, we take the risk that in the future, Odoo relicense in an incompatible license and then no module from OCA can be used anymore.. That is not what all people trusting the OCA want. They want to be sure they can rely on OCA work what ever the future might be (even if some contributors are dead).
Hi,First thanks Graeme for your input here, I'm +1 for all what you say. Our CLA is entirely taken from
On Mon, Jan 25, 2016 at 2:22 PM, Ronald Wopereis <firstname.lastname@example.org> wrote:
i wonder what is worse(a) someone wanting to steal my code(b) nobody wanting to steal my codei was just looking at someone from the fashion business where creativity rules rather than ip.best regards, Ron2016-01-25 12:12 GMT+01:00 Andreas Becker <email@example.com>:On Mon, Jan 25, 2016 at 4:22 PM, Alexandre Fayolle <firstname.lastname@example.org> wrote:it won't happen any time soonThis implies that it might happen in future when i.e. a module will be needed to work together with proprietary parts ;-). The fact that most parts got not relicensed until now from AGPL to LGPL when moving to Version 9 is not a real sign as most modules until now have been set only as uninstallable - nothing more.But your statement clarifies the situation a bit more. Thanks Alexandre.It would be much better if everybody could contribute with all these constraints and fears.