Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
- about how they empower their community and play a role in the recognition of the good modules.
+1 to Anders (again)
I think it's not the right approach to try to find any workable solution to deal with this mess. Why would anybody who did not create this situation (Community, OCA) try to comply to the one that puts the fundamentals at stake (S.A.)
Did nobody ever hear the term "identification with the aggressor" before? That is in my eyes what trying to find whatsoever friendly compromise in order to satisfy the needs of S.A. in this matter basically comes down to.
First and foremost the Community should be clear that an attack is being conducted. And that does not require a 'friendly' response I think. The one being attacked should defend itself (or the idea that is to be protected).
On 5/13/2015 6:52 PM, Anders Wallenquist wrote:<blockquote cite="mid:55532C82.email@example.com" type="cite">
Den 2015-05-12 18:39, Alan Bell skrev: > On 12/05/15 15:58, Christophe Hanon wrote: > > I think a licence checker based on dependencies would be great... > > > > Regards, > > > > Christophe > > > my favoured solution too, if we can all agree that in the context of > Odoo, the best way to interpret the license in terms of the meaning of > derivative works is through dependencies then it could be set so that > pretty much anything can depend on LGPL modules, GPL or AGPL can depend > on GPL modules and only AGPL modules can depend on AGPL modules. This > dependency rule can be implemented in the code and we could have a > facility to automatically provide the source > of the AGPL bits. > > Can anyone see a downside to this? Well to implement a licence hell are fundamental wrong. If Odoo SA wants that Odoo still be a star in free software area the cost of a licence hell will kill the community and the product in the long run. To "sell" Odoo to new customers you have to look at each module and calculate if they will fit together in a licence matter. To create a qoutation sometimes a couple of hundred modules have to work together. It's not enough that you know its right functionality and you know by experience it right for the case, you have to know if any of the other modules disqualifies the use of this module in this case. Even if you have automatic checks at installation time it will not work. You'll have to build the installation before you can create a quotation. You have to educate your customer what modules they can use and what they cannot and why overtime when they want to grow theit business with Odoo. No if Odoo shall remain as a free software product as we know it has to have compatible licences in all modules payed or not. Odoo SA have lost the perspective in this new strategy, this is incorrigible stupid and amaturish. I understand what they want - but the implementation sucks. Regard, Anders Wallenquist > > Alan. > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: https://www.odoo.com/groups?unsubscribe >
Gunnar Wagner | Iris Germanica Ltd. | JinQian Gong Lu 385, 8-201 | FengXian Qu, 201404 Shanghai | P.R. CHINA
+86 159 0094 1702 | +49 (0)176 7808 9090 | skype: professorgunrad | www.fashionsupermarket.net