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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I think it's a good idea to have a warning, assuming people can stumble onto backpan and not realize that it's an archive meant only for historical record and is not the real CPAN. And I think you're right about the copyright/licensing issues; a module author doesn't necessarily hand over a module to the public domain just because it was uploaded to CPAN, or maybe it should just be explicit that by uploading something to CPAN you forfeit your rights to restrict the module's distribution? (or haven't you?)

    O

    • Personally, I like BackPAN the way it is and wouldn’t want things on it to be deletable forever, because I think of it as an archæological record. The mistakes of the past should conserved with equal prominence to its achievements.

      But it sure would be handy if there was a way to flag known bad stuff so people are forewarned.

      a module author doesn’t necessarily hand over a module to the public domain just because it was uploaded to CPAN

      Well, by uploading to the CPAN, you have distributed it to at least one third party. They are thereafter under the conditions of your licence. If the licence you labelled your work with at upload time does not grant you the right to retroactively retract that self-same licence, then you cannot retroactively demand that the CPAN stop distributing it. (You can ask nicely, and maybe your request will be considered in the spirit of cooperation, but you have no right to demand it.)

      That doesn’t make the module part of the public domain. The CPAN remains forever bound by the licence under which you uploaded the module.