Community archivos de la lista de correo
Re: Odoo 9 Accounting: We support your bankpor
Pedro M. Baeza
Answering you, I think your interpretation is wrong. You can replace enterprise features by developing them by yourself, while you don't use any of the code provided by Odoo, even if you have access to this code and have read it. If the feature is very straight-forward, there are chances that the code can be similar, but for sure this doesn't mean that they have the copyright of it or they can issue a demand against you. There's jurisprudence already about some popular cases (like Java vs Android), that have settled a good base about how to define something as copied.
Hi, Ondrej,The mail you have sent has not been replied by OCA because the address you have sent to is not the proper one (that one is for reporting a bug, a website typo or a technical problem), and it is not checked by all the board.
If you think about it, the problem is the same in open source, but with the ownership attributions. There are already cases in Odoo of people copying AGPL code and changing the author . These cases are very simple to check that there have been a verbatim copy. In other cases, some people have developed by their own the same feature/functionality, and also offer it as open-source, and there hasn't been any infringement. Look for example the module for changing the favicon: all have this module developed by their own, including me!
2015-10-05 10:49 GMT+02:00 Ondrej Kuznik <firstname.lastname@example.org>:
On 05/10/15 08:43, Alexandre Fayolle wrote: > On 04/10/2015 12:33, Richard Achatz wrote: >> Hi Fabien, >> >> i think we talk past each other. please follow me. >> >> if i developed a custom addon for 8 which depends on, or is based on >> appraisal in HR and want to upgrade to 9, i will have to do massive >> changes on my code or upgrade to enterprise. > > You may also consider porting the AGPL code of these modules from v8 to > v9, and maybe propose these ported addons to the Odoo Community > Association. And there you come across another issue: If you are a partner or enterprise customer, or otherwise have ever had access to the proprietary code, you cannot develop a replacement for that functionality and if you do, Odoo can send you a nice letter to cease and desist distribution of that code as it would be infringing on their copyright (and you really have no way of proving otherwise). That in my eyes is the greatest danger of Odoo's move to open-core, even if they decide to tolerate this practice, there is no telling whether one day they will decide to stamp out all the competition. Or should Odoo be acquired by an Oracle-like entity that decided to shut down new development on the community edition, no partner would effectively be able to extend it anymore, effectively killing off the LGPL version in one fell swoop by eliminating its potential developers through this legal uncertainty... I have voiced this concern with OCA last week, but so far there has been no reply to my email to email@example.com. And please do not take this response as spreading FUD, this is a real concern and it would be nice if Fabien or someone in the know commented on this. Regards, Ondrej