Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
Eficent Business and IT Consulting Services, S.L.
Agreed, and I don't say in all cases all the contributors of a module would agree.
My point here is that with this dual licensing, an author code released under AGPL will stay forever as AGPL, and ensures that no publisher can benefit from creating a closed-source platform using the author's modules.
The author is who decides which customer segments can use (and only use, not sell or redistribute) her/his code in a context where AGPL would be problematic.
On Mon, May 11, 2015 at 10:43 AM, Alexandre Fayolle <email@example.com> wrote:
On 10/05/2015 10:08, Jordi Ballester Alomar wrote: > > Graeme, the OCA CLA states that the original author retains the copyright. > > Perhaps the author could directly submit the privately licensed code > (with special provision) directly to the end customer (through Odoo > web shop or any other), if he wants to help Odoo SA. > > For example, an author creates a module and both submits it to #OCA > and to a web shop under this private license. > > OCA and Odoo SA would remain out of the loop. It is resposability of > the original author to choose if he wants the customer to use his > module under Enterprise contract. > > The thing is, as soon as the OCA version starts to get contributions from people from the community, the author needs to ask these contributors for permission to relicense these under his private license. -- Alexandre Fayolle Chef de Projet Tel : + 33 (0)4 79 26 57 94 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com