Re: passing the baton onwards (was Re: The relation between CPAN Testers and quality (or why CPAN Testers sucks if you don't need it))
On Fri, Sep 05, 2008 at 04:07:43PM +0100, Nicholas Clark wrote: On Thu, Sep 04, 2008 at 02:19:26PM -0400, Greg Sabino Mullane wrote: Careful attention and responsiveness to CPAN testers and to rt.cpan.org is the best cure for this. Alternatively, I could just not upload code to CPAN, and not have this problem. You're right that it's a problem. I'm not convinced that your cure will work with all real world volunteers. The best cure is that if someone wishes to use a piece of software and finds that it has gone rotten, he can take over maintenance of it. That's how I ended up with Data::Compare. -- David Cantrell | Godless Liberal Elitist Aluminum makes a nice hat. All paranoids will tell you that. But what most do not know Is reflections will show On the CIA's evil landsat.
passing the baton onwards (was Re: The relation between CPAN Testers and quality (or why CPAN Testers sucks if you don't need it))
On Thu, Sep 04, 2008 at 02:19:26PM -0400, Greg Sabino Mullane wrote: I recognize that CPAN is a volunteer effort, but it does seem to me there is a implicit responsibility on the part of the author to maintain the module going forward, or to pass the baton to someone else. Call it a Best Is there an easy central visible way to flag up a module as up for adoption? What should have been the right list to ask that question on? Practice, if you will. The end-user simply wants the module to work. Maintainers not paying attention, and the subsequent bitrot that is appearing on CPAN, is one of Perl's biggest problems at the moment. Careful attention and responsiveness to CPAN testers and to rt.cpan.org is the best cure for this. Alternatively, I could just not upload code to CPAN, and not have this problem. You're right that it's a problem. I'm not convinced that your cure will work with all real world volunteers. Nicholas Clark
Re: passing the baton onwards (was Re: The relation between CPAN Testers and quality (or why CPAN Testers sucks if you don't need it))
In article [EMAIL PROTECTED], Nicholas Clark [EMAIL PROTECTED] wrote: On Thu, Sep 04, 2008 at 02:19:26PM -0400, Greg Sabino Mullane wrote: I recognize that CPAN is a volunteer effort, but it does seem to me there is a implicit responsibility on the part of the author to maintain the module going forward, or to pass the baton to someone else. Call it a Best Is there an easy central visible way to flag up a module as up for adoption? What should have been the right list to ask that question on? A couple of the PAUSE admins have been talking about that, but we haven't really decided anything about how it should happen. There would probably be some virtual PAUSE ID that people could pass primary maintainership too and once those modules are there, someone could request maintainership of them without a waiting period. That's the way that would work with what is already in place, although someone has to upload a new dist for it to show up in the new account. I was thinking we'd want to do that anyway to at least modify the docs to note its status. Or, Andreas could change PAUSE, which is a bit more involved :)
