Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
contributing requires the "admins ... declare code abandoned and the seize it"

I assume I misunderstand you, because this strikes me as disingenuous at best. I would guess that any PAUSE author who requested that their work be taken off CPAN would have their request honored. It may provoke some comment and consternation, but given that an author may have legal issues regarding authorship I see no advantage in CPAN's noncompliance.

I don't believe CPAN contributions require that "admins ... seize code" nor do I believe that the fear of such prevents contributions.

CPAN is a distribution mechanism not a development tool. There is no reason to expect CPAN admins to jump to take on new tasks that have little to do with that for which they volunteered.

When you release on CPAN, you don't have to stop developing the codebase where, how and with whom you like. I should have been clearer about the timing.

There is nothing I see in the rules of the CPAN that you are complaining about; how is CPAN stopping you from setting up a collaborative development process for the modules in your care? You just seem to want CPAN to be something completely different than what it is.

I like what you are proposing, I just don't see it having much to do with CPAN.

Be well,

In reply to Re^8: JETTERO tries to take over Net::IMAP::Simple on PAUSE (admins) by rir
in thread JETTERO tries to take over Net::IMAP::Simple on PAUSE by jettero

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
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 romping around the Monastery: (3)
As of 2021-05-15 21:45 GMT
Find Nodes?
    Voting Booth?
    Perl 7 will be out ...

    Results (150 votes). Check out past polls.