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 agree that RT would probably be a good idea. At least worth trying.

          I also think that splitting out the multiple roles of the modules@perl.org list into several module-foo@perl.org lists might be a good idea.

          To those who ask about why "slience means approval" with regard to module naming... it's effectively a veto system.

          Module naming can be a very subtle issue. It requires judgement that typically comes from many years experience.

          Just because five people can't see any problem with a module name, d
          • Being, like Tim, one of those people behind the "deafening silence", I thought to comment a bit, too. Mainly I'm just 120% in agreement with Tim, but maybe some further examples will help in understanding the issue. A ticketing system will help in account creation, module list surgery, things like that, but not in naming.

            - First and foremost, people tend to take module naming very personally. They have toiled away their module in private for a long while, they *know* that their name is perfect, not many