-
trac tags
last modified November 29, 2007 by nickyg
Use these trac keywords consistently and it'll be easier for us to sort tickets. If you find yourself using a new keyword, add it here, so others can use it too.
Broad themes:
- "ui" -- anything that needs to be looked over / thought through by UI folks before programming happens. These tickets should also be assigned to Mouna, Rollie, or Nick.
- "copywriting" -- anything wording-related. also assign these to Bryan."
- "bugday" -- anything that's tagged for bugday, obviously
- "javascript" -- speaks for itself
- "userfacing" -- bugs / features that directly face users
- "cleanup" -- maintenance-type stuff that will make our lives easier
- "documentation" --use it for all help related stuff right?
- "performance" -- make things faster.
Features / issues:
- "undo" -- stuff related to undo functionality (as opposed to "confirm")
- "team" -- anything related to team membership or management. We will review these tickets together, and then fix them as a group.
- "listed" -- anything related to public/private project memberships. Mouna will review these all together.
- "permissions" -- stuff related to what visitors can & can't do -- roles & permissions.
- "featurelets" -- tickets relating to how featurelets are integrated into the site (installing, configuring, removing, etc.) | MAYBE WE DON"T NEED THIS
- "usermessages" -- anything related to sending messages to the user: PSMs, site errors, etc.
- "i18n"
