Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • I recently took over maintenance of Class::Factory from Chris Winters. I use the module quite a bit, but I got an email from another user of it asking for a feature. What he wanted looked fine, so I handed him a commit bit to the svn repository. Works for me :)

  • The last couple of times I tried to use RT, my ticket was rejected by the system without a good explanation. Plus, that user interface is GOD...AWFUL. I cannot follow what the hell is going on with that thing, and I've used a bunch of different bug trackers, from GForge to Trac to Bugzilla. That thing actually makes Jira look good.

    <sarcasm>Oh, but it's written in Perl, so let's all pretend it's wonderful.</sarcasm>

    After that experience, I decided to just email the authors directly, or sti

    • RT isn't perfect. But it has a few things going for it:

      - It's well-integrated into the other services around CPAN and PAUSE: You get a bug (RT ticket) count on, PAUSE ownership/maintainership status propagates to RT, etc. That's not easy to do and it can help tremendously.
      - It's free. That is, in terms of Software.
      - It's also a free service in that it's run by volunteers (i.e. Best Practical) on their server with their bandwidth.

      About the user interface: You can report bugs via automatically
    • I agree. I do use RT, but it’s very annoying. Comes with the territory: it’s really a ticketing system, not a dedicated bug tracking system, so there’s a lot of interface clutter.

      The only thing I’ve used that’s worse is Bugzilla. Also written in Perl…

  • I'd say that rather than assuming that you should, you should check to see if the module has a SUPPORT section. Personally, I prefer that people use RT for my modules, and my SUPPORT sections say so. But if an author doesn't want to use RT, they should say how they prefer to be contacted.
    • You're right. If the author explicitly says that bugs should be reported in some different manner, we should by all means respect that! (I'll update the journal entry to reflect that.)