Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Adding a license to an existing module 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I believe that you cannot retroactively apply a license. The best you can do is to continue to release it without a license and hope the original author doesn't come after you for copyright violation. This module should be listed as "restrictive" as per Module::Build's classification system [cpan.org]

    Obviously, you should put some commentary about this issue in the POD.
    • I agree with Chris Dolan - the difficult thing however is defining what the restrictive license should be. Apparently distribution is somewhat free, but perhaps limited to CPAN. The source code is available and the software is free to download and use.

      It would be nice if the CPAN had a default license, that modules not specifying a particular license would fall back to. At least this would get CPAN contributors to think the subject over.

      Agreeing on a common CPAN license could take some time though :)
      • Well the de-facto license on CPAN seems to be "same as perl" which I think is what everyone assumes anyway...

        I guess maybe I'll try and track down the original author again.
        • Hehe I am in an agreeing mood and yes I agree with you, but still many modules does not have license specified and therefor unknown is listed, an example [cpan.org], my own actually :-/

          So yes the defacto license might have been chosen, but CPAN should apply it automatically, then we would not end up with the situation you are in now.
          • No, CPAN should not declare a license simply because CPAN is software and can't understand the complexities of licensing. When software is open sourced, the author is granting rights beyond what is required by law or convention. That grant requires that the author controls the intellectual property behind the software and that s/he really has the right to assign those more liberal rights. That HAS to be opt-in, not opt-out.
          • Well, you can't just go applying license to things that aren't yours.

            HOWEVER, CPAN _requires_ the use of an open source license, and the lack of a license (in the META.yaml I guess) should probably be grounds for PAUSE refusing to allow a distribution to be uploaded. For that matter, so should "restrictive".

        • Sorry, but I disagree. Yes, the most common license on CPAN is probably "same as perl" but any default license must respect some sort of copyright laws which likely already provides some default (like "fair use" in the Unied States)

          Sure, the author *probably* meant it to be Artistic/GPL and you're *probably* not going to have problems redistributing or reusing the code, but when actually stating a license, I say you have to be conservative in this case and let the end user know that the code has not actual
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.