Difference between revisions of "Tracker"
(→Introduction) |
(→2nd) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 7: | Line 7: | ||
=Mission Statement= | =Mission Statement= | ||
| − | '''To make sure | + | '''To make sure issues are kept in an orderly fashion, properly organized and adhere to the specific teams' specifications''' |
=Resources= | =Resources= | ||
| Line 49: | Line 49: | ||
===[[Explanation_of_Teams#2nd|2nd]]=== | ===[[Explanation_of_Teams#2nd|2nd]]=== | ||
| − | |||
===[[Explanation of Teams#Tamarin|Tamarin]]=== | ===[[Explanation of Teams#Tamarin|Tamarin]]=== | ||
Latest revision as of 16:59, 24 November 2010
Introduction
Tracker Monkeys deal with the lifecycle of the project bugs, feature requests etc. Each team and sub-team should have a Tracker Monkey working closely with the Silverback, the TMs also look after the boards and forums and most importantly the hundreds of Issues that make up the project's list of things to do.
Mission Statement
To make sure issues are kept in an orderly fashion, properly organized and adhere to the specific teams' specifications
Resources
- For TMs that are a Team Liaison
- For entering a New FREQ Example
- The PCGen_Jira_Guide for our new JIRA Tracking System (Beta)
- For dealing with Yahoo Group File Management
Old Resources
For the old Sourceforge Tracking System
- Tracker Priorities and what they mean
- Tracker Input Requirements
Active Team Members
Silverback
- Andrew Maitland - (Team Liaison - Data)
2nd
Chimp
Gibbon
Tamarin
- Fluxxdog
- Tom Parker
Lemur
Inactive Team Members
2nd
Tamarin
- Kent Behrends (Team Liaison - OS)
Lemur
- Bart Rompelman
- Frank Kliewe
