hello there,
I'm not sure if this is the rigth mailing list, but I try anyway :)
(Because I think that this is connected to clause
'how to make Perl be accepted in the workplace')
Backgound:
I think that there is growing group of Perl programmers who are
doing their work to companies and when your workplace is in the
company it is not always obvious that you can relaese the source code.
Because there seems to be modules which are released under GPL
license the situation is sometimes unmaintainable.
I hope that in the future we can avoid this formula with Perl modules.
- Not use the module
- try to search optional module
- invent the wheel again
- try to discuss with the author about special license
- try to find some holes in license agreements
I have posted the following mail both Larry and Tom Ch. too.
--------------------------------------------------------------------------------
We have come thru a long discussion about GPL license and
it's relationship with Perl modules realeased under GPL.
(pointer : http://groups.google.com/groups?hl=en&th=b7a58446dbdcd5fc&rnum=1 )
I quote a few lines from discussion.
-------------------------------------------------------------------------------
>The GPL philosofy says :
>'Free software is about freedom, and enforcing the GPL is defending freedom.'
>
>I wonder that. If you decide to use modules under GPL you
>do not have the freedom to choose if you want or not
>release the source code.
You have the freedom to not include the module at all.
Then you can release your program any way you want.
-------------------------------------------------------------------------------
I think that this is not the real choise at all, so long when
you want to use Perl. I think that modules are main idea
behind the Perl for lazy programmers. Invent the wheel again
is wast of time.
So far, as a lot of programmers are doing their work to
companies the releasing of source code is sometimes difficult.
Because Perl is fine programming language, it think that it is
wast too use the Perl only for purposes which suits for GPL
license.
My question is simple.
Can we expect that there is some day commercial version of Perl too ?
- this could include commercial CPAN (CCPAN). So when downloading
and registering the module from CCPAN you dont have to feel
yourself guilty for using these modules for commercial purposes.
- So, then you have real choises: use the Open source ideology or
commercial way or maybe both or mix of these.
- the writer of the module could also have more choises:
make an commercial, Open source or both versions of the
module.
The current situation requires too much energy, because your choises are
- Not use the module
- try to search optional module
- invent the wheel again
- try to discuss with the author about special license
- try to find some holes in license agreements
regards and greetings from Finland,
Sami
