Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
Le 10 mai 2015 à 12:07, Raphaël Valyi <email@example.com> a écrit :And we should trust blindly Odoo SA and give up our AGPL contractual warranty on the OCA modules that is our own community work?So after some loud questioning from the community during an embarrassing silence of two days, we see these improbable justifications from Odoo SA and here are we discussing again about how the community should accept anything to please the profitability of the original editor which is now obviously doing policies under the effective control from some liquid VC money.And now that the license could legally be changed on the core, BY ACCIDENT some community developer at Camptocamp detected that the master Github repository has been discretely hidden for several weeks...At the beginning of 2015, the AGPL license was attacked and a move to a permissive LGPL license for the core was announced. Contributors got threatened to have their contribs removed if they did not sign a CLA for the core and finally nearly everybody ended up signing that CLA under the business pressure. At that time Odoo SA was presenting signing the CLA as a business trade off that would enable Odoo SA not going closed source for 18 months before hypothetically publishing the code again.Between 2014 and 2015, Odoo service pricing has been extremely volatile, changing with factors like 3x back and forth on some combos in totally chaotic ways... Just in France it seems some 50 partners have been hitting the road in the meantime...At the beginning of 2013, version 7 was launched in the air with a fancy new website "sorry SAP". That looked like if all the community aspects of the software where removed and OpenERP just turned into one more single vendor SaaS software that would now compete with SAP (hahaha)... And yes, the campaign was ridiculous and it had to backpedal later because it was totally out of target.Take a step back and see what has been happening over the last couple of years:So do you want to sign that blank check?Basically moving away from AGPL is a matter of trust: it's moving away from the contractually safe and sustainable AGPL world (it's at least sustainable for the OCA players and that's enough today) toward a unsafe world where a business failure from Odoo SA or just some greedyness eventually would expose the users and the integrators to an unlimited closing of the code and the future development process.Hello community,I also would like to highlight an other point: TRUSTSurprisingly however, not everybody found the campaign ridiculous because Sofinnova, Xange and SRIW VC's put another 10 millions USD into the company. But don't worry, only good things were to expect from that investment.A few months later during 2014, OpenERP was surprisingly renamed Odoo overnight. It was publicly promised that the code will always remain open source and the traditional blablabla dance from open source projects receiving extra venture capital.
I mean no offense, but come on...On Sun, May 10, 2015 at 5:10 AM, Jordi Ballester Alomar <firstname.lastname@example.org> 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.
If Odoo SA close the source, they can't redistribute OCA modules, because they were never given to Odoo SA but tobhis customers.
Just trying to help here.