X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,TW_CG,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 10:41:20 -0400
Lines:	39
Message-ID:	<cmfq66p4d2s88u1foj5s7d13ucg2oda29i@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> <8cdq66dd6mang9d5oseab1v7l20io5epmi AT 4ax DOT com> <20100819141948 DOT GB19001 AT calimero DOT vinschen DOT de>
Mime-Version:	1.0
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

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

Agreed, but OTOH I'd guess that half of all of the bugs reported on this
list are for just two packages: cygwin and setup.exe.  If the maintainers
of those two packages think a bug tracker would be useful, we should make
one.  If they don't, it's probably not worth bothering.

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

I can see a few models for notifying maintainers:

(1) Individual maintainers must each agree to receive emails, or their
packages won't be in the bug tracker.

(2) The community decides that bug tracking is important enough that anyone
who signs up to maintain a package must also agree to receive email from
the bug tracker.  Then all packages are listed in the bug tracker.

(3) Bug notifications are sent to the cygwin list, or possibly to a
separate cygwin-bugs list, instead of/in addition to the maintainers.

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

The list of packages could be automatically fetched and turned into
categories, once a day.  If the package maintainer names & addresses could
also be automatically fetched, then they could be automatically propagated
into the bug tracker too and so much the better.

The UI would need some care.  We would NOT want a pull-down menu of 1400
categories to enter a new bug :(  An autocomplete widget for the package
names would probably work well.

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

- Raw text -