Contributors mailing list archives
Re: Licence of version 9.0 modulesby
InitOS GmbH, Frederik Kramer.
Hi all, i think this issue can't be discussed enough since it is crucial to the core values of the OCA. Although, both licenses are open source, there is a huge difference between AGPL and LGPL, whereas AGPL is a strong copyleft license and LGPL is a week copyleft one. Having said so, given the architecture of Odoo you could built fairly few and minor things on top of a couple of hundred Odoo modules which are LGPL licensed and built an entirely proprietary product with just one proprietary module and a few lines of code and if you just used the LGPL as is, you would be perfectly fine. The tendency for that is already happening since the very moment the base modules of Odoo have been put under LGPL. I personally don't think that this will solve any of the problems of our customers that may at some point have or will decide to move from proprietary products to open ecosystem such as Odoo but it will only shift the scope of the entirety of the ecosystem to trying to monetize a sample of modules and create what i often call vendor lock-in 2.0 just by attracting and locking in some fools. The "degree of openness" (given the actual AGPL standard in the OCA modules) and the very fact that there are strong technology partners around the globe helps the ecosystem to flourish by shareing, not the ability to built contemporary lock-ins. Most of the successful OCA Odoo partners are successful because they help their customers to transform their businesses into digitalized business, hence fueling the digital transformation. So i think the lock-in of every OCA member and user shall be solely the knowledge / expertise / processes and reputation he or she has built over time. An no, i am not one of the RMS kind of folks, saying that strong copyleft is always the one and only solution. So long, kind regards and sorry for the long statement, that some may oppose against Frederik Am Mittwoch, den 14.09.2016, 13:23 +0000 schrieb David Dufresne: > Thank you all for your answers. > > My intention was only to take the pulse of OCA on this matter. I am not myself in favor of using LGPL. > > I think the position of OCA is clear. Sorry if it seems like a redondant subject that has already been discussed. > > Regards > > David Dufresne, Consultant en logiciels libres > Savoir-faire Linux > > Téléphone : 418-525-7354 #156 > Cell : 418-271-0915 > Ring ID : 9ac472765d298cc5de294b5765d0ccfaec48cbbf > www.savoirfairelinux.com > > ISO 9001 et ISO 14001 > > ----- Original Message ----- > From: "Graeme Gellatly" <firstname.lastname@example.org> > To: "contributors" <email@example.com> > Sent: Wednesday, September 14, 2016 7:53:49 AM > Subject: Re: Licence of version 9.0 modules > > Do not forget the practical considerations, like that many modules came out of extra-addons, some original authors might not have CLA etc. Think what Odoo had to do for allegedly just 2 pct of their codebase just to relicense. That's with full commit logs and history. Now imagine that task across the OCA universe. > > On Wed, 14 Sep 2016 10:40 PM Ronald Portier < firstname.lastname@example.org  > wrote: > +1 Completely agree with Stefan. > Op 14-09-16 om 12:23 schreef Stefan Rijnhart: > > On 14-09-16 00:38, Eric Caudal wrote: > >> > >> AGPL and LGPL are to fairly open source licenses AFAIR ;) so we would > >> not slipping into the "proprietary" world yet > >> > > > > Well, a module licensed under LGPL allows a proprietary module to be > > built on top of it. It gives these proprietary modules a distinct > > competitive advantage over their open source dependencies and lowers the > > return on investment in these open source contributions, which is why I > > strongly prefer the AGPL for OCA modules. > > > > Regards, > > Stefan. > > > > -- > > Opener B.V. - Business solutions driven by open source collaboration > > > > Stefan Rijnhart - Consultant/developer > > > > mail: email@example.com  > > tel: +31 (0) 20 3090 139 > > web: https://opener.am  > > > > _______________________________________________ > > Mailing-List: http://odoo-community.org/groups/contributors-15  > > Post to: mailto: firstname.lastname@example.org  > > Unsubscribe: http://odoo-community.org/groups?unsubscribe  > > > > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15  > Post to: mailto: email@example.com  > Unsubscribe: http://odoo-community.org/groups?unsubscribe  > > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: http://odoo-community.org/groups?unsubscribe > > >  mailto:email@example.com >  mailto:firstname.lastname@example.org >  https://opener.am >  http://odoo-community.org/groups/contributors-15 >  mailto:email@example.com >  http://odoo-community.org/groups?unsubscribe >  http://odoo-community.org/groups/contributors-15 >  mailto:firstname.lastname@example.org >  http://odoo-community.org/groups?unsubscribe > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15 > Post to: mailto:email@example.com > Unsubscribe: http://odoo-community.org/groups?unsubscribe > > > -- Dipl.-Wirt.-Inf. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: firstname.lastname@example.org Web: www.initos.com Geschäftsführung: Dipl.-Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/205/21518 USt-IdNr.: DE815580155