From 47fb2434438e67771e77bd3fb9733cd75cb7cf7d Mon Sep 17 00:00:00 2001 From: David Golden Date: Sun, 1 Feb 2015 09:08:58 -0500 Subject: perlmodstyle: point people to PrePAN, not modules list This harmonizes perlmodstyle with the guidance on PAUSE for getting feedback. Having new authors email modules@perl.org is not a good use of PAUSE admin time. --- pod/perlmodstyle.pod | 21 ++++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-) diff --git a/pod/perlmodstyle.pod b/pod/perlmodstyle.pod index d6111d059d..6f0cb96c12 100644 --- a/pod/perlmodstyle.pod +++ b/pod/perlmodstyle.pod @@ -58,6 +58,10 @@ Do one thing and do it well Choose an appropriate name +=item * + +Get feedback before publishing + =back =head2 The API @@ -240,11 +244,18 @@ hierarchy already exists under which you could place your module. =back -You should contact modules@perl.org to ask them about your module name -before publishing your module. You should also try to ask people who -are already familiar with the module's application domain and the CPAN -naming system. Authors of similar modules, or modules with similar -names, may be a good place to start. +=head2 Get feedback before publishing + +If you have never uploaded a module to CPAN before (and even if you have), +you are strongly encouraged to get feedback on L. +PrePAN is a site dedicated to discussing ideas for CPAN modules with other +Perl developers and is a great resource for new (and experienced) Perl +developers. + +You should also try to get feedback from people who are already familiar +with the module's application domain and the CPAN naming system. Authors +of similar modules, or modules with similar names, may be a good place to +start, as are community sites like L. =head1 DESIGNING AND WRITING YOUR MODULE -- cgit v1.2.1