On Sun, Dec 21, 2008 at 8:33 PM, Robert Castley <[email protected]> wrote: > Hi, > > Just curious here. I/we currently use Bugzilla & CVS, no formal wiki but I > do have a MediaWiki used for somethings. > > I am looking for a solution that fits all, so the obvious choices are 'Trac' > like. > > My problem is that I need a solution that will support multiple projects. > (Trac doesn't score well in this area.) > > Bugzilla is used by multiple PHP, Java & C/C++ products. CVS is used only > by PHP developers the 'others' use VSS. > MediaWiki is used for 'sparse' documentation. > > > My gripes with the current setup: > > Bugzilla - v. slow and ugly but it fitted the bill at the time. > CVS - I like, no love, CVS but I know that there are better solutions out > there but am concerned about migration etc. > MediaWiki - Probably too much of an overkill for what we need and it is not > that easy to configured, extend etc. > > I now that the ZF team uses JIRA, Confluence etc but I have a budget of > £0/$0 :-) and don't qualify for the OS licenses. > > So ... I would be interested on the views of others of a 'one hat fits all' > solution that can handle multiple projects. > The solution needs to offer Issues/Bug tracking and Wiki at a minimum. > Integration with SCM not important but > if it does it great. > > I would prefer a PHP based solution but happy to consider others i.e. Ruby, > Perl, Java etc. > > - Robert
We are all hosted/outsourced in this regard. For the SCM we use subversion (through a plan by cvsdude) on all projects. And then lighthouseapp[1] or Fogbugz[2] (primarily). This is just to track issues etc. and see the overall progress. I'm also using a slimed down trac as a svn browser (since it's included in the plan). Using a post-commit script, we can post to either Fogbugz or lighthouseapp to integrate ticket status, progress and what not. Fogbugz IMHO -- aside from the hefty price tag -- is like a dream come true. All my non-technical users understand it and feed it. It's just very convenient, e.g. you can feed in tickets via email and web interface. You can also answer on a ticket via email and so on. You can organize it all with priorities and into releases (aka milestones) and it works. Not saying that no other system does that, but the flow is more natural than in trac or Bugzilla. We also handle *all* issues in it -- as a rule of thumb, if it's not in the system it's not being done. All documentation is phpdoc and the details are kept in wiki on Google Sites. (We use Google Apps for your domain, etc..) If money is an issue, I'd stick with trac only. Issue tracking, milestones, wiki, etc.. There are also a ton of plugins which can add to the feature set, but I'm not in the know with those. You can customize the hell out of trac, that I know, but I'm not an expert. If I needed to recommend a wiki, I'd say dokuwiki. I use it with a couple clients who are not too well equipped on the tech side. They just needed basic knowledge management and it works perfectly. Till [1]: http://lighthouseapp.com [2]: http://fogbugz.com
