 |
 |
Hi, Cynthia, we use Trac here, both for integrating code management and how it relates to issue tracking, but also for project management. We've recently rolled out multiple Trac instances to help other organizational groups (mainly higher-level committees) with project tracking and wiki space. The cool thing about that is Trac can support inter-trac links, so issue numbers and wiki links on one Trac instance can be linked to other Trac instances. It's a pretty versatile tool. I'm always impressed with its performance, even on modest hardware. As Mike noted, Trac is a Python/wsgi app. It doesn't do e-mail ticket submission out of the box, though that wasn't a requirement for us. As far as dislikes, my main pet peeve now, after recently upgrading to a newer version, is sorting out exactly how to preserve the same feature set our developers are used to. In other words, it's kind of a pain to upgrade. To your specific questions: > 1) minimal effort in install/setup i.e. ready to use out of the box Yes, Trac is packaged for RedHat (in the EPEL repository for RHEL users), and Debian-based distributions (Ubuntu et. al.) I've heard it runs well in Windows, can't vouch for that. > 2) small scale is okay, we have a very small team We started with Trac just because our small group of developers (all two of us at the time) needed a way to track issues and how they relate to code changes. Trac did everything we needed in that regard, and it did it all with a wiki flair. On top of all that, it was wicked fast on the same server that was dragging along with a big Perl-based app. > 3) ideally, have an area for documentation and issue creation via email Trac has a wiki for this. There is a plugin for issue creation via e-mail, but I haven't tried it. -- HARDY POTTINGER <[log in to unmask]> University of Missouri Library Systems http://lso.umsystem.edu/~pottingerhj/ https://MOspace.umsystem.edu/ "And remember, also" added the Princesss of Sweet Rhyme, "that many places you would like to see are just off the Map and many things you want to know are just out of sight or a little beyond your reach. But someday you'll reach them after all, for what you learn today, for no reason at all, will help you discover all the wonderful secrets of tomorrow." --Norton Juster, The Phantom Tollbooth On 2/22/12 11:53 AM, "Michael J. Giarlo" <[log in to unmask]> wrote: >On Wed, Feb 22, 2012 at 12:36, Cynthia Ng <[log in to unmask]> wrote: >> >> What's key: >> 1) minimal effort in install/setup i.e. ready to use out of the box >> 2) small scale is okay, we have a very small team >> 3) ideally, have an area for documentation and issue creation via email >> >> What does your institution use? >> What do you like and dislike most about it? >> Would you recommend it to others? > >We have been using Redmine for the past year or so. We use it for >issues and for code repo integration and for tying issues to commits. >We don't much use the wiki/doc functionality and we do not create >issues via email, though I do believe it supports both of those >features out of the box. > >We're very happy with it and would recommend it. It runs on Ruby on >Rails, so make sure you can support that in your environment, needless >to say. > >I've also used Trac in the past, which I also liked very much but I've >found Redmine to be a little less fiddly though I recognize that is >highly subjective. If it's easier to support Python/wsgi apps in your >environment, Trac might be a better choice than than Redmine assuming >its feature set matches your needs. > >-Mike