On 2/26/07, intersol <[EMAIL PROTECTED]> wrote:
And this will cost the developer good money, money that he will get back only if he is going to implement it 10 times. But he wonders: what's happening if one of his customers is going to share/publish the module with others?!
who says you can't implement it 10 times, even if it's published online under the gpl? an erp is not a trivial system, and enterprises need serious support and customization in order to implement it... and who do you think they'll hire for that, the creator of the module, or anyone? just look at all the projects in tinyforge, most of them have companies behind their development, and they're still published under the gpl... the business model of selling boxes (aka licenses) is getting old, now it's all about (quality) service.
This is why LGPL seams more productive. In the case of LGPL you are required to share only the modified sources.
more productive for taking advantage of the existing development without giving anything back; not more productive for the whole ecosystem. if everyone did the same that you want to do, there would be no tiny erp.
PS. I don't even dare to think about requesting a price for LGPL license when I see the current support prices. :(
well it's an enterprise-grade erp system; try to get one of those under the license you feel like, without paying for that. anyway, i don't know if tiny sprl can even do that, because there are many patches contributed by others (under the gpl), and i don't think they have copyright over those, in order to relicense them (correct me if i'm wrong, fabien). -- Santiago Roza [EMAIL PROTECTED] _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
