On 25/06/11 18:11 +0200, Albert Cervera i Areny wrote: > A Dissabte, 25 de juny de 2011 18:01:54, Cédric Krier va escriure: > > 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. > > I'm not a lawyer either but I don't think that's possible. At least, it is > not > with C/C++ and compiled applications in general. That's why KDE has it's > libraries released under LGPL instead of GPL, because otherwise nobody could > create non-GPL applications with their libraries. In the case of Python may > be > a bit different because it's not compiled but IMHO the same logic would > apply. > So if you intend to extend Tryton by creating module which uses Tryton > libraries, you're enforced to using the GPL license. You would not be forced > to that license if you created an application which communicated with Tryton > using the RPC interface.
All is about derivative work and not about the technical details.
Here is a text that explains how it is not logical and even absurd to define
derivative work based on technical point of view (especially the plugin and
object parts).
http://www.law.washington.edu/lta/swp/law/derivative.html
--
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/
pgpZsfSo7IhP8.pgp
Description: PGP signature
