Hi Steve,
Steve Bertrand wrote:
The company that employs me is very small, and although I don't believe
there will ever be a problem with giving my code away, I want to take
advantage of the fact that I have never signed anything to say I
``can't'' give it away. I'm at a stage where some of our staff is
testing, so before the powers-that-be decide that this is company code:
I hope you double-check this as sometimes the powers-that-be slip this
in without you noticing. It might be folded into your job contract,
etc. One could argue that you did that work while under their
employment (as opposed to doing it at home in the evenings or on
weekends). I honestly do not know -- but it might even be in Canadian
labor laws? I'm not saying that you can't release it; but just be careful.
That said, some of what I've done is released to the public, but when
you're paid by tax payers, I think it is slightly easier to argue for.
What is the quickest and easiest way to ensure my code is truly licensed
as public domain, if I don't feel that the code is quite CPAN worthy?
Perl aside, one thing you might want to look into is the documentation
for the GPL license to see if that is a license you want to attach to
your code. If so, then there are steps that it says you should do
(include the license with the archive, etc.).
In fact, Wikipedia has a list of software licenses:
http://en.wikipedia.org/wiki/Comparison_of_free_software_licences
Instead of GPL, you might want to see what you like and then do what it
says. Of course, assigning a license is different from distribution
(putting it on CPAN, on your homepage, etc.).
Ray
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
