At this point, CPANTS rules are getting into the realm of purely self- pleasuring. If more than a dozen people outside of this small enclave of people cares whether a module gets a 16 or 17, I'll be shocked.
I have a couple of suggestions on ways you can make REAL kwalitee changes and provide real benefit to the Perl community.
1) Start applying Perl::Critic to your code, especially modules. If you don't like all the rules, then make a .perlcriticrc file that fits your style.
2) If you find that Perl::Critic is missing rules that you would like to see applied to your code, then write an extension. The framework is extremely easy to use. I've written (stolen, really) a half dozen rules and put out a distribution called Perl-Critic-Bangs. See http://use.perl.org/~petdance/journal/30296
3) Those things that you put into CPANTS? The rules about module installers and passing POD and what not? Write in your use.perl journal about them. Write an article for the Perl Review about them. Get them out where people can see them.
4) Adopt a Perl Mongers group. Go to pm.org, and find a Perl Mongers group that could use a kick in the ass and/or expert technical help. Then, sign up for their email list. Answer questions nicely, and helpfully. Don't pick London or Chicago or NY or Portland. Maybe pick Cleveland or Kuala Lumpur.
5) Write tests for Perl 5 core. Write tests for Parrot. Write tests for Pugs.
6) Become a Parrot Cage Cleaner. Help me get the Parrot underpinnings cleaned up so that it will scale as more and more developers join in. http://use.perl.org/~petdance/journal/30146
And if you still have time or inclination to make CPANTS rules, have at it.
Thanks, xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
