[dokuwiki] Re: Move the issue & bug tracking to Github
- From: Andreas Gohr <andi@xxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Sun, 26 Aug 2012 13:06:22 +0200
Hi,
> To put this into better perspective, the Symfony2 and Doctrine
> projects have migrated out of jira, etc to Github and have
> substantially benefited from it.
How? What were the exact benefits (except that Jira is a bloated piece
of ... that drives me insane when I have to work with)?
I'm always in favor of using someone else's service when this means we
can save time to administer something others do better. However I'm
not sure Github's issue tracker is a good enough replacement for
flyspray... Let's have a pro/con list for Github:
Pro:
* someone else administers the whole thing (even though running
flyspray isn't much work)
* easy linking and closing of tickets from within commits
* developers will most probably have a github account already
* dubious social benefits I'd love to hear explained
Con:
* markdown parsing makes it hard for novice users to simply
copy'n'paste examples, code snippets or anything else that conflicts
with markdown
* no way to attach a file to bug reports (this is the most serious thing IMHO)
* I'm not sure if non-committers are able to attach tags and thus help
categorizing tickets
* we'd need to write an export/import script to move all previous
tickets to github (any volunteers?)
* we would have ID clashes for the 100 or so existing ticket IDs (from
pull requests)
* as far as I know, existing developers are familar and happy with
flyspray's features (correct me if I'm wrong)
* there's no easy way to send a weekly bug summary mail to the mailinglist
* we rely with a crucial part of our devel process on a 3rd party that
proved to be deaf to our support pleas before
So far, I'm not convinced. But maybe I'm wrong.
Andi
--
splitbrain.org
--
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist
Other related posts:
