Community mailing list archives
Re: Indiegogo: Upgrade Odoo Community Edition!by
Mr James Alfa
thanks for the response - I would like to insert a few followup questions in the text. Unfortunately a lot of these discussions about the implications go rapidly to philosophical arguments about perceived motivations, of Odoo, of 3rd party developers, of capitalism etc.
For people who want to know what can and cant be done with Odoo code it is virtually impossible to work out from all this confusion what is possible. If I list some typical scenarios it may clarify the situation
1) A programmer is considering writing some code and putting it on the Odoo Apps store. They would like to know if they can state 'you can only install this on one instance of Odoo'
2) A designer is considering developing a theme. They would like to know if they can buy an existing LGPL theme, modify it and then sell the resultant theme on the Odoo Apps store (or perhaps elsewhere)
3) A hosting company is considering offering a hosted version of Odoo and would like to bundle Odoo with (some AGPL + some LGPL) modules. They would like to know if they need to pay only once for each LGPL module or whether they have to pay 100 times, if they have 100 customers who host odoo instances with them
4) An end user is considering installing Odoo within their organisation, including hosting an external website for their customers. They have read about the requirements of AGPL and wonder what they have to do to satisfy the requirement that all visitors to their external website must be able to have a copy of the source code that their website is 'using' - they want to know if they are going to be in a position of being forced to spell out exactly to their competitors how they have created such a nice looking website - eg do they have to explain exactly which of the 6431 apps on the Odoo Apps store they are using, can they remove the 'made in odoo' message at the bottom of each webpage, etc etc.
These are all reasonable questions posed by different people coming to the Odoo platform for the first time. If we can clearly answer questions like these it will make it less likely that they will walk away in confusion.
Alfa Industrial Components
Litton House, Saville Road, Peterborough, Cambs, PE3 7PR, UK
Tel 03333 441658 Fax 03333 441659
On Sat, Nov 7, 2015 at 4:13 AM, James Fox <firstname.lastname@example.org> wrote:Correct it IS permitted to do that. Admittedly the original developers of the module would not be so happy, but they cannot stop you.
"Correct it IS permitted to do that. Admittedly the original developers of the module would not be so happy, but they cannot stop you."James I would be very careful with that. The GPL licenses say very clear that license changes can ONLY take place if ALL people who ever contributed to this code agree with a license change. In other words it has to be AGPL and if it has to be AGPL it can be simply copied and rereleased as Free like free beer with Free like Freedom in mind to everybody in the community!I guess after the THEME indiegogo campaign we should better invest in the Free Mind instead of contributing to people who are nothing else than money collectors!Of course there is nothing wrong with the Odoo ecosystem having many distribution channels. We're not talking about Apple here ! Odoo is an open source platform, which I believe means that all and every odoo module written must be either LGPL or AGPL licensed as they all have to use the AGPL licensed kernel to work and that was developed by all those fine previous programmers that have written it and released it to the world on the basis that the system keeps its open source capability via copyleft provisions. The introduction of LGPL does not suddenly transfer microsoft style licensing rights to module developers - i.e. you may only use this on one machine, you may not see the source code and you certainly cannot modify it,