On 25/06/11 10:18 -0500, Michael Hipp wrote: > On 6/25/2011 9:12 AM, Cédric Krier wrote: > >After that, you must define what you mean by "closed-source app"? > > I'm developing a program that will be sold/rented to small > businesses. The sponsor of the project is not willing (yet) to open > source our own code. If I were to make use of (make python calls > into?) Tryton in a program distributed to these businesses, would I > then be required to open source our code?
Again INAL, but here is our (B2CK) understanding of the GPL.
Your code must be under the GPL if it is a derivative work of Tryton.
Once this is said, we must define what is and what is not a derivative work
and there is no simple answer. We think it should be answered case by case.
There is difference common cases:
- you modify directly Tryton code, so it must be under the GPL
- you write a small module that makes simple modifications on the behavior
of existing Tryton modules (like adding few field on Sale Order). Then
it is clearly a derivative work and must be under the GPL.
- you write an all new module that does something completly new that is
not in Tryton (for example (at this date) a payrol module). Then it can
be seen as an original work and you can release it under the license of
your choice.
Of course, the limit between the two last cases could be fuzzy and it is in
this cases that you should ask for a lawyer to have clear statement.
PS: if you are releasing a closed modules, you must ship/distribute it
separatly of Tryton and in any cases together.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgp0TmwOe4AO9.pgp
Description: PGP signature
