From: ycollette.nospam@free.fr
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: Add a bugzilla website
Date: Mon, 18 Nov 2013 08:37:19 +0100 (CET) [thread overview]
Message-ID: <1186100344.320778474.1384760239079.JavaMail.root@zimbra35-e6.priv.proxad.net> (raw)
In-Reply-To: <20131115225709.GC314350@vauxhall.crustytoothpaste.net>
On most linux distro bugzilla website, there are some people dedicated to triaging bugs (finding duplicated bugs, asking for more informations, closing old and / or resolved bugs).
To have an efficient bugtracking tool needs to have some people dedicated to this.
But for the user, it's a better approach. For example, I do not need to register to the devel list and I do not have to watch all mails to locate the one which concerns my bug.
It works nicely with fedora, magieia and other distro / tools, so I don't know why this shouldn't work fine with git ?
But as far as I can read, most people here are very reluctant to use a bugtracking tool ...
YC
----- Mail original -----
De: "brian m. carlson" <sandals@crustytoothpaste.net>
À: "ycollette nospam" <ycollette.nospam@free.fr>
Cc: git@vger.kernel.org
Envoyé: Vendredi 15 Novembre 2013 23:57:09
Objet: Re: Add a bugzilla website
On Fri, Nov 15, 2013 at 10:40:47AM +0100, ycollette.nospam@free.fr wrote:
> And the conclusion is ? No bugzilla tool installed because somebody
> want to build a gitbased bugzilla thing ?
Personally, I do not want Yet Another Bugzilla Account. A project is
significantly less likely to get a patch from me if I have to create an
account to report a bug. Most of the patches I send to various projects
are for bugs I've experienced and want to provide a fix for, so I send a
small number of patches to many projects.
I feel that the mailing list workflow ends up working very well for Git
and it provides a low barrier to entry for those that want to send just
one or two patches for problems that they're experiencing. It also
allows me to see and comment on virtually every patch on the list, while
ignoring threads I am not interested in, a combination which is
difficult to achieve with a web-based bug tracker.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
next prev parent reply other threads:[~2013-11-18 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1501110902.314721105.1384501257984.JavaMail.root@zimbra35-e6.priv.proxad.net>
2013-11-15 7:44 ` Add a bugzilla website ycollette.nospam
2013-11-15 8:53 ` Damien Wyart
2013-11-15 9:40 ` ycollette.nospam
2013-11-15 9:51 ` Konstantin Khomoutov
2013-11-15 10:34 ` ycollette.nospam
2013-11-15 10:50 ` Matthieu Moy
2014-01-08 9:24 ` David Aguilar
2013-11-15 17:27 ` Andrew Ardill
2013-11-15 19:19 ` Jonathan Nieder
[not found] ` <CADoxLGPnoo_fXsQXE2jb_H4Otf9eRWsN=nQP9smhPbt20H-72Q@mail.gmail.com>
2014-01-13 1:06 ` Fwd: " Stefan Saasen
2013-11-15 22:57 ` brian m. carlson
2013-11-18 7:37 ` ycollette.nospam [this message]
2013-11-18 12:40 ` Matthieu Moy
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=1186100344.320778474.1384760239079.JavaMail.root@zimbra35-e6.priv.proxad.net \
--to=ycollette.nospam@free.fr \
--cc=git@vger.kernel.org \
/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).