From owner-freebsd-arch@FreeBSD.ORG Sat Aug 27 19:29:41 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2885106566B for ; Sat, 27 Aug 2011 19:29:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AB7E78FC0A for ; Sat, 27 Aug 2011 19:29:41 +0000 (UTC) Received: by vxh11 with SMTP id 11so4437638vxh.13 for ; Sat, 27 Aug 2011 12:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BA9akaGU1GS2BorApO8dVFrs8o3IZcgZV+sKnvy7Mzs=; b=oDX/IdTBujZZhkUEhEyMTz9VynisMiMtgigqDqk+1L9kFyABzwWtD8Je72P+g8Qr+P Q356depp55bv5egSYw8KgDGuYxRTfq92ogD8VX8FAIyFza7oWVJVViJB/+WCBGzKdPti Yl6/RnJRgGmaegf0cNHUVcCnVGC32qRfz0KzE= Received: by 10.52.95.166 with SMTP id dl6mr2665887vdb.88.1314471633203; Sat, 27 Aug 2011 12:00:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.169.100 with HTTP; Sat, 27 Aug 2011 12:00:03 -0700 (PDT) In-Reply-To: References: <175270279.98941.1313793515391.JavaMail.root@erie.cs.uoguelph.ca> <1314468512.87152.YahooMailClassic@web113511.mail.gq1.yahoo.com> From: Eitan Adler Date: Sat, 27 Aug 2011 15:00:03 -0400 Message-ID: To: Garrett Cooper Content-Type: text/plain; charset=UTF-8 Cc: giffunip@tutopia.com, freebsd-arch@freebsd.org Subject: Re: How about finally replacing GNATS? (was Re: FreeBSD problems and preliminary ways to solve) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2011 19:29:42 -0000 [removing specific proposals here to make a general comment] I don't think anyone wants to keep GNATS. However most proposals of this type are "lets use bug tracking system X because it has features A, B, C." With every tool change comes a workflow change and we need to be able to deal with that. As a member of the bugbusting team one of the most useful features for me has been the ability to use shell scripts to change bug states. As a port maintainer one of the most useful features has been the ability to use send-pr from the command line _without registration_. As a comitter having my commits automatically posted to the PR was very convenient. I am obviously not the only user and what is important to me might be trivial to other people. If one wants to gain the support of the community, and to have a good proposal we need to work forwards: What are the requirements we are looking for in a bug tracking system? Only then could we look to see what software fulfills this. In order to achieve that goal I am working on two things: a) A wiki page which we could use to describe the features we want *in order of priority* and b) A Google form with a list of features and related issues to act as a survey. The former is quite empty at the moment. The latter will be announced (hopefully) shortly -- Eitan Adler