Add meeting notes from the March 2023 meeting

[CAM-Gerlach]

Adds the meeting notes from the March 2023 meeting, with some minor textual cleanup to linkify, remove sections that weren't relevant, tweak formatting and fix a couple typos (in a separate commit for easy reviewability).

Also replaces Current agenda: TBD on the index page with a link to the current agenda on HackMd, and got the live agenda ready for the next meeting.

---

📚 Documentation preview 📚: https://docs-community--76.org.readthedocs.build/en/76/

[CAM-Gerlach]

Seems like arewemeetingyet is down, which is causing the check failure. Do we want to switch to another site, remove the links or just wait a bit? We'd probably want to do the same on the "live" doc.

[hugovk]

I reported it at djc/awmy#28

We can merge already and check back later. If it's still down by the next meeting, let's replace it.

[CAM-Gerlach]

Considering at least per the readme it's mentioned as still running on Python 2.7 (though it seems it might be Python 3 compatible), and there have been no changes for years, it seems like the answer may be no. We could actually host it ourselves since it's FOSS, but it looks rather archaic and its probably more realistic to just use another service.

[hugovk]

https://arewemeetingyet.com/UTC/2022-10-03/19:30/Docs%20Meeting is back up!

[CAM-Gerlach]

Unfortunately, I can't restart the CIs without closing and re-opening this issue, as it seems neither I nor even the core devs have Write access here.

FWIW, the permissions here have always seemed a little restrictive to me relative to other much more critical repos (like cpython, peps, devguide, core-workflow, etc.) that even triagers have the GitHub write role (minus actual push/commit/merge) to. We might want to consider giving the docs team write access, and/or implementing python/core-workflow#460 here so we can all use the full GitHub feature set without needing merge rights.

[encukou]

Thanks!