On Sun, May 31, 2009 at 1:43 AM, Matthew Toseland <toad at amphibian.dyndns.org> wrote: > On Saturday 30 May 2009 16:11:42 Daniel Cheng wrote: >> On Sat, May 30, 2009 at 10:09 PM, Florent Daigni?re >> <nextgens at freenetproject.org> wrote: >> > * Matthew Toseland <toad at amphibian.dyndns.org> [2009-05-30 11:55:17]: >> [....] >> >> - Database-backed PHP for MANTIS. I don't think we should get rid of >> >> MANTIS. >> > >> > I do think we should; three main reasons: >> > ? ? ? ?- mantis is just not adapted to our usage anymore (We don't have >> > ? ? ? ? ?one single tree anymore) >> > ? ? ? ?- most reported bugs don't apply >> > ? ? ? ?- It's really a high-maintenance cost application... >> > ? ? ? ? ?Administrating mantis, patching it, keeping it up to date is a >> > PITA >> > >> > What about using github's issue tracking thingy instead? >> > >> >> GitHub's issue tracking thingy don't even handle dependency of bugs, >> no real categories (just tags), no milestone thing, no release >> management... --- this is even worse then what MANTIS has. >> >> Most of the github users use LightHouse (http://lighthouseapp.com/), >> but I have not used it either... >> >> Anybody have experience with hosted bug trackers? > > Isn't there a lock-in problem? The business model being much the same as > Microsoft, they own your data, even if you can download it it's in ?a > nonstandard format and can't be taken elsewhere if they suck? So it would be > better to get free (or paid) hosting for a standard open source bug tracker, > such as MANTIS or Trac? >
Lighthouse have "export to csv" function. Seriously, I haven't use it for any real project, so i am not very strong on this. If you want github integration, the options are: - GitHub Issue (very primitive) - LightHouse (used by most github user) - Trac - BaseCamp - FogBugz Of course you can do your own hook for other tracker. but this is what github currently support.
