From: Phil Hord <phil.hord@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Neal Kreitzinger <nkreitzinger@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Thomas Rast <trast@inf.ethz.ch>,
Andrew Ardill <andrew.ardill@gmail.com>,
opticyclic <opticyclic@gmail.com>,
git@vger.kernel.org
Subject: Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests
Date: Wed, 7 Mar 2012 12:18:36 -0500 [thread overview]
Message-ID: <CABURp0q7fJLBHGGdD7EQ6pwEu=zErKHz+ZZJ5HLVe5VO2Y66gQ@mail.gmail.com> (raw)
In-Reply-To: <7vsjhrfprz.fsf@alter.siamese.dyndns.org>
On Fri, Mar 2, 2012 at 2:03 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Neal Kreitzinger <nkreitzinger@gmail.com> writes:
>
>> I realize this is not an exact match of the git-workflow, but you get
>> the idea. I'm also new to mailinglists so I'm not sure if you can
>> change part of the subject line. If not, a header in the body could
>> possibly be used.
>
> The most important information is missing from your discussion: who are
> you trying to help, and what problem are you trying to solve?
Problems this could help solve (regardless of whether it's an
appropriate tool for the job):
1. Collects issues into a more concise list than the mailing list provides.
2. Collects issues (and discussion) conveniently bundled with the git
source code.
3. Collects issues for off-line reference and searching.
4. Reduction of list noise, if issues in git.git turn out to be better
grep-targets than the mailing list.
5. Serves as an incubator for a git-based distributed issues tracker
Best Practice or Dire Warning, depending on how it goes.
The current mailing list bug tracker, where finding existing issues
and previous discussions is "crowd-sourced" to the list, is very
efficient for the new users, but not so efficient for the core
developers and respondents.
I doubt this idea is really workable or appropriate for git.git, for
various reasons. But I do think a well-designed, distributed,
git-based issue tracker could be useful for many other projects. Many
others have tried and failed, so I am probably wrong about this last
statement. See [*1*] for a list of mostly stagnating prior art.
Phil
[*1*] http://dist-bugs.branchable.com/software/
next prev parent reply other threads:[~2012-03-07 17:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:19 Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests opticyclic
2012-02-29 18:23 ` Brian Gernhardt
2012-02-29 18:53 ` Junio C Hamano
2012-02-29 22:53 ` Jonathan Nieder
2012-02-29 23:58 ` Andrew Ardill
2012-03-01 0:37 ` Greg Troxel
2012-03-01 0:45 ` Andrew Ardill
2012-03-01 0:50 ` Junio C Hamano
2012-03-01 1:05 ` Andrew Ardill
2012-03-01 1:05 ` Junio C Hamano
2012-03-01 1:20 ` Andrew Ardill
2012-03-01 5:16 ` Miles Bader
2012-03-01 5:40 ` Andrew Ardill
2012-03-01 16:52 ` Scott Chacon
2012-03-01 20:23 ` Junio C Hamano
2012-03-01 11:29 ` Thomas Rast
2012-03-01 11:54 ` Ævar Arnfjörð Bjarmason
2012-03-01 12:46 ` Andrew Ardill
2012-03-01 12:28 ` Andrew Ardill
2012-03-01 17:10 ` Junio C Hamano
2012-03-02 4:03 ` Neal Kreitzinger
2012-03-02 4:19 ` Jonathan Nieder
2012-03-02 4:21 ` Junio C Hamano
2012-03-02 5:50 ` Neal Kreitzinger
2012-03-02 6:25 ` Jonathan Nieder
2012-03-02 7:03 ` Junio C Hamano
2012-03-02 14:18 ` Andreas Ericsson
2012-03-02 16:45 ` Junio C Hamano
2012-03-07 8:03 ` Andrew Ardill
2012-03-07 9:52 ` Vincent van Ravesteijn
2012-03-07 13:04 ` Joern Huxhorn
2012-03-07 13:53 ` Jonathan Nieder
2012-03-07 14:47 ` Joern Huxhorn
2012-03-07 15:08 ` Pau Garcia i Quiles
2012-03-07 17:18 ` Phil Hord [this message]
2012-02-29 19:18 ` Carlos Martín Nieto
2012-02-29 21:37 ` Sitaram Chamarty
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABURp0q7fJLBHGGdD7EQ6pwEu=zErKHz+ZZJ5HLVe5VO2Y66gQ@mail.gmail.com' \
--to=phil.hord@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=nkreitzinger@gmail.com \
--cc=opticyclic@gmail.com \
--cc=trast@inf.ethz.ch \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).