Summary of Docs Team meeting September 16, 2025

Attendance

@estelaris, @milana_cap, @ninianepress, @sagargurnani, @atachibana, @azharderaiya, @mosescursor, @aialvi, @sirlouen, @rollybueno

Housekeeping

• Where: #docs  channel on Slack
• When: Tuesday, September 16, 2025 at 04:00 PM GMT+2
• Meeting Facilitator: @milana_cap
• Note Taker: @estelaris

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

• Docs Team online contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.
  • Where: #docs channel on Slack
  • When: Tuesday, September 23, 2025 at 04:00 PM GMT+2
  • Facilitator: @ninianepress
• Docs Team discussion meeting
  • Where: #docs channel on Slack
  • When: Tuesday, September 30, 2025 at 04:00 PM GMT+2
  • Facilitator: @estelaris and @milana_cap

Open Floor

@milana_cap and @estelaris attended the #core meeting on September 10 and our conclusion is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team wasn’t aware of the tasks of the docs team during a release. For 6.9 release, @estelaris accepted a temporary Docs Liaison, to not interfere with release work and to have a proposal from the docs team on how we want to collaborate in future releases.

The Docs Liaison will attend the release team meetings in the #6.9 release leads channel, review the roadmap to create the 6.9-related user documentation and to support the team during the final release day. DevNotes will be the responsibility of core committers, the 6.9 GH project has been created to track both DevNotes and User documentation.

@estelaris will work with the 6.9 release team on final release day to create/update the release documentation. In order to mentor other documentarians on this workflow, during the next Contributor Day (September 23), docs will have a mentoring session on this topic and record videos to add to the handbook page Documentation process during a major version release day.

Other topic discussed was how #docs team gives props to contributors and we agreed to review our process on this topic.

As a summary, the team committed to discuss the following in the next discussion meeting on September 30:

• Gather all the release-related documentation (from core & docs handbooks) and review the sections that are pertinent to docs. Update what’s needed, change the vocabulary/tone and length. We know people don’t read and sometimes handbooks are written in a difficult English.
• Create a proposal of how docs wants to work in future releases (@estelaris to write a draft), including tasks and timing.
• Define which contributors tasks should be recognized (is there an automatization we can add to GH/WP?)  eg. when they submit an issue, submit drafts, publish a new article, etc.
• Decide what goes for noteworthy and what goes for “regular” release contributor.

Among other handbook workflows we need to review:

• Define team members vs team contributors
• Update the team page
• Documentation team profile badge
• Add props and ask for peer reviews on meeting notes

Gathering the list of updated files

Thank you to @sirlouen for showing us how to gather the updated files list during a release cycle.

Props to @milana_cap and @ninianepress for reviewing the notes