This repository has been archived by the owner on Aug 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
Label glossary
Brad Nunnally edited this page Jun 6, 2016
·
1 revision
A glossary of the labels used on the Vote.usa.gov to help you get a better understanding on what they mean and how we use them.
- Accessibility
- Content Design
- DevOps
- Documentation
- Engineering
- Front end
- User Experience
- Visual Design
- Micro Purchase
- Abandoned: Contributor no longer responsive in correspondence.
- Accepted: Reviewed and approved by core teammate, included on product roadmap.
- Backlog: A build up of work that’s been initially reviewed and correlating labels applied. It needs to be reviewed before moving to “Accepted”.
- Blocked: Not able to move forward with work due to conflict.
- Completed: Merged in and closed.
- Help wanted: Contributors open to claiming and tackling. Description and acceptance criteria have been written.
- Idea: New idea or request, team has yet to evaluate.
- In progress: Work that has been assigned and is currently being worked on.
- Need more info: There is not enough information in order to move forward. Information is requested from the submitter or team member is assigned to research.
- On Hold: Work is currently paused, or not able to move forward due to conflict.
- Review needed: Pull request review needed.
- Revisions needed: Requires corrections based on team feedback.
- Blocker: Needs immediate attention. Prevents the product from working if it were released in that state. (For example: build failing, tests not passing)
- Critical: A critical requirement without which it is unacceptable to stakeholders. Impacts the applications functionality. (For example: feature not working in all browsers, content not accessible to screen readers)
- Major: A necessary but deferrable requirement which makes the product less usable but still functional. Does not impact the application’s functionality. (For example: typos)
- Minor: A nice feature to have if there are resources, but the product functions well without it. Also known as "could be betters." (For example: feature requests, cosmetic enhancements)
- Bug: Error, failure, or flaw in the product.
- Enhancement: Modification of product to enhance performance or correct faults for items that already exist.
- Maintenance: Fixing product defects.
- Question: An inquiry asking for more information.