Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 8C9AE13F0F80 for ; Sat, 14 Apr 2012 04:02:44 -0300 (ADT) Received: from 30.55.colo.spiretech.net ([69.168.55.30] helo=lists.commandprompt.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SIx0M-0003tZ-RM for pgsql-hackers@postgresql.org; Sat, 14 Apr 2012 07:02:43 +0000 Received: from clam (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 011B192; Sat, 14 Apr 2012 00:02:33 -0700 (PDT) Received: from clam ([195.88.15.88] helo=clam) by assp.commandprompt.com with ESMTPS(AES128-SHA) (2.1.1); 14 Apr 2012 00:02:30 -0700 From: Alex To: Peter Eisentraut Cc: Robert Haas , Tom Lane , Greg Smith , pgsql-hackers@postgresql.org Subject: Re: Last gasp References: <4F7E99BA.1080805@2ndQuadrant.com> <20120409053852.GG11987@tornado.leadboat.com> <20120409222359.GE30702@tornado.leadboat.com> <4F83FCB10200002500046D70@gw.wicourts.gov> <4F84D3A0.8010808@2ndQuadrant.com> <1334165303.25392.9.camel@vanquo.pezone.net> <28338.1334168965@sss.pgh.pa.us> <1334180206.25392.39.camel@vanquo.pezone.net> <1334350086.9019.16.camel@vanquo.pezone.net> Date: Sat, 14 Apr 2012 10:02:21 +0300 In-Reply-To: <1334350086.9019.16.camel@vanquo.pezone.net> (Peter Eisentraut's message of "Fri, 13 Apr 2012 23:48:06 +0300") Message-ID: <878vhyeqyq.fsf@commandprompt.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Assp-Version: 2.1.1(11364) on assp.commandprompt.com X-Assp-Client-TLS: yes X-Assp-ID: assp.commandprompt.com m1-86953-06727 X-Assp-Envelope-From: ash@commandprompt.com X-Assp-Intended-For: pgsql-hackers@postgresql.org X-Assp-Original-Subject: Re: [HACKERS] Last gasp X-Pg-Spam-Score: -0.6 (/) X-Archive-Number: 201204/723 X-Sequence-Number: 206526 Peter Eisentraut writes: > On ons, 2012-04-11 at 23:30 -0400, Robert Haas wrote: >> Now what would be sort of neat is if we had a way to keep all the >> versions of patch X plus author and reviewer information, links to >> reviews and discussion, etc. in some sort of centralized place. > > Well, a properly linked email thread contains all this. I have seen a > couple of anti-patterns evolving, though, including patch authors > starting a new email thread for each patch version, and reviewers > starting a new email thread for each review. When that happens, the > existence of the commitfest app makes things worse, in a way. (Of > course, any discussion here about bug trackers emphasizes the need for > email to be the primary communications method for this very reason.) I didn't follow this whole thread, but have we considered Redmine[1]? We at CMD rely on it as the primary means of customer communication, via email. New email to a mailing list backed by Redmine triggers new ticket creation and any followups result into an update to the ticket. The ticket history is searchable, browsable (and updateable) on the web. It's GPL-ed, uses Ruby on Rails, and comes with a broad range of plugins[2]. Also it is quite hackable (for a RoR guy, of course.) We could integrate Redmine with the CommitFest or even replace it completely with a custom-written plugin. A command line interface[3] exists, so 'cf close ###' suggested further in this thread should be also possible. -- Regards, Alex [1] http://www.redmine.org/ [2] http://www.redmine.org/plugins [3] https://github.com/diasjorge/redmine-cli