- we don't want to let the core team grow infinitely because
- no clear responsibilities
- hard to make decisions with too many members
- by introducing subteams we can more easily add new members
- individual teams can pinged or requested for review; we'd like to have PRs merged by the responsible team where possible
- GitHub_team_name (Discord role name)
- GitHub_child_team_name (Discord role name)
-> A child team inherits all permissions of its parent and gets notified when the parent gets notified -> That allows us to give people the same permissions but at the same time we allow to mention the subteams -> and make the responsibilities visible -> On Discord, the child team is above the parent so the child team members get their own section (useful?)
- core ("Core Team")
- engine-devs ("Engine Team")
- assets-devs ("Assets Team")
- render-devs ("Render Team")
- net-devs ("Networking Team")
- tools-devs ("Tools Team")
- web-devs ("Web Team")
- .. (will be extended when needed)
- members inactive for 6 months both on GitHub and Discord will be removed
- when they return they get re-added
- we want to make the steps clearer that are necessary
- for somebody to review / approve a PR
- for somebody to merge the PR
- the exact details will be discussed in the following pull requests