Message-ID: <4C6D3D07.1010208@blunn.org>
Date: Thu, 19 Aug 2010 15:17:43 +0100
From: William Blunn <bill+cygwin AT blunn DOT org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bug tracker
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> <8cdq66dd6mang9d5oseab1v7l20io5epmi AT 4ax DOT com>
In-Reply-To: <8cdq66dd6mang9d5oseab1v7l20io5epmi@4ax.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 19/08/2010 14:57, Andrew Schulman wrote:
> 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.
>    

Sounds like a top idea.

I suppose the top-level management workload is more about creating / 
maintaining the sub-projects for packages so as to associate them with 
the correct maintainers for each package.

You might also want to make it clear at the "new bug" page that the 
tracker was only used for packages where the maintainer had elected to 
use the bug tracker, and that if there was no sub-project listed for a 
particular package then bugs for that package were not tracked in the 
tracker and the proper place to go would be the mailing list.

Bill

--
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