Current status:
The process for sub-teams/project teams creation is implied in https://github.com/conda/governance#voting-items. The whole process is not clearly (or explicitly) documented, making it hard to find and leading to inconsistent processes (and results) for team creation/dissolution/refresh (for example, the CoC team is the only team with a documented and visible charter).
Recommendations:
- The team creation process should be defined and documented accordingly, in a section of its own rather than implicitly in the voting mechanisms section of the governance doc.
- Sub-teams/teams charters should be stored/documented in a
.md file or similar (and could build on https://github.com/conda/governance/pull/147/files to add structured data as yaml frontmatter). There should be templates to streamline team-related processes.
- Existing charters and teams should be documented per the above bullet point.
- Processes to update an existing charter should be defined and documented.
We should provide a template for new teams creation
The CoC is the only team with the charter documented in the repository
“Repositories SHOULD belong to one project team” -> now Infra is owner across all repos + project team
References:
Current status:
The process for sub-teams/project teams creation is implied in https://github.com/conda/governance#voting-items. The whole process is not clearly (or explicitly) documented, making it hard to find and leading to inconsistent processes (and results) for team creation/dissolution/refresh (for example, the CoC team is the only team with a documented and visible charter).
Recommendations:
.mdfile or similar (and could build on https://github.com/conda/governance/pull/147/files to add structured data as yaml frontmatter). There should be templates to streamline team-related processes.References: