From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs465952agc; Mon, 2 Nov 2009 06:58:41 -0800 (PST) Received: by 10.224.65.69 with SMTP id h5mr267252qai.190.1257173921110; Mon, 02 Nov 2009 06:58:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 3si7532803qyk.68.2009.11.02.06.58.40; Mon, 02 Nov 2009 06:58:41 -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 C82031588066; Mon, 2 Nov 2009 09:58:40 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3526C1858292 for ; Mon, 2 Nov 2009 09:58:18 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N4yMM-000193-4A for sup-talk@rubyforge.org; Mon, 02 Nov 2009 06:58:18 -0800 From: William Morgan To: sup-talk In-reply-to: <1257154664-sup-90@tilus.net> References: <1257111816-sup-4397@peray> <1257143690-sup-7839@tilus.net> <1257150627-sup-1843@peray> <1257154664-sup-90@tilus.net> Date: Mon, 02 Nov 2009 06:58:18 -0800 Message-Id: <1257173616-sup-9298@masanjin.net> 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 Reformatted excerpts from Tero Tilus's message of 2009-11-02: > Unless you take service, not the bare tool. We are already using > gitorius and rubyforge (at least to some extent). I'd go for a issue > tracking service that suits our needs. I'm not dead-set against a hosted solution, but I am wary of making too much of the development cycle reliant on third parties. E.g. I see people who can't get any work done when Github is down. Well, that's not Github's fault, per se, but they've integrated it into their process to such an extent that they're now reliant on it. Not to say that that would happen with just an issue tracker. But still, our use of Gitorious and Rubyforge is pretty minimal right now, and I feel good about that. (And honestly I find Gitorious merge requests a little irritating, because they're invariably not rebased properly against master and I have to have the same discussion every time.) -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk