X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 19 Aug 2010 16:19:48 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug tracker
Message-ID:	<20100819141948.GB19001@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT 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> <8cdq66dd6mang9d5oseab1v7l20io5epmi AT 4ax DOT com>
MIME-Version:	1.0
In-Reply-To:	<8cdq66dd6mang9d5oseab1v7l20io5epmi@4ax.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Aug 19 09:57, Andrew Schulman wrote:
> > 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.

The question is if the maintainers really want that, and cgf and I are
just 2 out of ~60 maintainers, maintaining over 1400 packages.  From
these ~60 maintainers we have quite a few who either don't reply to any
mail about their package, or who only reply after some nudging.

Somebody would have to set up the system and the maintainers must be
willing to get automatic mails about issues entered into the bugtracker.

How to set that up is YA question.  One category per package?  That
doesn't sounds feasible, unless we have another, *active* maintainer
just for keeping the bugtracker in shape.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -