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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Isn't this something that an RT queue would deal with better?

    --Nat

    • RT would help things like PAUSEID requests, and requesting to add a module to the module list. But I can't see how it would increase discussion about the naming of a module. Maybe you could detail how that would work with RT?
      • I'm a member of modules@perl.org, albeit just as busy as the rest, and just as guilty of getting lagged in responding to posts.

        I am a proponent of the RT idea, because it would help me (and probably others) to log into one place and see "HERE are the requests that have been waiting in line longest without a response." As it is at the moment, I would tend to respond to the most recent requests because I can't figure out whether the older ones have been dealt with or not.

        Currently the only way to track a
        --
        Kirrily "Skud" Robert perl@infotrope.net http://infotrope.net/
        • I'd vote for RT too. I think this and an increase in the number of people involved in the modules@perl.org effort would probably help this thing flow better. I would be quite happy to help despite being as busy as everyone else :)

          Another suggestion I would like to make here would be the introduction of a more automated mechanism for introducing existing modules into the module list by their authors - that is to say that alongside the tool to edit the existing entries there could be a list of modules that have been uploaded by the author and not entered on the module list - again I would be quite happy to help with this in some capacity ...

          /J\