Define long term goals and roadmap and maintainer roles #731
Description
📚 Documentation Issue
Larger corporations (like @SecuraBV) are often interested in getting insights into a project's roadmap and team structure. Specific details that should clearly be defined such that they can be incorporated into the dependent party's strategy:
Goals:
- Short term goals are detailed in GitHub Issue milestones (already implemented).
- Longer term goals should be outlined in a maintained roadmap readme in this repository.
Features:
- What features are considered core?
- In what degree will scanners/hooks keep being added to this project?
Team:
- Who are core, long-term, team members?
- Who are temporary team members (e.g. interns/thesis projects)?
- Who are external contributors?
- What is this team's workflow? Already in blog-post format, not directly linked in main repo.
Iteratec:
- What is iteratec's role in secureCodBox?
- Who is financially sponsoring secureCodeBox?
- Is secureCodeBox development sold by iteratec?
- In other words, what ensures that iteratec continues development on this project?