Summary of Docs Team meeting September 9, 2025

Attendance

@estelaris, @milana_cap, @ninianepress, @sagargurnani, @jdy68

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Open floor

@estelaris shared these updates about the next release, which was discussed:

  1. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is experimenting with a smaller release team to avoid pitfalls. The experiment will be re-evaluated after this release.
  2. There seems to be no need to have docs team as a named lead in releases, I argued the importance that it has to us, mainly we want to mentor other contributors and releases are like an “extra” benefit for the team.
  3. Also, the release team needs to plan better so they can ask us for someone to update the HelpHub pages – known to us as the WP version pages

For releases, Mary recommended that we name a Docs Liaison person that will commit to update in documentation anything related to the releases (User documentation, WP version pages, etc.).

Docs will not be in charge of wrangling/writing any DevHub articles related to releases. Updating issues that are posted in the Docs Issue Tracker is still on the balance, as I found out that many core committers had no clue that issues were reported to us, so they don’t update anything util someone from docs reports the issue on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..

And the biggest issue that we need to decide is the updating of the WP version pages. The last 3 minor releases, I have done it. 1 time I was asked when the release was being planned and the other 2 times, at the last minute. So I mentioned that we need to plan better and find a way to work together and create a process that works for both teams.

The response from core is that we give access to all core committers so they can update the WordPress version pages, that is a list of 40 people. And I said I wasn’t comfortable in giving access to everyone, perhaps a few, my reasons the version pages are in the same site as the rest of the documentation and the docs team is in charge of maintaining the version pages also. Giving access to everyone, means we will be called less and less to help on releases or anything else.

Here is the chat to the main conversation.”

#docs, #meetings, #summary