Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 9EC4A16FA502 for ; Mon, 9 Jul 2012 18:56:17 -0300 (ADT) Received: from smtp.01.com ([199.36.142.181]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SoLwE-0006Jw-HA for pgsql-hackers@postgresql.org; Mon, 09 Jul 2012 21:56:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 702044F63E6 for ; Mon, 9 Jul 2012 16:56:00 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3yfpJe4Yq4r for ; Mon, 9 Jul 2012 16:56:00 -0500 (CDT) Received: from smtp.01.com (localhost.localdomain [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 4AC904F6481 for ; Mon, 9 Jul 2012 16:56:00 -0500 (CDT) Received: from Sidney-Stratton.local (70-36-143-92.dsl.dynamic.sonic.net [70.36.143.92]) by smtp-out-2.01.com (Postfix) with ESMTPSA id E6B9B4F63E6 for ; Mon, 9 Jul 2012 16:55:59 -0500 (CDT) Message-ID: <4FFB536F.5020206@agliodbs.com> Date: Mon, 09 Jul 2012 14:55:59 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: Bug tracker tool we need References: <1334758503.29544.14.camel@vanquo.pezone.net> <20120706192141.GA11753@momjian.us> <20120706234626.GB26828@momjian.us> <20120707104851.GA525@svana.org> <20120707144211.GE26828@momjian.us> <20120707144805.GG26828@momjian.us> <4FFB2ADC.4040407@agliodbs.com> <4FFB306B.9000901@commandprompt.com> In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/413 X-Sequence-Number: 211096 >>> -- Bug Submitter: easy-access way for users to submit bugs and check on >>> their status later. > >> Not sure how to handle the first two. Bug submission is always a pita and >> although we could use the fix-bug-later app, it would clutter it as we were >> trying to determine real bugs vs user error. > > And whatever you/we do, be *VERY* aware of the > "pile-of-...-in-the-bugtracker problem". I just happend to have Joel > Spolsky's post come through my RSS reader, where he talked about about > bugtrackers, and suggested: Well, frankly, I don't think we really want to make it easier for the *general public* to submit bugs than it already is. We're already getting enough quality bug reports to keep us busy. And I'm all-too-familiar with the failings of a "bug-losing system"; check the number of bugs I have filed against Thunderbird sometime. Where bug submission is broken that we care about is in two areas: 1. it's very difficult for the existing bug submitters to check status of their bugs after submission, or even find out if they went anywhere (if using the webform). 2. we don't have an API for downstream projects and products to submit bugs, which makes those projects think we don't care about bugs. Note that both of the above could be solved without having a public bugzilla instance. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com