Community mailing list archives

Re: Enterprise: Is it allowed to use AGPL community modules?

Libertus Solutions, Alan Bell
- 10/06/2015 10:31:12

On 06/10/15 15:24, Nicolas Schmitt wrote:
> Well, now we seem to be reaching more or less of a good comprehension of
> the problem, that APGL modules from OCA may be installed alongside
> proprietary modules by the end-user.
> But what about selling a product as a partner?
> By product I mean Odoo core + a suite of precise modules.
we don't do that, but others might do.
> Does this mean that I cannot implement to a user with both types of licences
> involved? Because in this case I would be selling a product that as a
> whole violates AGPL don't you think?
well, we don't sell a product. The user uses free software (maybe with 
an enterprise subscription and they can use proprietary stuff if they 
want) and they buy implementation services from us, plus sometimes 
hosting services for running their software on our cloud based 
computers. If they subsequently want to buy services from someone else 
that is fine, it is their software, in a more real sense than it would 
be if it was proprietary software.
> Or is this notion of product should be taken a bit more loosely?
> You may also say that I am not selling a product as such, more of the
> service of installing a free product, but still the question is of
> interest to me.
we sell services, others *might* wrap up the core with other bits and 
call it a product, but determining compliance in that scenario is their 
problem not mine :)
> Do you have a better picture on this question than I do?
> Thanks
> Regards,
> Nicolas Schmitt
> On 06/10/15, Alan Bell wrote:
> >
> > On 06/10/15 13:08, Levent Karakas wrote:
> > > This discussion has been made mostly on our side, let's see how it
> > > feels like if we put on customer shoes.
> > indeed, which is why it is OK for the customer to have the freedom to
> > install AGPL stuff alongside unrelated proprietary closed stuff. AGPL
> > stuff shouldn't restrict users freedom to use it, in any way they want.
> > >
> > > Assume a case that a partner develops proprietary code over enterprise
> > > version and customer buys this with a similar clause as odoo sa's
> > > (have to pay forever or remove the applications). What if customer has
> > > problems with partner? Trapped inside another trap....
> > yeah, sucks to be them. This is a perfectly good reason not to use code
> > that doesn't give you software freedom.
> > >
> > > Similar case: partner (official or else) develops proprietary code
> > > over community version and sells it to a customer. Later they want to
> > > finish working together. How will the customer get out of this situation?
> > sucks to be using that code. Stick to stuff that gives you freedom if
> > the cost of the risk of the trap is not worth the value the proprietary
> > stuff gives you. Sometimes for some people the risk is worth taking.
> > >
> > > What is the exit strategy here? How do we explain this to customer
> > > while selling it?
> > >
> > well, explaining it is really the problem of the person making the
> > proprietary software. I have no idea how the proprietary software
> > industry has been explaining it to customers for so long, I guess they
> > just gloss over the risk of vendor lock-in and the lack of auditability
> > and peer review of the code.
> > There is nothing intrinsically wrong with making proprietary code and
> > selling it in my opinion, but customers should value it less because of
> > the freedoms they are giving up by using it.
> > Alan.
> > _______________________________________________
> > Mailing-List:
> > Post to:
> > Unsubscribe:
> >
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe: