Issue Labels

Labels of the issues on github

In this site the different labels used to identify the issues in github should be described.

Project state

• 1 - Ready
• 2 - Working
• 3 - Done

These define the progress of the issue during development.

Component

• Backend: The backend in PHP is affected
• Frontend: The frontend (HTML/JS) is affected
• Design: Decisions on the software design (Or do we mean visual design?)
• Setup: Problems during the setup routine
• Upstream: Problems which originate in libraries included
• Usability: Issues related with the user experience (What is the difference to Frontend?)

Which component is affected by the issue?

Priority

• Must Have
• Medium Priority
• Low Priority
• Nice to have

This defines the severity of the issue

Issue Type

• Bug
• Feature Request

Misc

• dependencies: automatically generated upon version changes in the dependencies
• Feedback Needed: some information are missing and these need to be delivered before any further help can be provided
• Need to reproduce: the issue is not reproducible, a clear test case is needed.
• Needs Main-dev Attention: some major question which requires senior knowledge.
• Will be closed soon

Unknown

The following tags/labels are not clearly defined and should either be defined or removed.@

• Build System

To be added

• meta: Used for issues not related to the code itself but the repo, the wiki, the programming standards and the like
• help-requested: Used to indicate that an issue is seeking for help during setup, usage, etc. This might be better pushed to a forum than kept as an issue here on github.
• good-first-issue: Used to indicate potential low hanging fruit
• move-to-wiki: The issue is better located as a tip in the wiki than in the issues
• complex-triage: The triage process is not trivial and another review should be done
• security-issue: The issue is security relevant. This should also have a priority of Must Have