Better overview of teams

[cornelius]

We have quite some teams now and it's not always straightforward to get a good overview and understanding what the teams are there for. Here are some thoughts about how we could improve that.

Replace general.yaml by more specific files

https://github.com/OpenRailAssociation/openrail-org-config/tree/main/teams

• Would it make sense to split up the general.yaml file into an openrail-team.yaml and and event-organizer.yaml? Then all teams would be represented by one file. Could make the config a little bit easier to understand.
• Would it make sense to use a prefix to indicate different types of teams, so project- for the project teams, wg- for the working groups, and maybe org- for the OpenRail Team and the Technical Committee and external- for the Hack4Rail team?

Consistent naming and descriptions for all teams

The overview https://github.com/orgs/OpenRailAssociation/teams shows all teams, but the descriptions are not consistent and for some teams it's not completely clear what they are meant for:

• Some descriptions say "people", "members", "the members", "the team behind". Some subteams have no description. Maybe we should make the role of team clear in the description ("Maintainers", "Contributors", "Participants", "WG members")? At least use a consistent scheme.
• Capitalization of team names is not consistent (liblrs-admins vs. NGE-Admins).
• We have some Admin teams and some Maintainer teams. What's the difference? Are they used in a consistent way? Should we always have maintainers and admins? Or should maintainers always be admins?

[mxmehl]

Regarding the files, unifying them makes sense. This will not break anything if you also consider the CODEOWNERS file.

Regarding the teams themselves:

• Changing description makes sense of course and does not break anything
• Changing capitalization as well
• Changing e.g. "Team Maintainers" to "Team Admins" will not rename the team but delete the one team and create the other. In fact, nothing will change but it may lead to some noise and required changes of subsequent CODEOWNERS files (e.g. in the OSRD repos).

The logic of maintainer/admin teams is mostly to give some people elevanted permissions, e.g. to make edits in this very repository, the repo settings or team memberships directly. Not sure why the naming is different but it should actually not make a difference.