[dokuwiki] Re: Move the issue & bug tracking to Github
- From: Michael Hamann <michael@xxxxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Tue, 28 Aug 2012 11:04:29 +0200
Hi,
I don't have any particular preference for Flyspray or GitHub. What I
like about GitHub is their email interface. Sometimes I think there
are just too many ways to categorize bugs in Flyspray, by using tags
we could get rid of that complexity. I don't think it is a big problem
if users can't assign tags, it should be easy to do that when you view
the issues. Not being able to upload files is a larger issue in my
opinion.
2012/8/27 Guy Brand <gb@xxxxxxxxxx>:
> On Aug 27, Anika Henke wrote:
>> Although because git is decentralised/distributed, that's not much
>> of an issue, because it's extremely easy to work on it if GitHub is
>> temporarily faulty or to move to a different service. (BTW, do we
>> have a mirror? Shouldn't we have one?)
I don't think we need a mirror for the code as I think we have enough
mirrors of it, and I think even on dokuwiki.org as the testing service
always downloads the latest version. We can care about making that
available somewhere when we need to, a simple read-only git access is
as easy as moving a git repository into some path under the webroot
and executing a command.
>> I personally think the best solution would be a "distributed bug
>> tracker", i.e. bug reports should be kept on a branch of a
>> repository, so they would always move with the repository.
This sounds like a good idea, but we should make sure that there is an
easy to use web interface for submitting bugs (which could of course
use git in the backend). There are several projects which are trying
to implement a git based issue tracker but most projects don't seem to
be active anymore and I also haven't found any web interface yet.
I think we should also consider that we already have parts of our
development discussion in pull requests and comments on commits on
GitHub and we don't have any mirror of that information.
I think there is a difference between putting the code and the whole
discussion on GitHub as the code is - in contrast to the discussion -
easy to mirror and for this part, GitHub is easy to replace.
Nevertheless I think it makes sense to have everything in one place,
so if we don't trust GitHub for our issues, maybe we should re-think
pull requests and code review?
Maybe we could move everything to GitHub and setup a mirror of all
comments and issues using the GitHub api?
I think by moving on GitHub we might be able to attract more people
who are already familiar with GitHub as almost nobody (I mean of the
people who join DokuWiki) is familiar with Flyspray but some are
familiar with GitHub and as many plugins are already using the GitHub
issue tracker it could provide a more consistent user experience.
Michael
--
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist
Other related posts:
