RE: [PHP] Open Source BTS??

> -----Original Message----- > From: M. Sokolewicz [mailto:tularis@php.net] > Sent: Friday, November 16, 2007 3:45 AM > To: richardh@phpguru.org > Cc: Randy Patterson; php-general@lists.php.net > Subject: Re: [PHP] Open Source BTS?? > > Richard Heyes wrote: > >> I am needing to install a bug tracking system on a web server and > >> looking for a good PHP open source solution. Looking for a pretty > >> mature system that still has active development. Thanks for any > >> suggestions. > > > > The only one I have had experience of is Mantis: > > > > http://www.mantisbt.org/ > > > > No complaints here. > > > > I'm personally a big fan of both bugzilla (www.bugzilla.org) and Trac > (trac.edgewall.org), both not php (perl, and python I > believe), but they > are both really really good imo. > > - Tul I user Trac for my Wiki my personal SVN repos. Here's an email I posted this list a couple weeks ago about the topic: -----Original Message----- From: Daevid Vincent [mailto:daevid@daevid.com] Sent: Thursday, November 08, 2007 6:57 PM To: php-general@lists.php.net Cc: 'TG'; 'Skip Evans' Subject: RE: [PHP] Recommend a wiki? I have had 'Trac' thrust upon me by an employee/coworker and while it is not "perfect" (or even close to it), it does what it does, and it does it pretty well. http://trac.edgewall.org/ Some of my favorite things about it are: Wiki is pretty common tags (http://trac.edgewall.org/wiki/WikiFormatting) Subversion integration with diff, view source, and svn commit hooks ("fixes, references, etc") You can integrate SQL 'reports' and the Wiki together. This rocks! Ticket tracking Roadmap graphs Plugins Can have different 'Tracs' setups on same server (I run two - biz and personal) On the negative side: It is a little tricky to install IMHO. It uses SQLlite (this is a pro and a con at the same time) doesn't seem to be updated with any frequency or regularity it's not even a 1.0 -- but that's all the rage with the kids it seems v0.11 is due "any day now" all written in python (yuk) Tickets are sort of cumbersome and they store the TEXTUAL names rather than relations. *sigh* (for example, if you change an employee, you have to search and replace the NAME, not just a 'user' relational link) .WTF.