Hi Malcolm, On 30 January 2016 at 06:49, Malcolm Wallace wrote:

If someone with more experience of setting up trackers were to do the work of creating one for cpphs (maybe on github? is that where everyone hangs out these days?), I might be persuaded to use it. :-)

To you set up a bug tracker in GitHub for cpphs requires only two steps: 1. Create a GitHub account (you already have one) 2. Create the cpphs repository with the issues enabled. Best, -- Andrés

OK, that was easier than I thought. https://github.com/malcolmwallace/cpphs/issues Regards, Malcolm On 30 Jan 2016, at 20:17, Andrés Sicard-Ramírez wrote:

Hi Malcolm,

1. Create a GitHub account (you already have one) 2. Create the cpphs repository with the issues enabled.

Yes, Malcolm, please us a public bug tracker (why not just github.com?)! Thanks! --Andreas On 30.01.2016 12:49, Malcolm Wallace wrote:

On 30 Jan 2016, at 05:19, Andrés Sicard-Ramírez wrote:

...

Is there a bug tracker for cpphs?

Sorry, no. I know it is a bit old-school to accept only email reports of bugs, not least because it gives little visibility to the world at large about which bugs are known, and if they are being fixed or not. But I never found a ticketing system I liked, and the effort required to set up a tracker always seems greater than the value it might deliver for a small project like cpphs. If someone with more experience of setting up trackers were to do the work of creating one for cpphs (maybe on github? is that where everyone hangs out these days?), I might be persuaded to use it. :-)

Regards, Malcolm

_______________________________________________ Libraries mailing list Libraries@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries

-- Andreas Abel <>< Du bist der geliebte Mensch. Department of Computer Science and Engineering Chalmers and Gothenburg University, Sweden andreas.abel@gu.se http://www2.tcs.ifi.lmu.de/~abel/