Documentation Community Team Meeting (August 6, 2024)

Roll call

(Name / @GitHubUsername [/ Discord, if different])

  • Hugo van Kemenade / @hugovk

  • Ezio Melotti / @ezio-melotti

  • Trey / @treyhunner

  • Manuel / @humitos

  • Ned Batchelder / @nedbat

  • Petr Viktorin / @encukou

  • Usman

  • Carol / @willingc

  • Daniele / @EvilDMP

Reports and celebrations

  • [Manuel] Moving the docs to Read the Docs

    • Several reasons: be more open (let everyone see if the builds failed, how the builds work); faster builds;

    • A test is already working for pull requests. Only PRs that touch documentation are built.

    • Test: https://cpython-previews.readthedocs.io/en/main/

    • python/docs-community#5

    • In the last 1-2 months, we’ve been working on the language and version selector. In the current process this is added at build time from a JSON file, RTD does that at serve time with Javascript so even old versions of the docs link to current versions.

    • We’ve been working to not losing what we already have but also not get rid of RTD features.

    • 3.13 or 3.14 is the version we’ll migrate first, to get a feel for the workflow. All other versions will be served by python.org for now. Then we’ll migrate one version at a time.

    • [Trey] Will this enhance the search? [Manuel] There have been many improvements in RTD search lately. Traditionally RTD overwrites Sphinx search entirely with server-side (Elastic Search) search. Now there’s a way to choose RTD or Sphinx search from the docs theme. There’s also a person who said they’re working on the Sphinx search engine.

    • [Trey] So there won’t be a change on day one.

    • [Carol] For the PR previews, is there an option to link to the most changed file in the PR? [Manuel] We’re working on it, don’t know the details. The idea is to perform a diff and determine what changed, and link to it directly.

    • [Carol] That’s way further ahead than I thought. Thank you!

Discussion

[Ezio] Deprecations in the What’s New file - replacing the list of deprecations with a table

[Ezio] Defining and documenting a procedure to ensure that we follow up on additional tasks brought up in review

  • python/devguide#1359

  • [Hugo] If someone says “let’s do this”, they should be in charge of who’s going to do it

  • [Ezio] There’s a “diffusion of responsibility”, we should define who should go and open the issue to follow up. The proposal is that the PR author should be in charge – either volunteer to follow up or find other actors to do it.

  • [Carol] One thing we’ve done on other projects is that the person who proposes additional work should open that issue; then it’s fair game for anyone to pick it up.

  • [Ezio] One reason I mentioned the author of the PR is that someone could come and see an issue, but they don’t have the context that the PR author has.

#118891 Slow actions for doc builds

PEP Workflow

Follow-ups from previous meeting(s)

Monthly reports archive