I hear some people don't like rt.cpan.org. Heretics!
rt.cpan.org seems to evoke a somewhat marmite response[1] in most of the Perl developers I've spoken to about it. As someone who's used, administered and developed with RT since back in the 2.0.13 days I don't get why they don't like it! What's not to like?!
Ho hum.
So for you heretics and RT unbelievers out there, Shadowcat Systems have been hard at work producing a set of patches in order to make your lives easier - external bug tracking support in rt.cpan.org is just around the corner...
Whut?!
Up until now, various of the distribution build tools have let you set an alternative bugtracker mailto or web adddress. search.cpan.org has used these to link through to the alternative bug tracker instead of rt.cpan.org however people can and will visit rt.cpan.org as a first point of call.
Introducing support for External Bugtrackers! If the META information has been set accordingly, the new set of patches will display the information at the top of the rt.cpan.org pages very visually indicating that our would be bug reporter should visit an alternative site or email the issue to the given address.
Dist::Zilla
In your dist.ini you can add the following to your MetaResources config:
bugtracker.web = http://rt.perl.org/rt3/
bugtracker.mailto = perlbug@perl.org
Dist::Zilla::Plugin::AutoMetaResources
Module::Build
This only seems to support setting the web URL, so you'll need to add the following to your Build.PL:
bugtracker 'http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Module-Build-Functions';
Module::Install
Within your Makefile.PL you can add:
resources bugtracker => 'https://github.com/ranguard/svg-tt-graph/issues';
So, go and update your distributions as required and soon that information will be more visible to your potential users.
idn
[1] You either love it or you hate it.