This project is requirements driven, here are some hints how to process them.
Like all OpenSource projects we're listening to our current and future users, so anyone can suggest a requirement or just a feature wish using this project, then entries are accepted or rejected and planned, flow will be detailed but it's good to keep history of such activities.
Here is a WIP flow
0/ Req is filled
Just file issues in project:
Then make it as "Draft": and assign to @rzr: he will proceed the "wish list":
1/ Requirement is labeled (reviewed)
Drafted features are detailed (by @rzr or reassigned) and then re-assigned to @seba for removing draft state
TODO:@seba please update following part or remove if obsolete
Current domains are enlisted under this link .
Once got reviewed and accepted, they will become a part of this wiki. }
2/ Requirement is planned (WIP)
Some state will be applied:
Some priorities will be assigned
- https://git.ostc-eu.org/OSTC/planning/product/-/blob/master/domains/labels.md (labels and domains management)