This repository was archived by the owner on Nov 3, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Labeling System
enesozi edited this page Feb 16, 2016
·
3 revisions
Labels are a great way to organize different types of issues. Therefore , customizing them according to our needs is essential.
Our labels are as follow:
- bug: is for indicating bugs detected in the project.
- documentation: is for indicating the changes made in wiki.
- duplicate: is for indicating potential dublication of an issue.
- enhancement: is for indicating any improvements made in any part of the project.
- help-wanted: is for indicating that there is a need for an issue.
- invalid: is for indicating that the issue is no more valid.
- question: is for indicating any question directed to the project.
- requirement: is for indicating any necessities that will emerge during development process.
- test: is for indicating tests tried on enhancements.
- wontfix: is for indicating that the issue won't be fixed.
- Project Description
- Project Video
- Themes/Features
- User Stories & Acceptance Criteria
- Personas
- Domain Analysis
- Requirements
- Initial Plan
- Diagrams
- Use Cases
- Peer Reviews
- Mockups
- Test Plan
- User Tests
- Test Web Project
- Meeting 1 - 16.02.2016
- Meeting 2 - 18.02.2016
- Meeting 3 - 3.3.2016
- Meeting 4 - 7.3.2016
- Meeting 5 - 11.3.2016
- Customer Meeting 1 - 28.03.2016
- Meeting 6 - 8.4.2016
- Customer Meeting 1 - 29.9.2016
- Customer Meeting 2 - 06.10.2016
- Meeting 7 - 06.10.2016
- Meeting 8 - 13.10.2016
- Customer Meeting 3 - 27.10.2016
- Meeting 9 - 27.10.2016
- Customer Meeting 4 - 03.11.2016
- Meeting 10 - 03.11.2016
- Meeting 11 - 10.11.2016
- Meeting 12 - 01.12.2016
- Meeting 13 - 08.12.2016
- Customer Meeting 5 - 08.12.2016
- Meeting 14 - 08.12.2016