From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: How about a Gnus Bugzilla?
Date: 15 Oct 2004 11:08:31 -0400 [thread overview]
Message-ID: <4nbrf4c93k.fsf@lifelogs.com> (raw)
In-Reply-To: <87zn2p85zi.fsf@dod.no> (Steinar Bang's message of "Thu, 14 Oct 2004 21:17:05 +0200")
On Thu, 14 Oct 2004, sb@dod.no wrote:
>>>>>> "Ted Zlatanov" <tzz@lifelogs.com>:
>
>> It's extra work to monitor and maintain Bugzilla for Gnus
>> contributors. I have plenty to monitor with the 2 newsgroups and
>> the mailing list, so I'm not sure this is a good idea. Maybe if it
>> was read-only for outside users, so contributors could decide if a
>> bug goes in. I would hate to spend my day answering questions with
>> WORKSFORME and explanations like the Mozilla guys do.
>
> The idea of a bugtracker is to track bugs in a traceable way, which,
> as far as I can tell, bugzilla does really well.
>
> In that context, I'm not sure I understand the problem you're
> describing. Could you perhaps elaborate on it?
You are forgetting the bug submission process. I don't want every
Gnus user to submit bugs, only developers and qualified users. In the
Mozilla project, a lot of the bugs are things that the user simply
doesn't understand. If I take the burden of tracking bugs, I want to
make sure they are real and not something best answered in the other
Gnus forums.
Just my 5 cents.
Ted
next prev parent reply other threads:[~2004-10-15 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 11:04 Steinar Bang
2004-10-14 17:51 ` Xavier Maillard
2004-10-14 18:44 ` Ted Zlatanov
2004-10-14 19:17 ` Steinar Bang
2004-10-15 15:08 ` Ted Zlatanov [this message]
2004-10-15 19:28 ` Steinar Bang
2004-10-19 13:41 ` Bjørn Mork
2004-10-14 20:14 ` Reiner Steib
2004-10-14 21:31 ` Xavier Maillard
2004-10-15 8:40 ` Adam Sjøgren
2004-10-16 9:03 ` Xavier Maillard
2004-10-14 19:12 ` Steinar Bang
2004-10-14 20:22 ` Wes Hardaker
2004-10-15 5:16 ` Steinar Bang
2004-10-14 21:50 ` Jesper Harder
2004-10-15 5:27 ` Steinar Bang
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=4nbrf4c93k.fsf@lifelogs.com \
--to=tzz@lifelogs.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).