X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0	tests=AWL,BAYES_00,SARE_RMML_Stock10,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 11:18:48 -0400
Lines: 30
Message-ID: <pphq66ptach2iki3bhqb9rp4s46f7g5si6@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> <cmfq66p4d2s88u1foj5s7d13ucg2oda29i AT 4ax DOT com> <20100819144931 DOT GD19001 AT calimero DOT vinschen DOT de>
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

> http://cygwin.com/acronyms/#SHTDI ?

Auto-updating the package categories daily doesn't seem hard to me, I would
build that if we had a bug tracker working.

But before we get to that point, I'd have a few other questions.

(1) Most important:  How many people care?  Do users want a bug tracker?
Would package maintainers use it?  Would the cygwin and setup.exe
maintainers use it?

Andrew Schulman and Bill Blunn would find a bug tracker useful, but that's
not enough reason to build one.  There has to be significant community
buy-in, or it's not worth doing.

(2) What's the best bug tracker for Cygwin?  I know Trac, and I would help
to set it up.  Maybe that's all we need to know, but I'd like to hear from
people who have experience with other bug trackers and could suggest which
is likely to work best for us.

Trac's big selling point is its integration of wiki, bug tracker, and
version control repository views.  Only the bug tracker seems to be
immediately of interest for Cygwin.  We could disable the other components
and just use the bug tracker, but it's not necessarily the strongest
stand-alone bug tracker.

(3) Would sourceware.org/cygwin.com be able to offer any server support,
i.e. file space, PHP, and a database?

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