From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs3295agb; Mon, 2 Nov 2009 12:47:09 -0800 (PST) Received: by 10.224.118.129 with SMTP id v1mr3108848qaq.274.1257194829233; Mon, 02 Nov 2009 12:47:09 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 15si7589553qyk.23.2009.11.02.12.47.08; Mon, 02 Nov 2009 12:47:08 -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; DomainKey-Status: bad 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; domainkeys=hardfail header.From=joe@talkhouse.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DF55816782B5; Mon, 2 Nov 2009 15:47:07 -0500 (EST) X-Greylist: delayed 395 seconds by postgrey-1.31 at rubycentral.org; Mon, 02 Nov 2009 15:47:02 EST Received: from outbound-mail-37.bluehost.com (outbound-mail-37.bluehost.com [69.89.20.191]) by rubyforge.org (Postfix) with SMTP id 528531598079 for ; Mon, 2 Nov 2009 15:47:04 -0500 (EST) Received: (qmail 18289 invoked by uid 0); 2 Nov 2009 20:40:24 -0000 Received: from unknown (HELO box392.bluehost.com) (69.89.31.192) by outboundproxy2.bluehost.com with SMTP; 2 Nov 2009 20:40:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=talkhouse.com; h=Received:Content-Type:Subject:From:To:In-reply-to:References:Date:Message-Id:User-Agent:Content-Transfer-Encoding:X-Identified-User; b=c56IFO7a9sjvo1nSQuYpiWGF3DlAkvRb/q1U4gQiWp1op5Ieuwp4sYiZ/OJpPpBNlg+dSeqZVsOelFBu1XWjRcParR+hlKKMwbIUozolo3zvlDNATI2wfQz2vkzLfGzS; Received: from c-174-48-135-109.hsd1.fl.comcast.net ([174.48.135.109] helo=localhost) by box392.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1N53hO-0004Ib-Cc for sup-talk@rubyforge.org; Mon, 02 Nov 2009 13:40:24 -0700 From: =?utf-8?q?Joe_W=C3=B6lfel?= To: sup-talk In-reply-to: <1257169654-sup-6224@masanjin.net> References: <1257111816-sup-4397@peray> <1257169654-sup-6224@masanjin.net> Date: Mon, 02 Nov 2009 15:40:21 -0500 Message-Id: <1257193345-sup-3174@maui.local> User-Agent: Sup/0.8 X-Identified-User: {2758:box392.bluehost.com:talkhous:talkhouse.com} {sentby:smtp auth 174.48.135.109 authed with joe@talkhouse.com} 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 William Morgan's message of Mon Nov 02 09:50:08 -0500 2009: > 1. Web submission. The burden of creating a record should be on the > submitter---it's not too much to ask, and it saves developer time. This > also encourages reporters to provide relevant information like version, > platform, Ruby version, etc. upfront, since they can be prompted for > those data explicitly. > > 2. Developer discussion via email. This is vital. There's no way I would > want to have a technical discussion using text boxes on a website. And > this discussion should be attached to the issue, of course. Please ignore this suggestion if you feel it is stupid, but couldn't an internal sup-based bug submission perform prompting and validation tasks just as easily as a web form? Also, wouldn't it be better for automatically including or verifying operating system info, version info, libraries, etc? It seems like this might make for a more natural transition to email-based developer discussion, reduce the need for centralized infrastructure, make it easier for users to figure out how and where to submit a bug, and possibly make critical system and library information more accurate and detailed. Cheers, Joe _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk