Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
Akretion, Raphael Valyi
And ideally the two worlds still collaborate on the LGPL core. Well this is is for me the most worrying point still because that will only work if that master core is public and since a few weeks it has been secretly hidden from what we found. I've read Antony's justification about it, but I think just like Sylvain Legal said, I don't believe the hidden PR had anything to do with what Antony said and we still don't see the master branch moving forward anymore. Well if the core was hidden then of course instead of collaboration there would be a fork on the core, but as for now Odoo SA officially said it was just a technical glitch and there was no intention to not publish the core anymore, so let's wait and see if the git-filter is applied and if things are quickly merged into the master branch again so we can keep collaborating in that essential part.
There will be the AGPL world with all the modules we know and they will keep improving a lot and on the other side there will be another world with a few proprietary modules. If you like OpenERP/Odoo the way it is, you'll just choose that same AGPL world and you'll be just fine. If instead some people believe because of some marketing that they would be better in the other world with a the few proprietary modules, that's fine. I even think the clear separations of these two world will in fact have a pedagogical virtue quickly and will quickly educate the market to support better the AGPL initiative (OCA etc..) so it will just improve even faster than today, I only see advantages in this.
Hello community,I see a lot of negative reactions with people worried a lot. Well, I think it will do just well.
On Wed, May 13, 2015 at 7:52 AM, Anders Wallenquist <email@example.com> wrote:
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 >