Probably me. :)
RT has always been my preferred issue tracker, and the one I linked to in META.yml. However, some people were reporting issues on GitHub anyway, which meant I often didn't see those issues. So I closed the GitHub issue trackers for each project not so much because I hate GitHub's issue tracker, but more because having two for each project was bad, and out of the two, I would rather use RT.
RT being shut down is annoying yeah. I'm currently investigating three routes:
Switch to GitHub issues. GitHub issues is mostly pretty decent if you look at it on a per-project point of view. However, if you're managing a lot of projects, it's less good. You can't move an issue from one project to another, for example; you'd need to close it on one project and open a new one on the other project. RT lets you create a custom dashboard where you can see new issues on all your projects at one glance. This is somewhat possible on Github, but it's a lot less flexible. Maybe I can figure something out with the API though.
Host my own copy of an open source issue tracker. A lot of them suck though. I've set up Roundup for clients a couple of times though, and it's pretty darn nice. Customizing it involves writing Python though. Ewww. Overall, it's still a good option, even if I'd need to shower afterwards.
Write my own issue tracker. Very tempted to go down this route. It would let me manage issues exactly how I wanted to manage them. I started fleshing out an SQL schema. It seems a lot of work though.
I think I'll probably end up using GitHub in the end; MetaCPAN has pretty decent integration with it, showing the number of open issues like it does with RT. And given the amount of work I'd need to put into setting up and maintaining my own hosted issue tracker, I could put that work into writing custom dashboards for the Github issue tracker using the API.
And actually switching distros over to use the new tracker is pretty easy. Perl exists. It can be scripted.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.