From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Thomas Harning <harningt@gmail.com>,
Pierre Habouzit <madcoder@debian.org>, <git@vger.kernel.org>
Subject: Re: [RFC] Idea for Git Bugtracking Tool
Date: Fri, 07 Mar 2008 15:10:18 -0800 (PST) [thread overview]
Message-ID: <m3zltaf7vs.fsf@localhost.localdomain> (raw)
In-Reply-To: <vpqskz3pqdo.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> Thomas Harning <harningt@gmail.com> writes:
>
>> Any ideas/flaws with this concept? Anybody up for taking on this
>> project... or for taking this up as a GSOC project mentor?
>
> Already discussed here:
>
> http://thread.gmane.org/gmane.comp.version-control.git/48981/
>
> Pierre Habouzit started working on something called grit, which
> seems to be dead.
Pierre, what happened to git://git.madism.org/grit.git ?
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
* DisTract (http://www.distract.wellquite.org), written in Haskell,
uses Monotone as backend. Has good reviews on blogs, e.g. by
Masukomi.
* DITrack (http://www.ditrack.org), written in Python, currently
uses Subversion as backend, has plans to be backend-agnostic.
Inspired by Subissue.
Other links (mainly blogs):
http://erlangish.blogspot.com/2007/05/distributed-bug-tracking.html
http://erlangish.blogspot.com/2007/06/distributed-bug-tracking-again.html
http://weblog.masukomi.org/2008/1/3/distributed-bug-tracking
http://weblog.masukomi.org/2008/1/20/more-thoughts-on-the-future-of-distributed-bug-tracking
http://www.geekfire.com/~alex/blog/entries/Ideas-for-a-distributed-bug-tracking-system/Ideas-for-a-distributed-bug-tracking-system.html
--
Jakub Narebski
ShadeHawk on #git
Poland
next prev parent reply other threads:[~2008-03-07 23:11 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 [this message]
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
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=m3zltaf7vs.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=harningt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.