Re: Getting co-maint for new modules in a package
[[ This message was both posted and mailed: see the To, Cc, and Newsgroups headers for details. ]] In article [EMAIL PROTECTED], Chris Dolan [EMAIL PROTECTED] wrote: Is there an easy solution to getting co-maint on all modules in a distro? Is it just something we need to remember to do, or is there an automatic solution somewhere? At PAUSE we can set up a mailing list user (it's not really a mailing list) for Perl::Critic. Anyone we add to that list can assign co-maintainer permissions. See the guide I made for the Parrot people: http://search.cpan.org/~pmic/parrot-0.7.1/docs/project/pause_guide.pod
Getting co-maint for new modules in a package
The Perl::Critic team has a small but persistent problem with PAUSE. We frequently add new policy modules to the distro. When we do so, the person who does the release gets ownership of that namespace. We have three co-maintainers who do releases, so reminding each other to grant co-maint on the new modules is becoming an unwelcome ritual before handing off the release baton. Is there an easy solution to getting co-maint on all modules in a distro? Is it just something we need to remember to do, or is there an automatic solution somewhere? Chris
Re: Getting co-maint for new modules in a package
Everybody's a critic... (sorry, couldn't resist) On Sat, Oct 11, 2008 at 1:49 PM, Chris Dolan [EMAIL PROTECTED] wrote: The Perl::Critic team has a small but persistent problem with PAUSE. We frequently add new policy modules to the distro. When we do so, the person who does the release gets ownership of that namespace. We have three co-maintainers who do releases, so reminding each other to grant co-maint on the new modules is becoming an unwelcome ritual before handing off the release baton. Is there an easy solution to getting co-maint on all modules in a distro? Is it just something we need to remember to do, or is there an automatic solution somewhere? Chris
