@numerigraphe,

> Anyway Tiny SPRL is the owner of all copyrights regarding the official code 
> of OpenObject. If you want to be safe, just ask them for a written permission 
> to make a non-GPL module.


That's debatable I think. They accepted a lot of contribs and bug fix but had 
no license contribution agreement, such you'll find in the Mozilla, Eclipse, 
Sun projects (at least). And in other projects where either licensing, either 
agreements had not been set early there have been troubles with copyright owner 
not allowing to change the licence: famous examples are the Linux Kernel that 
wouldn't move to GPL3 and openjdk that couldn't simply release Sun Java as 100% 
open source.

I already urged Tiny to present such a contribution agreement, like one year 
ago. The more they wait, the more they could be people attacking them upon 
copyright ownership (and hence future licensing policy). That could already be 
too late for them to be able to decide future licensing changes...

I personally support the GPL idea, On an other side, that's clear that allowing 
commercial modules could build a sustainable professional eco-system such as 
Magento extensions (great commercial eco-system example). Now, I think we 
should absolutely protect the core modules of the system from having commercial 
catches. I think it's very good to ensure at least the current scope is GPL. 
Now, very specialized tools such as sale prediction, MRP2 scheduling, legal 
payrolls, could be better achieve if companies could ensure they would get 
their investment back. But I see no simple way to define two different scope, 
one GPL, and an other that is not. The GPL is viral and that's probably a good 
thing. With no alternative, I prefer much more the GPL option than commercial 
adhoc licences with commercial catches around each corner.

------------------------
Raphaël Valyi

CEO and OpenERP consultant at
http://www.akretion.com




-------------------- m2f --------------------

--
http://www.openobject.com/forum/viewtopic.php?p=44856#44856

-------------------- m2f --------------------


_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users

Reply via email to