From: Jan Hudec <bulb@ucw.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Thomas Harning <harningt@gmail.com>,
Pierre Habouzit <madcoder@debian.org>,
git@vger.kernel.org
Subject: Re: [RFC] Idea for Git Bugtracking Tool
Date: Sun, 9 Mar 2008 09:26:40 +0100 [thread overview]
Message-ID: <20080309082640.GA22732@efreet.light.src> (raw)
In-Reply-To: <m3zltaf7vs.fsf@localhost.localdomain>
On Fri, Mar 07, 2008 at 15:10:18 -0800, Jakub Narebski wrote:
> [...]
> There exists few implementations of distributed bug tracker idea. They
> include:
>
> * Bugs Everywhere (http://bugseverywhere.org), written in Python,
> developed in Bazaar, has Git backend support. Formerly written by
> Panoramic Feedback (note that there is stale version of this tool),
> picked up by one of developers
I recall Pierre mentioning that he didn't like some things on this back then
when he talked about Grit. Particularly, I believe, the way it suggested to
have the bugs in the same branch as source to keep them in sync. It might be
possible to use it in different way though.
> * DisTract (http://www.distract.wellquite.org), written in Haskell,
> uses Monotone as backend. Has good reviews on blogs, e.g. by
> Masukomi.
Sounds a little overcomplicated with the monotone storage and firefox UI.
> * DITrack (http://www.ditrack.org), written in Python, currently
> uses Subversion as backend, has plans to be backend-agnostic.
> Inspired by Subissue.
I wish them good luck. The problem is, that this is /not/ distributed,
because they use sequential bug numbers, which they'd have to change if they
wanted to use Git.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2008-03-09 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:22 [RFC] Idea for Git Bugtracking Tool Thomas Harning
2008-03-06 20:08 ` Matthieu Moy
2008-03-07 23:10 ` Jakub Narebski
2008-03-08 13:42 ` Pierre Habouzit
2008-03-08 14:23 ` Jakub Narebski
2008-03-08 15:02 ` Pierre Habouzit
2008-03-09 8:26 ` Jan Hudec [this message]
2008-03-11 3:29 ` Thomas Harning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080309082640.GA22732@efreet.light.src \
--to=bulb@ucw.cz \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=harningt@gmail.com \
--cc=jnareb@gmail.com \
--cc=madcoder@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).