From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs446483agc; Mon, 2 Nov 2009 00:30:33 -0800 (PST) Received: by 10.224.33.3 with SMTP id f3mr2734581qad.24.1257150633397; Mon, 02 Nov 2009 00:30:33 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 17si6965829qyk.103.2009.11.02.00.30.33; Mon, 02 Nov 2009 00:30:33 -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 12BA63C8056; Mon, 2 Nov 2009 03:30:32 -0500 (EST) Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by rubyforge.org (Postfix) with ESMTP id F2F7018580F5 for ; Mon, 2 Nov 2009 03:30:03 -0500 (EST) X-IronPort-AV: E=Sophos;i="4.44,665,1249250400"; d="scan'208";a="39340755" Received: from peray.inria.fr (HELO localhost) ([128.93.8.98]) by mail1-relais-roc.national.inria.fr with ESMTP; 02 Nov 2009 09:30:03 +0100 From: Nicolas Pouillard To: Kevin Riggle In-reply-to: <1257124377-sup-199@black-opal.mit.edu> References: <1257111816-sup-4397@peray> <1257124377-sup-199@black-opal.mit.edu> Date: Mon, 02 Nov 2009 09:30:03 +0100 Message-Id: <1257150469-sup-7051@peray> User-Agent: Sup/git Cc: sup-talk 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 Kevin Riggle's message of Mon Nov 02 02:17:31 +0100 2009: > 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. SD looks indeed really fun, however I think it fails my simplicity goal. Indeed the tool expose tons of commands and try to abstract how it is made, I'm in favor of better knowing the underlying store (a YAML file), and simply storing it with usual DVCS tools. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk