git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Idea for Git Bugtracking Tool

From
JHJan Hudec <bulb@ucw.cz>
Date
Mar 9, 2008, 08:26 UTC
Message-ID
<20080309082640.GA22732@efreet.light.src>
In-Reply-To
<m3zltaf7vs.fsf@localhost.localdomain>
On Fri, Mar 07, 2008 at 15:10:18 -0800, Jakub Narebski wrote:
Show 8 quoted lines
> [...]
> 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>
Previous: Pierre HabouzitNext: Thomas Harning
Message 7 of 8 in “[RFC] Idea for Git Bugtracking Tool”
  1. Thomas HarningMar 6, 2008
  2. Matthieu MoyMar 6, 2008
  3. Jakub NarebskiMar 7, 2008
  4. Pierre HabouzitMar 8, 2008
  5. Jakub NarebskiMar 8, 2008
  6. Pierre HabouzitMar 8, 2008
  7. Jan HudecMar 9, 2008
  8. Thomas HarningMar 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.