|Perl: the Markov chain saw|
I don't think hosting more CPAN modules in revision control would matter to most people or most modules. Although a small group of people will actually make a patch against the repository, most people don't.
Even if a few people do patch against the repo, I've only ever had one person also update the tests. It might be hard for some hard-core contributors to realize that, but most people either don't have the time or inclination, and even more people don't have the skills to do it.
You don't need anyone's permission to upload a new version of an abandoned module. PAUSE just doesn't index it if you don't have privileges. A restive period is not helpful because some modules don't need updates in that time frame. There's no timeframe that you can apply across of all CPAN.
Don't refrain from patches because you think the author won't help. Make the patch public, such as in RT, and other people can get it even if the author doesn't apply it. Don't hide from the rest of the world what you know because one person doesn't respond to you. And, making the patch public starts the history of an author not responding to you and makes it easier for the PAUSE admins to see what happened so they can transfer the module when necessary.
brian d foy <firstname.lastname@example.org>
Subscribe to The Perl Review