Members mailing list archives

Re: OCA's statement on the announced change of license of Odoo

Hertford Developpments LTD, Kurt Haselwimmer
- 06/02/2015 10:45:37

in response to your point I will give a little story. 

I went to the Odoo conference last year and one of the talks was about creating labels for shipping, with fedex or some such other courier. I forget who it was by exactly, but the talk was good and it left me wanting more - specifically it left me wondering why this was just for one courier, and why there wasn't any tracking reporting integrated once the shipment had left the factory (after all this is a feature I had on my, basically free, ecommerce cart, for three years and it was very helpful) - so I asked a question after the talk - "is there a module, or standard framework for odoo for tracking shipments after they have left the factory?"

I was surprised by what came next.

The speaker looked completely confused - "well, no" they replied "they had not been asked to create that, and no, they didn't know of any module". This answer said the following things to me at the time:

1) development could only happen when there was a corporate customer already standing at the developer's door, and they had the money ready to solve something that was important TO THEM.
2) there was  little incentive to produce software 'products' - modules that would be developed for more than one customer, with generic requirements in mind, and with future maintenance properly paid for.
3) the developer community would ultimately be limited to those partners who had the resources to market to mid-sized companies and this would restrict the ability for themes and ecommerce/cms functionality to be developed

Once I understood that this situation was a result of the particular licensing approach that Odoo had in place at the time I concluded that the ecommerce/cms development of odoo would be hampered to such an extent that I would not be able to use it for my purposes until 2016 at the earliest and so have since concentrated on developing my customer facing front-end on other platforms. 

The change of licensing for odoo marks an important transition to a more commercially sustainable platform, for odoo, for theme developers, for small and mid-sized customers, but more importantly it marks a transition that existing odoo partners must make in their business models - instead of thinking just about the one customer standing in front of them, and how THEY are going to pay for any particular development, the partners can now start to think about other potential users of the same feature, and how the feature might be supported and developed in future. It is an enlargement of the partner's horizon, and it is a positive thing.



Dr. Kurt Haselwimmer

Hertford Developments Ltd
Willow House, 100 High Street, Somersham, PE28 3EH
Tel +44 (0) 845 899 0257  Fax +44 (0) 845 899 0259

I still think the AGPL is the best license for this type of software, if
the objective is to protect the community from intents to closing it.
LGPL in this sense is a much weaker protection, and is precisely chosen
for that reason: to allow CMS developers to keep their code private,
even while they're benefitting from the whole Odoo ecosystem.

Apart from the disadvantage - im my eyes - to encourage such private,
closed modules, there is the risk that at any point Odoo S.A. maybe
inclined to continue their development closed source. Now of course I
don't say they will, but we must keep this scenario in mind, especially
as venture capital has taken a growing part of the company. And Odoo is
becoming a bigger and better brand name in the ERP/Apps marketplace.

For keeping a healthy ecosystem I think the LGPL move doesn't help, but
maybe there are people who could convince me from that (?)

my 2 cts,

Wouter Tebbens

On 02/05/2015 11:44 PM, Jean-Sébastien Suzanne wrote:
> 2015-02-05 21:27 GMT+01:00 cubells <
> <>>:
>     El 05/02/15 a les 19:57, david ha escrit:
>     > Dear OCA members,
>     >
>     > As a regular contributor on OCA modules, I don't see any advantage to
>     > move to LGPL
>     > for my new modules contributions.
>     > I think AGPL will protect our hard daily work by its contamination
>     > property over other licenses.
>     >
>     > I'm ok to sign a personal commitment (know by the whole community and
>     > displayed as it)
>     > to go on to contribute with AGPL license only.
>     >
>     > Could we constitute a large members list of contributors with the same
>     > engagement ?
>     >
>     > What do you think of it ?
>     >
>     I totally agree with you.
> +1 
>     AGPL is perfect for me.
>     -- 
>     Atentament, cubells.
>     --
>     _______________________________________________
>     Mailing-List:
>     Post to:
>     <>
>     Unsubscribe:
> -- 
> Jean-Sébastien SUZANNE
> <>
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:

Post to: