From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Why Emacs needs a modern bug tracker Date: Sun, 06 Jan 2008 08:46:41 +0900 Message-ID: <87y7b3zvha.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20080104164454.0A4BD830697@snark.thyrsus.com> <20080104232514.GB2735@muc.de> <20080105052007.GA27075@thyrsus.com> <20080105111720.GA3014@muc.de> <20080105145743.GH30869@thyrsus.com> <86prwg9h9m.fsf@pullcord.laptop.org> <20080105212643.GX30869@thyrsus.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199576573 29451 80.91.229.12 (5 Jan 2008 23:42:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Jan 2008 23:42:53 +0000 (UTC) Cc: "Eric S. Raymond" , Chris Ball , Alan Mackenzie , emacs-devel@gnu.org To: esr@thyrsus.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 06 00:43:13 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBIfO-0000ws-5j for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 00:43:10 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBIey-0006l4-Bt for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 18:42:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBIeh-0006Lg-2g for emacs-devel@gnu.org; Sat, 05 Jan 2008 18:42:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBIec-0006Ac-DT for emacs-devel@gnu.org; Sat, 05 Jan 2008 18:42:17 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBIec-0006A6-6Q for emacs-devel@gnu.org; Sat, 05 Jan 2008 18:42:14 -0500 Original-Received: from mtps02.sk.tsukuba.ac.jp ([130.158.97.224]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBIeY-0008VE-NO for emacs-devel@gnu.org; Sat, 05 Jan 2008 18:42:14 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps02.sk.tsukuba.ac.jp (Postfix) with ESMTP id 2C1C58001; Sun, 6 Jan 2008 08:42:00 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id A68601A29E5; Sun, 6 Jan 2008 08:46:42 +0900 (JST) In-Reply-To: <20080105212643.GX30869@thyrsus.com> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" (+CVS-20071205) XEmacs Lucid X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86264 Archived-At: Eric S. Raymond writes: > > I think it's appealing to have a checkout of the bug database available > > alongside a source code checkout. Bugs Everywhere is not finished yet, > > but can use many different VCS backends including arch, bzr and hg. > > I have a small patch to add GIT support to it, too. > > This sounds interesting. How close would you say it is to production status? Interesting, yes, but a word of caution: a bug database is like a market. Markets are most useful when *every* bid and ask is published. As soon as you allow secret dealing, things become less liquid. Similarly, unless bugs are more or less automatically pushed to the public interface, it's not going to be as useful for communicating with casual users and developers. The easiest and least invasive way to achieve automatic pushing is to have only the public interface for bug entry. Of course the motivations for "secrecy" are personal profit in the market and "laziness" in the bug tracker, but the chilling effects on information flow will be qualitatively similar. Quantitatively? "Try it and see." But be prepared with Plan B.