Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Moving modules@perl.org here 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Are you asking to:
    • move the mechanism by which namespace requests are submitted (use.perl slash plugin vs. modules@perl.org)?
    • increase the number of people who are responsible for responding to (and approving?) namespace requests? (the members of modules@perl.org can't really be blamed for being so busy)
    • make a fundemental change in the management of CPAN namespaces, including the switch to use perl and the increase of namespace monitors?

    I really don't care which goal you have in mind. What I really c

    • Well what I really meant to do was raise some discussion about it :-)

      I think number two is the most important thing. People are pointed at modules@perl.org to get ideas for what to name their modules. But for example if an XML person went there with a request, it would fall on deaf ears because I don't think there are many (any?) xml experts on that list.

      Once a community has discussed naming, then it might need to feed back into a more formal mechanism to get onto the modules list. But most of the compl
      • I'm wondering if this would create overhead for pudge/other submitters as someone needs to approve the topics that go into a channel? Or am I misunderstanding something?
        • Yes, but it would be fairly easy to add a few moderators. I mean, slashdot copes with thousands of submissions a day - I'm sure we wouldn't have more than 30 or so, which is about the current daily traffic on modules@perl.org (and they would still have to deal with new user and pauseid requests). And quite a few of that 30 or so is replies. So thinking along the lines of 10 module requests a day, it's not too much work to see which are valid module requests and approve the story... But then I wouldn't want
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.