Stuff needed for the project to become an accessible FLOSS project
This issue should be used to collect stuff which we should do/implement in order to become an accessible FLOSS project. Out of this we can generate new meta issues here too - they then should be linked here.
- #2 (closed) a project website P1
- some transparent governance rules for this project P1
- videos of talks explaining the project or single components P2
- contributor guide P2
- administrator guide P3
- user guide ~P4
The priority tags in the list are used similar to how GitLab uses it - P1 meaning highest priority and P4 lowest. Priorities will likely change over time. E.g., administrator and user guide will become more important when we reach beta stage and set up production ready environments.
Use this issue to discuss what we need and what priority it has. Discussions about how single things from this list should be implemented should go into those issues. If there is no issue for a list item, go and create one.