public inbox for [email protected]  

help / color / mirror / Atom feed

From: Josh Berkus <[email protected]>
To: Tom Lane <[email protected]>
To: Neil Conway <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [HACKERS] Collaboration Tool Proposal
Date: Thu, 26 Feb 2004 22:10:21 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Tom,

> Our first try at a bug tracking system, several years ago, was open to
> anybody to create entries, and we found that the signal-to-noise ratio
> went to zero in no time.  Too many not-a-bugs, too many support
> requests, too few actual bugs.  We went back to using the pgsql-bugs
> mailing list.

I actually sort of agree with Tom, although I don't want to raise the barrier 
too high.   I'd suggest allowing all registered users to submit bugs.   
Needing to go through registration should severely reduce the "noise", even 
if we give no restriction on who can register.

I field the Advocacy webform right now, and only get about 10 e-mails a day, 
even though some of those are really support requests better handled by the 
mailing lists.   I think we could handle 5 bad bug reports a day.

> As for raising the barrier, you can presently submit bug reports to
> pgsql-bugs by either mail or webform.  Most of the bug trackers I'm
> aware of are webform-only.  I don't consider that a step forward,
> especially since a webform isn't very conducive to making good reports
> (it's hard to attach test cases, for instance).

Both the BZ and GForge webforms allow uploading files.   And I'd far rather 
have a single copy of a test case on our web site than a couple dozen being 
e-mailed out.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco

view thread (62+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Collaboration Tool Proposal
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox