search

libraryhackers / library-callnumber-lc

Perl and Python modules for normalizing Library of Congress call numbers
30 stars 2 forks source link

"New BSD" license is not the license of Perl itself (and version of Perl should be specified) #6

Open gmcharlt opened 9 years ago

gmcharlt commented 9 years ago

Original issue 6 created by gmcharlt on 2012-06-08T13:48:36.000Z:

What steps will reproduce the problem?

  1. http://code.google.com/p/library-callnumber-lc/ says the licence is "New BSD"
  2. http://code.google.com/p/library-callnumber-lc/source/browse/trunk/perl/Library-CallNumber-LC/README# 64 says "This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself."

What is the expected output? What do you see instead?

I expect to see the license in the code match the Google Code project metadata.

Please provide any additional information below.

The Perl Foundation advises against the lax "same terms as Perl itself" phrase and suggests you specify a particular version of Perl (as the license for Perl can change over time): http://www.perlfoundation.org/cpan_licensing_guidelines

So perhaps a better phrase for the license in the code and README would be "same terms as Perl 5.14.0" (per the CPAN licensing guidelines) which resolves to "GPL 1 or later; or the Artistic License".

gmcharlt commented 9 years ago

Comment #1 originally posted by gmcharlt on 2012-06-13T04:26:02.000Z:

The Fedora package reviewer (https://bugzilla.redhat.com/show_bug.cgi?id=830221#c5) noted that there was a bug filed on CPAN for this same problem last year (https://rt.cpan.org/Public/Bug/Display.html?id=70038). It seems that version 0.22 includes the "or BSD" option in the README - but per issue # 5, that code is out of sync what this repository, which the README says is the home of the library.

So, we need to clean up issue # 5, and also (per the Fedora package review), update META.yml to also specify the BSD license as an option.