Meeting Minutes: Aug 11, 2026

Meeting Minutes from Python Docs Editorial Board: Aug 11, 2026

Attendees

Notes

  • Carol is taking a break from core Python responsibilities until the end of October, but can stay with us if needed.
  • Do we need to fill a slot at all? We are very informal and low-key.
  • We don’t get a lot of requests for docs, and there is not much going on.
  • The frustrating part is doing something different with the docs: sometimes there is no clear path forward.
  • Docs are still seen as less important.
  • Does the documentation vision belong to the PSF or the core team? Docs are not just the reference docs, but also user docs.
  • The point of this board is to be decisive and unblock docs decisions. Are there people who are blocked and don’t know they can get help from the Editorial Board?
    • Maybe things are fine and we are not needed. That could be a good sign, even if it makes us feel like we are not being useful.
  • In the Docs WG, people chat about docs, but no decisions are needed there. The discussion is more about logistics and the pipeline, not about docs content.
  • Potential engagement idea: add a docs community/triaging session.
  • It is easy to say what should be done about the docs, but hard to actually implement big changes.
  • Do we have metrics about how the Python docs are used?
  • What’s New: we could take the What’s New document and break it up by what’s important to a maintainer, a web developer, and so on. It might be worth having a visual landing page.
    • Sometimes we just need to know what is going to break (what’s deprecated). As maintainers and consumers, we usually care most about what’s going to break, but deprecations are usually at the bottom and new features at the top.

Action items

  • Start joining the Docs WG meetings.
  • Ask Hugo about adding a triaging session to the Docs WG meeting.
  • Finish PR #41.
    • Accessibility of the docs.
    • Might need funding from the PSF.
    • Who will be the project lead?