X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 19 Aug 2010 13:32:16 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bug tracker Message-ID: <20100819173216.GB9090@ednor.casa.cgf.cx> 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> <20100819141948 DOT GB19001 AT calimero DOT vinschen DOT de> <20100819144931 DOT GD19001 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Thu, Aug 19, 2010 at 11:18:48AM -0400, Andrew Schulman wrote: >> 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? No, sourceware.org is not going to set up a completely new bug tracking system just for one project. I'm several messages into this thread and I have yet to see anyone say "It's already there". There is already a cygwin category in sourceware's bugzilla database and we've already had the discussion about how it should be handled. We had the discussion and then nothing happened and apparently no one even remembers that it exists. My problem with making this available to the Cygwin community is that I think, by and large, it is comprised of a fairly naive and nontechnical group of people who will not provide adequate bug reports. So anyone maintaining bugzilla will be spending a fair amount of time closing bug reports or asking for obvious clarification. However, if someone wants to volunteer to maintain this and vows to do a good job policing the database then I'll give them administrative authority and change the wording on the web site. I assume we'd want to change some categories in bugzilla too. cgf -- 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