[dokuwiki] Re: Move the issue & bug tracking to Github
- From: Anika Henke <anika@xxxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Mon, 27 Aug 2012 12:34:23 +0100
On 27/08/2012 09:29, Anika Henke wrote:
I generally like the idea of GitHub as a bug tracker and would
theoretically prefer it over Flyspray, mainly because it is linked to
the repository which makes a few things slicker.
But I think it might not be worth it...!
At the moment we are talking about two options:
1. Keep on using Flyspray.
2. Move the Flyspray issues over to GitHub and use their issue tracker
instead.
But we actually have *more* than those two options.
Why are we considering moving to the GitHub issue tracker? Because it
would integrate issues with our repository and our repository with our
issues. But there are other ways to do the same thing:
3. Use a different bug tracker which also integrates with GitHub! There
are a few which are better bug trackers than the one on GitHub, but they
integrate in a similar way, e.g. Snowy Evening, FogBugz, Redmine,
Pivotal Tracker, YouTrack, ... (I haven't tried most of them.)
There are currently already loads of "service hooks" you can choose on a
project on GitHub. I think it's worth checking them out.
4. Enhance Flyspray to integrate with GitHub! I don't know how
complicated that would be, but it's worth evaluating. I can imagine
writing a GitHub plugin for Flyspray (or implement it through other
means) would cost less time and effort than moving all bugs to GitHub.
Cheers,
Anika
--
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist
Other related posts:
