Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
Any thought about being more descriptive with the naming to avoid confusion?
If the Enterprise edition is simply a bundle of modules why make it sound like the core is different.
I fully support Odoo making paid modules but then why not name it "Enterprise Feature Pack" or "Enterprise Add-on" or anything to signify that the Odoo core is not involved.
Odoo Community addition sounds like a stripped down, vanilla version of Odoo Enterprise addition.
I really want odoo to succeed but please don't add fuel to the fire. Proudly present Odoo as a strong product and then confidently charge for Enterprise Module Features.
Just my two cents. I really don't want to be explaining the difference of the two versions for years in the forums.
On Thu, May 7, 2015 at 10:42 AM, Antony Lesuisse <firstname.lastname@example.org> wrote:
With version 9, we will release 2 editions of odoo: Odoo Community and Odoo Enterprise. Odoo Enterprise will consist of Odoo Community plus a set of enterprise only features (or in technical term, an additional repository with extra modules). Some new features that have been under developement latetly will be in enterprise such as electronic signature, integration with shipping providers. For example the crm_voip module (currently published as a paid app on the app store) will be in the enterprise repository. However core modules like the new accounting remains in the Community version. Odoo community will be supported as much as Odoo enterprise, Odoo Community is the foundation of Odoo Enterprise and it will remain free and open source as LGPL. For technical users, they can access the code through the same GitHub repository. The community version 9 will be at odoo/odoo#9.0 and the development branch is still at odoo/odoo#master. Odoo Enterprise users (and partners) will have access to the enterprise repository containing only the additional modules. You might have wondered why odoo master has not been pushed for a few weeks. The reason is that we had some feature branches with those extra modules, we did not want to push the merged branches as LGPL. We are currently filtering the branch with git-filter-branch before we can push it back to master. Antony.