NCCOOS Trac Projects: Top | Web | Platforms | Processing | Viz | Sprints | Sandbox | (Wind)

Using Trac for NCCOOS Projects

This page describes how to use the Trac System for projects run by NCCOOS. It contains general how-to notes for getting started and day-to-day details of Trac focused on working in a team and/or maintaining a project as a team-leader. Add to this page as you find useful info and how-tos related to Trac and SVN.

Trac System

Trac is a minimalistic approach to web-based management of software projects. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress. By integrating web-based documentation tool (wiki) with bug tracking or enhancement features (tickets), and code repository, the Trac System allows distributed teams of people to collaborate remotely on a software and documentation project.

For Team Members


  • Change the status of a ticket from 'new' to 'accepted' when you start work on the ticket. It's fine to start work, drop it and come back to the ticket later.
  • Make use of TracLinks in the original description of the ticket to refer to other tickets and to wiki documentation.

Modifying Code

For the Project Leader(s)


  • For small projects, use a single Milestone to define the project. Breakdown the project into a collection of tickets that are in the 'Task' Category and assign them to the milestone. When a new tasks are added, be sure to mark them as part of this milestone.
  • Use a short paragraph describing the milestone's overall objective. Then create tickets for each item of the to-do list with Category set to Task for each.


  • For the larger project, use several milestones. Add a wiki item for the project and link the relevant milestones into the wiki text.
  • Use the Trac wiki for software development and collaborative documents. Use the for more general info.