Community mailing list archives

Re: Odoo v9 Paid Apps

Wouter Tebbens
- 05/12/2015 07:46:08
Hash: SHA1

So, the question remains: why can the paid modules not be licensed
under a free software license, such as LGPL or AGPL? Aurélien, Anders
Wallenquist and others have suggested this before. Of course end
customers could request the code and publish it, reducing the income
potential, but it may prove to be a strategic choice to keep the Odoo
ecosystem together and thriving.

Also there's the option suggested by someone on this list (sorry, I
couldn't find it back in the thread) to put a time delay on this. Say
the paid apps are under LGPL but kept private the first say 18 months
and then they'll see the full daylight under AGPL. In any case there's
no license incompatibility and even more important: the code will be
free software.

That same person also suggested to sell the Odoo S.A: shares under the
community instead of depending on VCs: an interesting idea I must say.
Maybe the best one to achieve a solid integration of S.A. and the
wider community!

- -- 
best, salut, saludos, groet,

Wouter Tebbens
- --

On 05/12/2015 12:50 PM, Alexandre Vandermeersch wrote:
> Let me  clarify a few things about those decisions: 1. It's about
> our ambition to have the best & most complete business management
> software in the world - and it's a must have The size of the
> challenge is huge - a fully integrated product from CMS down to
> accounting, omnichannel (POS, Ecommerce, Salespeople).  For 
> instance on ecommerce, we will need to have a different sets of
> apps , themes to be competitive. And we think 'just' having
> connectors (eg with Magento) is not good enough and actually,
> doesn't work very well (we've tried).  In an 'omnichannel' world,
> where front & back are getting more integrated than ever, we simply
> have no choice than go that route.  For that great challenge we
> need a thriving open source community that contributes to great
> modules AND a funding system that provides some stability to a
> solid R&D staff AND a new community of developers/ Designers who
> can thrive on Odoo without being integrators (ie relying mostly on
> apps revenues).
> 2. It's about balancing the funding On that funding point, you
> might say that it's either for free or there is a lock in, and not
> everyone likes that. Yes, we will be moving the cursor a little
> because we think companies that can afford it should be paying a
> small amount for extended, advanced apps that required a 
> significant investment on our side.  But it's not a lock in,
> because there is still Odoo community, and the amount are way
> smaller than what many competitors do, and it's still pretty much
> about getting our services like migration, not simply apps.  As a
> note, you'd be surprised how little the VCs are involved in those
> decisions. We simply want to build a 'forever' company, based on a
> sustainable ecosystem & business model, and all the changes in the
> recent years were to find exactly that (and it's hard). The old
> version of '100% AGPL' + Odoo Enterprise contract did not enable
> that fully, so we reviewed it. We are now confident we are on the
> right model but it does not depend only on us, but on the community
> & our partners too.
> 3. Compatibility matters Having compatibility issues is a problem,
> not for Odoo Sa but for end users, who frankly don't understand
> much about the differences between all open source licenses (why
> would they care?). So we're coming again from an end user point of
> view. It's not Fabien's problem, it's the community's problem. We
> may say 'too bad' or we may say 'let's do something about it and
> find a solution so that our end users can have confidence in the
> whole ecosystem'. Contributors need their work to be respected, but
> they like it to be used too (it's good marketing & it's good
> recognition). Having barriers to usage is a problem for everybody. 
> Again, we are not taking anything away that was open source (from
> us or others) and moving it to paid. For all who signed a CLA with
> Odoo sa, their code will remain part of Odoo Community.
> So we definitely want to work with all contributors past & future
> to make it work, having in mind our collective ambition and most 
> importantly the end users. I think we are quite close and we'll
> take the opportunity of the upcoming Odoo Experience event early
> June to move forward constructively with all, followed up over the
> summer. Thanks Alexandre
> Le 12-05-15 10:04, Anders Wallenquist a écrit :
>> Den 2015-05-11 21:02, Fabien Pinckaers skrev:
>>> Do we want to say to VOIP module customers: "You can not use
>>> OCA modules because of license incompatibilities"?  No, the
>>> more people use the OCA module the more the OCA will grow.
>>> (even if those guys also use the VOIP module)
>>> Do we want to say to OCA users: "You can not use the VOIP
>>> module!"? If they want, why would you force them not to do it?
>>> If you are against paid modules, don't use it yourself, but
>>> don't restrict the others to benefit from them.
>> Fabien, it's not the OCA who is the problem, your problem is that
>> you got >5000 modules at and many more at
>> and github and other places that is AGPL and is not
>> OCA-modules and will be AGPL for many years ahead. Only on
>> you have a list of 500 companies that have
>> contributed to Odoo. Only in Sweden we have regular contact with
>> 50 more companies that have done contributions to Odoo and 
>> additional companies in Denmark, Norway and Finland not on that
>> list. Each company that contribute to Odoo are responsible to one
>> or a large quantity of end users using Odoo.
>> You try to speak with OCA as one entity because it's convenient,
>> but this is not the reality. You have pointed at AGPL for six
>> years now and to move from that will take time and with the
>> closed source-approach maybe never happen. There are just a small
>> if any incitements for contributors to change the licence on
>> their investments to a licence they not trust. Maybe it should
>> have been GPLv2 instead of AGPL, but AGPL are what you have
>> today.
>> You look at all those modules not compatible with closed source
>> as a problem. As long as you don't work with all those
>> contributions and contributors as a valuable asset you will
>> cripple Odoo in whole. Some people would say that those assets
>> are the most valuable asset for a company like Odoo and cost the
>> most to replace. It's not the source code for core that are most
>> valuable, its all end users and consultants around the world that
>> are willing to contribute and enhance your product and widen your
>> procucts user base - human resources. An Enterprise Odoo without
>> thousands of modules and without localizations are worth nothing.
>> Who do you think will contribute with hours of their own time to
>> translate your closed source modules to their native language?
>> Your competitors are already localized and well translated, so
>> who will buy that product?
>> Regards,
>> Anders Wallenquist
>>> My 2 cents,
>>> Fabien
>>> _______________________________________________ 
>>> Mailing-List: Post
>>> Unsubscribe:
>> _______________________________________________ Mailing-List:
>> Post to:
>> Unsubscribe:
>> -- Alexandre Vandermeersch +32 491 08 80 09 Marketing Join us on
>> June 3-5 2015:
> _______________________________________________ Mailing-List:
> Post to:
> Unsubscribe:

Version: GnuPG v1
Comment: Using GnuPG with Thunderbird -