X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0	tests=AWL,BAYES_20,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject: Re: Bug tracker
Date: Thu, 19 Aug 2010 09:57:26 -0400
Lines: 34
Message-ID: <8cdq66dd6mang9d5oseab1v7l20io5epmi@4ax.com>
References: <4C6C1B01 DOT 4020808 AT blunn DOT org> <20100818182641 DOT GB22698 AT ednor DOT casa DOT cgf DOT cx> <4C6C4372 DOT 2070701 AT blunn DOT org> <20100818205009 DOT GK11340 AT calimero DOT vinschen DOT de> <4C6D17E0 DOT 5010506 AT blunn DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive: encrypt
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> It might be helpful if I could be clear what the reasons for not having 
> a bug tracker are.
> 
> I could take a stab as:
> 
> 1. It is not the feeling of the Cygwin maintainers that a bug tracker 
> would provide a significantly better solution than the current mailing 
> list solution
> 
> 2. There is not any human resource around to do the top-level 
> maintenance of such a system

I think that a bug tracker would be a nice improvement to our development
workflow.  As a package maintainer, I'd love to be able to call up a page
of all of the open bugs for all of the packages I maintain.

I also think that the work to set up and maintain a bug tracker isn't very
much at all.  I've set up three Trac installations myself, for different
projects.  It's no big deal, and if Trac were the tool of choice for
Cygwin, I would volunteer to set it up and maintain it.

I don't have any experience managing other bug trackers though, e.g.
Bugzilla, so I can't say about them and would be reluctant to volunteer to
help with them.

I don't know about server space, but surely that should be available
somewhere.

I'm guessing that it really comes down to what the project leaders want to
support.  Then again, if the community maintains a bug tracker, the project
leaders don't have to be involved at all, except that it would be a much
more valuable tool if they agreed to use it.

Andrew.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple