CPAN licensing redux

ziggy on 2001-04-28T18:33:54

hfb writes "CPAN recently had a discussion about licensing that spilled over into several different mailing lists. We would like to remind people to be sure to license your modules before uploading them to PAUSE.. Please choose a license that suits you or make one yourself and note it somewhere in your POD documentation in the module itself , e.g.

=head1 COPYRIGHT AND LICENCE

Copyright (C) YEAR YOURNAMEHERE

This library is free software; you can redistribute it and/or modify
it under the same terms as Perl itself."

hfb continues: "O'Reilly may be hosting a Open Source licensing tutorial with a real lawyer, not Perry Mason, at TPC so be sure to check the schedule if you are interested in learning more about licenses and the benefits of using them.

Again, please, please, please, license your modules and remind authors when you see unlicensed code on CPAN to add a statement of copyright/license and upload a new version to CPAN.

It has the benefit of more people using your code without ambiguity, we won't have to field questions of license as much and it will hopefully avoid any serious legal problems for the archive in the future."


License? Licencing?

jjohn on 2001-04-30T21:54:20

You see? This is why jjohn can't read...

Re:License? Licencing?

vsergu on 2001-05-01T17:43:23

In writing for an international audience, the best policy when confronted by words that are spelled differently by different English-speaking communities is to flip a coin each time such a word appears. Inconsistency is preferable to giving offence. The obvious extension is to pick a random language for each word as you go.

Re:License? Licencing?

hfb on 2001-05-01T20:09:46

Actually, I used 'Licence' because it was already spelled that way in h2xs where you will find that little code snippet.

If this gets your panties in a bunch, I suggest you get a A to Zed dictionary and get over it.