Re: Git Survey summary

From: Shawn Pearce <spearce@spearce.org>
Date: Sep 21, 2006, 15:56 UTC
Message-ID: <20060921155617.GB3934@spearce.org>
In-Reply-To: <eeuapj$mgn$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> wrote:

Show 10 quoted lines

> Nguy?n Thái Ng?c Duy wrote:
> 
> >  - A place to post bugs and feature requests (if bugzilla is too big,
> > maybe mantis?)
> 
> Isn't this mailing list the place to post bugreports and feature requests
> (and of course patches)? Any bugtracker has to be tied to mailing list, and
> perhaps also two-way to gitweb (gitweb making links to bugtracker issues,
> bugtracker having links to gitweb; perhaps incrementing revision
> numbers...).

Its funny, some communities are based around their bug tracking systems (Mozilla) and others around their mailing lists (kernel, git). Both work, but only if those participating make it so. Trying to force one type of community into another model can kill it.

I'm all for hyperlink integration of gitweb and bug tracking systems but bug tracking tends to be a personal preference; there's so many choices. So whatever support is in gitweb needs to be pretty modular to allow users to drop in the configuration for whatever bug tracking system a given repository uses.

Since Git uses a mailing list model it would be nice if the gitweb hyperlinks were into the marc and GMane archives by Message-ID; but that would also require that commits start including the Message-ID of the thread which spawned the patches. It would also be nice if the links were able to jump to the discussion about the patch, as sometimes the patch thread is different from the spawning thread.

-- 
Shawn.