Functionalities

• List of Functionalities
• Functionality template
• Each one has an explicit unique identifier, like F50000 for the origin functionality "Artist is freed"
• Each one has a **single page**, built using the Functionality template, with the identifier as title
• They are hierarchics: F50000 has multiple children, like F10001, wich has also children, etc...
• Keep the functionality's page up to date when working on it
• When writing some code, always comment with the functionality identifier
• /!\ Functionality have states (Unactive - Planned - In progress - Finished) and when it changes, you have to update:
  • the functionality's page
  • the parent(s) functionality(ies)
  • the functionalities' list
• The priorities do not depend of the parents or children priorities
  • optional: to be performed later if possible
  • low: planned but not important to have seizam running
  • medium: seizam can work without but we miss it if not present
  • high: important for Seizam, it adds value
  • critical: Seizam doesn't run without