| Version 19 (modified by , 17 years ago) ( diff ) |
|---|
Note: This page doesn't belong to the "official" Trac documentation and consists entirely of user contributed comments.
What is Trac?
Exactly what is Trac? What does it do? Do I need Trac? Why is Trac the best /insert class here/ in the field?
Trac Main Features
What is Trac great at?
Ticket system
Online Repository Viewing
Trac improves greatly upon the online code viewing option provided by Subversion with its beautiful code highlighting provided by Pygment. This makes finding changes very easy.
Trac also shows the most recently updated files and dates for all files to easily find what you're looking for.
Wiki
With MoinMoin Syntax and magic links to tickets, reports and source.
Fully integrated web interface for Subversion
Features provided through plugins
Future features
0.11
Discussion
Things I don't know Trac has or hasn't:
Categories Calendar
Rationale
… and why not discuss all of this on the MailingList? ;)
. . . I was trying to create a page that answers the first FAQ: Where is the features summary.
- This page would be a great help for people needing to pick an issue tracking system out of the myriad available.
- Well, I read this, and it did not help me with my question at all: "Could Trac be useful for me and my Projects?"
- so true, this page eventually needs a total conversion ;-)
- Is there a "resource planning" possibility? Something that Gantt charts would provide, maybe?
Comparisons
To make this page particularly valuable, consider which features Trac sports/lacks in contrast to other popular systems, such as BugZilla, JIRA, Confluence, MediaWiki, FogBugz.
- Wikipedia hosts a comparison of issue (& bug) tracking systems …although Trac's entry is a bit out of date.
If this page covers both its relative strengths and weaknesses, this would be a great page — letting potential users know exactly what they'll get, how much work they'll need to do to get it running, and what competing packages can offer!
