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

Re: Losing faith in CPAN - unresponsive module authors

by grinder (Bishop)
on Jun 25, 2008 at 08:24 UTC ( [id://693910]=note: print w/replies, xml ) Need Help??


in reply to Losing faith in CPAN - unresponsive module authors

You make it sound as if the author owes you something.

CPAN is a volunteer operation, people donate code in the hope that it will be useful. Yes, it's rude not to acknowledge a bug report or patch, but there are any number of reasons: people may be too busy, the e-mail forwarding address may be obsolete, the author may have lost interest. It takes discipline to manage CPAN modules correctly and so it's only natural that there's a certain amount of attrition over the years.

If you have made a concerted effort to get in touch with the author (and ranting on Perlmonks doesn't count), can show that you are able to close out most, if not all, bugs on the RT queue of the distribution, then send a message to module-authors@perl.org documenting this, and you will be granted co-maint status on the module. This happens all the time.

• another intruder with the mooring in the heart of the Perl

  • Comment on Re: Losing faith in CPAN - unresponsive module authors

Replies are listed 'Best First'.
Re^2: Losing faith in CPAN - unresponsive module authors
by andreas1234567 (Vicar) on Jun 25, 2008 at 09:37 UTC
    You make it sound as if the author owes you something.
    If so that is completely unintended. It is quite the opposite - I recognize the huge volunteer efforts put into CPAN. I'm just wondering if there are ways to improve how CPAN works so that it is less dependent on people being not busy, email accounts correctly set up, and maintainers still having interest in the modules they once wrote.
    If you have made a concerted effort to get in touch with the author (and ranting on Perlmonks doesn't count), can show that you are able to close out most, if not all, bugs on the RT queue of the distribution, then send a message to module-authors@perl.org documenting this, and you will be granted co-maint status on the module. This happens all the time.
    That's true. But not all of us are able to fulfill all those conditions. Most of us can make reasonable efforts to contact a module owner. Some of us can submit patches to modules. Very few of us has what it takes to step up and claim (co-)ownership of a widely used and fairly complex module. I certainly don't belong in the last category, I'm simply not that skilled. But I still want to contribute.

    I will try to be more patient from now on.

    --
    No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://693910]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (4)
As of 2024-04-24 22:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found