The SC governs by consensus, so we try not to make the final call on things. Even so, we have final say in a lot of things, and we take that very seriously, and very carefully. Even long before Guido stepped down and we got the SC, many decisions were made by consensus rather than the BDFL (Guido). We talk a lot amongst Core Developers and Python users to figure out the consensus. The 5 SC members have quite different points of view, fortunately.

When I say governance needs to be stable and reliable, I don't mean it should be set in its ways. I mean its core values should be something people can rely on. I don't think the SC (or the #PSF) have made these core values entirely clear, although the PSF CoC (https://www.python.org/psf/conduct/) is part of it. We all care about Python, about helping users learn and use Python, about supporting *all kinds* of users, without judgement or gatekeeping. I hope we can improve this!

The Python Software Foundation (#PSF) is the non-profit foundation behind Python. It holds copyrights and trademarks, governs the license, and serves as a fundraising vessel. It's existed since 2003, but it's really grown in the last ten years (as has Python). It employs ~8 staff members and a few contractors to support PyCon US every year, fiscal sponsorees, PyPI, and development of Python itself.

I've been on the PSF Board for 6-ish years, as Vice-Chair and Chair, and I was the interim General Manager for about 6 months (to support the staff while we were between Executive Directors). I can talk for hours how awesome the PSF is. The staff, the volunteers, PyCon US, funding local communities, diversity, outreach, so much more. I will just point to the 2021 Annual
Impact Report, which I think covers a lot of it: https://www.python.org/psf/annual-report/2021/

I'm also the Release Manager for Python 3.12 and 3.13. I can't explain why in a few toots, but if you think I overextended myself, yeah, well, probably. Even so, this work matters to me so I volunteered. Also, Google supports me in all this work. RM work is mostly about quality assurance. I want 3.12 and 3.13 to be as free from disruptions as possible, while delivering new features and performance enhancements, and performing necessary deprecations.