From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
Eduardo D'Avila <erdavila@gmail.com>,
git@vger.kernel.org, git@packages.debian.org
Subject: Re: Helping on Git development
Date: Wed, 14 Sep 2011 16:32:03 -0500 [thread overview]
Message-ID: <20110914213202.GA20473@elie> (raw)
In-Reply-To: <7vehzjugdz.fsf@alter.siamese.dyndns.org>
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.
next prev parent reply other threads:[~2011-09-14 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOz-D1JW8RSR8kVWhT7v-DCbWayU8KhbePJwWrWvJwbmueRezQ@mail.gmail.com>
2011-09-14 3:05 ` Helping on Git development Eduardo D'Avila
2011-09-14 5:16 ` Andrew Ardill
2011-09-14 18:29 ` Junio C Hamano
2011-09-14 21:32 ` Jonathan Nieder [this message]
2011-09-14 23:14 ` Jeff King
2011-09-14 23:34 ` Junio C Hamano
2011-09-15 0:08 ` Jeff King
2011-09-15 6:24 ` Andrew Ardill
2011-09-15 15:50 ` Junio C Hamano
2011-09-15 17:21 ` Jeff King
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=20110914213202.GA20473@elie \
--to=jrnieder@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=erdavila@gmail.com \
--cc=git@packages.debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).