Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I fully agree with all of your points. (Except that I use svn instead of git, but that really doesn't matter).

As long as the technical side isn't resolved, it might help to encourage people to hand out co-maintainership freely.

It might help to have a wiki (or some such) where you can offer upload privileges, and list TODO items. For example I'm happy to help with Unicode handling of pure-perl modules. I'd just scan that list once a week, and see if there's something interesting. And when I work with a module anyway, I can just as well apply a few simple patches that live in the RT.

Or I could just notice a module I'm familiar with, and accept co-maintainership to to decrease the response times to bug reports and patches.

My experience with the pugs repository are very encouraging. We hand out commit bits very freely (when somebody say "I found a typo in file $file", the answer is usually "should I fix it, or do you want a commit bit?"), and so far haven't had any problems with vandalism or very poor commits.

In any case I think it's important to try to lower the entry barrier for contribution to CPAN modules. Maybe somebody wants to write a Meditation on that matter (to increase visibility and to have a better title)?


In reply to Re^3: Losing faith in CPAN - unresponsive module authors (ownership--) by moritz
in thread Losing faith in CPAN - unresponsive module authors by andreas1234567

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (6)
As of 2024-04-19 08:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found