Document OpenGitOps teams

[scottrigby]

Hello everyone 👋 After chatting with @staceypotter more (and after this has come up in many previous meetings), I decided to take a stab at this. Please let me know what you think, make any suggestions, and let's get something in so new people don't have to ask this question to find out about how to be involved in OpenGitOps teams.

Preview: https://github.com/scottrigby/ogo-project/blob/document-teams/TEAMS.md

What this PR does

• Adds a file to document OpenGitOps teams
• Clarifies processes around adding new members to a team
• Disables markdown lint rule MD033 - Inline HTML, to better visually list members

Problem

People consistently ask for info on how to contribute to the GitOps WG, how to join the teams (subgroups), and who is currently involved in each team. We have some transparency for all of this:

• Teams are listed in the template for the twice-monthly recorded WG meeting, which generally starts with a report from each of the active groups. But not everyone can join these meetings, and it's not clear at a glance looking at the project Git repo what and why these exist, or any of the above informatino
• We use GitHub teams to help with any permissions we may need for each team, and also so that volunteers can officially list their membership on their GitHub profile. However, there is no discovery for this, because the way GitHub teams work is only existing org members can see the list of other team members

Proposed solution

Add an accessible, easy-to-read markdown file in the project root explaining all of the relevant info about OpenGitOps teams.

To-do

• Add missing info to this file. For example, the volunteers for each language translation
• Consider splitting the table of teams into sections for proposed, active, paused and inactive
• Get feedback via this PR. Does this feel clear to people what the existing teams are, how to volunteer officially, how to propose new teams, and the processes around adding new members and teams?

Follow-up

• Follow-up: update GOVERNANCE.md to reflect and link here for information about teams instead of "committees"
• Follow-up: consider adding a directory/README per team. These could define each team's scope/purpose, clearly link to any relevant meeting info, and list the members there instead of all in one big document like this. This would also open the possibility of allowing direct team access to their file(s) via a GitHub CODEOWNERS file

[niklasmtj]

Looks great! Thank you!

[staceypotter]

This looks great @scottrigby! Thanks so much for putting it together, and sorry for my extremely late review! <3

[roberthstrand]

👏