# Documentation Community Team Meeting (May 5, 2026)

## Roll call

(Name / `@GitHubUsername` *[/ Discord, if different]*)
- Name / `username`
- Ned Batchelder / `@nedbat`
- Petr Viktorin / `@encukou`
- Ryan / `@ryan-duve`
- Trey
- Joe
- Blaise / `@blaisep` / `@controlpl4n3`


## Discussion

- Does `pip` support `pylock.toml` now? Should we switch to it for pinned docs builds?
  - It's used now ([python/cpython#149058](https://github.com/python/cpython/pull/149058)),
    but in some cases (that is, on Windows, see
    [python/cpython#149175](https://github.com/python/cpython/pull/149175))
    we still use `requirements.txt`.

- The next priorities for documentation are improvements for multithreaded
  programming and the free-threaded build.

- [Ned] The [Thread Safety Guarantees page](https://docs.python.org/3/library/threadsafety.html):
  this is a different style that nearby pages. It's more conversational, and I
  think it should be split into smaller pages.
  - Ideally, the list type should have its methods documented concretely
    (in addition to just sequence methods). That's a requirement to be able
    to note thread safety of each list method inline in docs
    (outside the thread safety page itself).
  - See also the free-threading Discord, which has a channel for
    documentation: https://discord.gg/WwmKQ6duJA

- Will there be a docs sprint at upcoming conferences?
  - PyCon US - maybe
  - EuroPython - yes

- How to help people feel more welcome in the [Python Docs Discord](https://discord.gg/862cyme4)?
    - Ryan volunteers to personally welcome new people in DMs for a month to get
      some information about what people need when they join.