Added Governance Page to list the maintainers and dev meetings of various OCaml projects

[tmattio]

The page lists the teams that compose the ecosystem (Compiler, Packaging, Infrastructure, Platform) and working groups (e.g. Multicore)

This is very WIP, the list of maintainers has been scraped from GitHub teams on the OCaml organisation. I'm opening the PR early to get some early feedback and facilitate communication to get an accurate list of teams and maintainers.

Governance Page	Team	Working Group

[sabine]

I like this. It makes it so much clearer who is a maintainer.

There's a problem with the Email links, they go to 404 pages on ocaml.org.

Would be good to merge after the placeholder texts have been pruned and the lists of maintainers have been completed. Even without the working groups section, if that requires more work. Incremental progress is good.

[kayceesrk]

This is great. Thanks @tmattio.

[tmattio]

@sabine do you think you'd have time to take over the UI part of this? I can work with the different teams and working groups to get correct data on the maintainers, communication channels, etc.

From a UI perspective, we can aim to get a minimal version in. The most important information to display for each team and subteam, I think, is:

• The list of maintainers
• The communication channels (mailing lists, GitHub, slack channels, discord, etc.)
• The dev meetings if they are open
• The dev meetings notes
• The main repositories they are responsible for

[sabine]

Yes. Bring sufficiently complete enough data here and I will fix this up and get it live.

[avsm]

This looks great. Might we be able to use the GitHub API to map the various team ids from the groups there? The links to email lists on lists.ocaml.org will not currently work either.

[tmattio]

This looks great. Might we be able to use the GitHub API to map the various team ids from the groups there?

That was our idea too, yes! For this, we'd need a few things:

• Move some of the Platform repositories in the Active stage to the OCaml GH organisation (following the Platform governance). In particular ppxlib, ocamlformat, opam-publish and utop
• Create missing teams for the dev teams that don't have one (e.g. opam-dev)
• Move the project permissions to be managed at the GH team level and not at the repository level

Since the GH teams haven't been used uniformly and some of them might be outdated, we were thinking of first agreeing on what the current state of the world is with the different project maintainers, and then open an issue on ocaml/infrastructure to request the migration of the projects and updates on the teams.

Happy to proceed differently if you see a better way to do it though.

[avsm]

Harmonising the GitHub permissions and ensuring this list stays in sync with reality that way sounds good to me. Note that there are several sub-organisatiosn involved as well -- ocaml-opam, ocaml-ppx, and ocaml-dune. I have admin on all of those to setup tokens as needed for the API scraping.

[christinerose]

Minor capitalisation/formatting suggestions & a few grammatical corrections. Some of the. Names would normally be in monospace, so I suggested as much; however, if monospace isn’t possible in its final view, then format them as if they were in monospace. If there was a way to visually differentiate them, like bold or italics, then it would be beneficial (but not necessary)

[tmattio]

The need for that page presented itself again recently.

As mentioned in the review, it would be better to fetch this information from the GitHub API, but until we have up-to-date teams on the different GitHub organisations that we can use to populate the data, I think the page provides enough value that we can keep it updated manually. Therefore, I'll go ahead and merge it now.

While I've tried to get feedback from the maintainers and I believe the list of maintainers represents the current state of the world, it's possible that there are accuracies. If you notice such inaccuracies, first, apologies in advance, and second, please don't hesitate to reach out to or send a pull request!

As a next step for this page:

• We should try to automate it by using GitHub API (see Use GitHub teams to manage project permissions infrastructure#55)
• Now that the page is there, we can start adding the existing working groups. For instance, OCaml Wasm, Windows, or any other currently running working group.
• Let's make the information complete and accurate if it's not already the case. If you notice missing maintainers, missing dev meetings, or anything that needs updating, a PR is welcome.