Closed Klortho closed 6 years ago
Can I ask why, the Perl license is by far the most common on CPAN. Apache 2.0 might be in the top 3 though. I haven't ever thought about it much. I'm curious why?
It is not important, but lately I've become much more license-aware. I'm more familiar with the Apache license, and wasn't sure what the Perl license was, so I just added this issue as a placeholder for something to look at.
It currently states, "under the same terms as Perl itself." I'm not sure what this means. I think it refers to this artistic license: http://www.opensource.org/licenses/artistic-license-2.0, which, on skimming it, I think it is too restrictive.
We might also consider the WTFPL, which I just discovered. ;-)
Its your party. Personally I don't mind a little restriction to keep my software open, but I know that people that are involved a little more restrictive environments appreciate more permissive licences. Anyway, your call. Once you decide, be sure to change the licence property in the Build.PL, for available option see licence
in the Module::Build::API
"Same terms as Perl itself" means either the Artistic License or the GNU GPL.
There is a guide here:
Note that Perl itself is under the GPL 1 or Artistic 1.0. The previous link to the Artistic license was to version 2.0.
Does anyone have a problem if I change the license of this software to Apache 2.0? http://www.opensource.org/licenses/Apache-2.0