From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs429165agc; Sun, 1 Nov 2009 17:21:37 -0800 (PST) Received: by 10.224.116.133 with SMTP id m5mr2539967qaq.214.1257124895835; Sun, 01 Nov 2009 17:21:35 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 27si6647364qyk.123.2009.11.01.17.21.35; Sun, 01 Nov 2009 17:21:35 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 82D5818582D5; Sun, 1 Nov 2009 20:21:35 -0500 (EST) Received: from granite.free-dissociation.com (207-180-139-38.ma.subnet.cable.rcn.com [207.180.139.38]) by rubyforge.org (Postfix) with ESMTP id A06FA18582C7 for ; Sun, 1 Nov 2009 20:17:34 -0500 (EST) Received: from 207-180-139-39.ma.subnet.cable.rcn.com ([207.180.139.39] helo=localhost) by granite.free-dissociation.com with esmtpsa (TLS-1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.63) (envelope-from ) id 1N4lX9-0006pj-Ck; Sun, 01 Nov 2009 20:16:35 -0500 From: Kevin Riggle To: sup-talk In-reply-to: <1257111816-sup-4397@peray> References: <1257111816-sup-4397@peray> Date: Sun, 01 Nov 2009 20:17:31 -0500 Message-Id: <1257124377-sup-199@black-opal.mit.edu> User-Agent: Sup/git Subject: Re: [sup-talk] Choosing a bug tracker for Sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Nicolas Pouillard's message of Sun Nov 01 16:52:08 -0500 2009: (snip) (snip) > > I would store and manage the first category using a simple YAML file. > > The bot acknowledges its updates by simply answering to the discussion. > > Those of the second category can be managed using a single email discussion. > > Since the discussion is central to the issue, tracking the original message-ID > could be used as the unique identifier. > > About the issues identifier I see two options, either we try to allocate > simple integers like most of the trackers or we just keep the unique (long) > identifier. > > Then, optionally a simple set of HTML pages can be generated using the YAML > file. > > About storage of the YAML file I would simply store it in the repository. > If we make the bot accessible, we just have to periodically pull > from it. > This portion of your proposed system sounds to me a lot like SD (http://syncwith.us), against which writing your proposed bot would be fairly straightforward. - Kevin -- Kevin Riggle (kevinr@free-dissociation.com) MIT Class of 2010, Course VI-2 (EECS) http://free-dissociation.com _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk