Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
In this sense, I feel that thought could be given to a natural and agile way (built into the structure of CPAN) of branching or evolving a given module, a way that automatically took care of authorship, copyright and and other important formalities.
I don't think this should be build in the structure of CPAN. The ability to fork is a licensing issue - most open source licenses allows you to fork. It's totally indepent of the existance of the module on CPAN.
That is, so that every bit of work by any author (no matter the level of it's original author's involvement after it is released) would be completely shared with the other authors and users.
That's not the task of CPAN. CPAN should not dictate what rights authors must be willing to give up for distributing a module via CPAN. The only restrictions CPAN should put on authors are those that keep CPAN from doing its work, as such, the restrictions for authors is that their work should be freely distributable.

Adding the requirement that outsiders may take over authorship and copyright of a module isn't a good thing in my opinion. You'll lose people contributing code to CPAN. Not to mention all the resources you have to pour in to work out the legal details of this.

Perl --((8:>*

In reply to Re^3: Responsibilities of a module author by Perl Mouse
in thread Responsibilities of a module author by xdg

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others about the Monastery: (7)
    As of 2020-02-19 20:59 GMT
    Find Nodes?
      Voting Booth?
      What numbers are you going to focus on primarily in 2020?

      Results (85 votes). Check out past polls.