Re: Helping on Git development

Junio C Hamano wrote:

As to contributing to the project, right now, I think we have enough
people who want to write code and documentation for Git, but what we lack
are bandwidth to (this is not meant to be an exhaustive list):

[...]

 - distilling random wishes from the end user community while winnowing
   chaffs that are unrealistic or do not fit well with the grand scheme of
   things, to come up with a concrete proposal and a patch series

[...]

 - dig list archives to point people at age-old discussions to non-issues
   that have long been resolved to squelch noise; and

 - remind original submitter, people who were involved in the discussion,
   and people who should have been involved but who weren't, of a worthy
   but stalled topics from time to time.

I also should (reluctantly) mention that the Debian bug tracker has
been accepting bugs from outsiders and provides a service like this.
Caveats:

 - it only tracks bugs that affect Debian (usually meaning
   platform-independent bugs).  Occasionally bugs from Windows users
   have been reported there and it's been okay.

 - the interface might seem quirky if you're not used to it.
   Documentation is at http://www.debian.org/Bugs/

 - no guarantee of a quick response.  When there is a response,
   usually it is "here are some thoughts; now let's take this to
   git@vger.kernel.org".

 - if the bugtracker gets swamped with reports from outside without
   manpower to match, the policy re bugs from outside Debian might
   change.

Bug listing: [1].
To subscribe to receive bug reports by email: [2].

Thoughts welcome, as always.
Jonathan

[1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=git;include=tags:upstream;exclude=tags:fixed-upstream;exclude=tags:moreinfo;exclude=severity:wishlist
[2] http://www.debian.org/doc/manuals/developers-reference/resources.html#pts-commands
Summary: an email to pts@qa.debian.org whose body contains the two
lines "subscribe git", "keyword git = bts" would do the trick.