I made a long detailed reply, then figured a short one would work.
While it could be in GT's interest to release the libs, *IF* they could properly support them, it would *NOT* be in their interest, if they could not support them.
Two things would/could happen. 1) they would be looked upon negatively, and it would HURT rather than help their image, and 2) they could lose control over the development of their modules, as more active developers with fewer other obligations take over modifications.
While there is a great benefit from open-sourcing modules and libraries, there is a responsibility that goes with them. You cannot release and ignore them, especially if you develop commercial products on top of them.
You can agree or disagree with this, but it remains a business fact. The most successful CPAN/PERL modules are ones that are actively supported. No module is written in stone. Something always comes up that requires a change or addition. RESPONSE time is important, and GT has other considerations than supporting an open source community. It would be wonderful if they could, but the realities are they can't, not at this time.
If GT could manage to find a support person to deal with CPAN, and maintain the modules, they would get an awesome boost in recognition from the use of those modules. I can't imagine programming in perl without them, and many other people have gotten hooked on them as well. But, realistically, you can't just throw things out and hope it works. That makes no sense, financial or otherwise. Releasing a well supported module, that brings customers to you for custom work, custom support services, or application development *IS* a financially sound business model. When, such time comes as GT can do that, I'm sure they will. Until that time, asking them to give up their IP rights is somewhat silly, and even arrogant.
These are my opinions, and do not reflect GT's motivations or plans in anyway.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
While it could be in GT's interest to release the libs, *IF* they could properly support them, it would *NOT* be in their interest, if they could not support them.
Two things would/could happen. 1) they would be looked upon negatively, and it would HURT rather than help their image, and 2) they could lose control over the development of their modules, as more active developers with fewer other obligations take over modifications.
While there is a great benefit from open-sourcing modules and libraries, there is a responsibility that goes with them. You cannot release and ignore them, especially if you develop commercial products on top of them.
You can agree or disagree with this, but it remains a business fact. The most successful CPAN/PERL modules are ones that are actively supported. No module is written in stone. Something always comes up that requires a change or addition. RESPONSE time is important, and GT has other considerations than supporting an open source community. It would be wonderful if they could, but the realities are they can't, not at this time.
If GT could manage to find a support person to deal with CPAN, and maintain the modules, they would get an awesome boost in recognition from the use of those modules. I can't imagine programming in perl without them, and many other people have gotten hooked on them as well. But, realistically, you can't just throw things out and hope it works. That makes no sense, financial or otherwise. Releasing a well supported module, that brings customers to you for custom work, custom support services, or application development *IS* a financially sound business model. When, such time comes as GT can do that, I'm sure they will. Until that time, asking them to give up their IP rights is somewhat silly, and even arrogant.
These are my opinions, and do not reflect GT's motivations or plans in anyway.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
