Summary of Docs Team meeting July 1, 2025

Attendance

@dilip2615, @estelaris, @sagargurnani, @atachibana, @rollybueno, @mosescursor, @abdulwahab610, @nikunj8866, @zeelthakkar, @masteradhoc

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Project check

@rollybueno completed these issues during our Docs Team Contributor Day last week — now ready for review:

@atachibana reviewed 7 issues and updated the corresponding articles.

Open floor

@estelaris had the following update to share:

If you want to learn how the release parties work, help with testing, or you’re scheduled to be one of the upcoming minor (or major) release leads, please join us with the details below.

Please note: As a friendly reminder, @kenshino and @ninianepress will be trained by @estelaris to be the Docs Team leads for the next WordPress minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..

@rollybueno mentioned and agreed to the proposed solution @masteradhoc communicated before the meeting:

@estelaris and @atachibana approved of the suggestion, and @atachibana suggested that @masteradhoc open a GitHub issue for Gutenberg.

The corresponding issue #70584 was created by @masteradhoc immediately following the meeting.

#docs, #meetings, #summary

Summary of Docs Team meeting June 17, 2025

Attendance

@milana_cap, @estelaris, @ravigadhiyawp, @rollybueno, @dilip2615, @atachibana, @ninianepress, @hemant-ahir

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Project check

@estelaris had the following updates to share:

Summary of WCEU Contributor Day accomplishments:

  • Issues closed: 19
  • Articles updated: 8
  • Contributors: 12

Open floor

@estelaris was in a meeting last week with the Core AI Team and is working on a process for using AI for writing documentation. It will also be a blueprint for future AI integration into WordPress. Project updates will be provided as they become available.

@kenshino and @ninianepress will be trained by @estelaris to be the Docs Team leads for the next WordPress minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..

#docs, #meetings, #summary

Agenda for Discussion Meeting (17 June 2025)

The meeting is scheduled with the following details:

When: Tuesday, 17 June 2025, 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Project check.
  4. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

Summary for Discussion Meeting (06-May-2025)

Attendance

@estelaris @divyeshk71 @azharderaiya @ravigadhiyawp @karthickmurugan @nikunj8866 @Dhruvang21 @DilipModhavadiya @70_Sense

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Open floor

@estelaris explained the steps for contributing to documentation:

  • Find issues like outdated info, typos, broken links, or missing ALT text.
  • Report or pick issues from the GitHub Issue Tracker.
  • Share your updates in the comments or using a Google Doc in the GH issue.

Onboarding videos are available for more help.

#docs, #meetings, #summary

Summary for Discussion Meeting (29 April 2025)

Attendance

@milana_cap @nikunj8866 @azharderaiya @karthickmurugan @zluck @divyeshk71 @devmuhib @ravigadhiyawp @Sumit Singh @kafleg @Zeel Thakkar @Dhruvang21 @Parth @noruzzaman

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues.

@karthickmurugan also worked on 6.8 issues.

Open floor

Q: I want to know how to contribute in docs

A: Here we have a bunch of onboarding videos: https://make.wordpress.org/docs/2022/06/13/live-onboarding-sessions-for-the-documentation-team/. And here’s the “Get involved” chapter in our Handbook: https://make.wordpress.org/docs/handbook/get-involved/. Do take a look and if you still have any questions, do not hesitate to ask in #docs channel.

Agenda for Discussion Meeting (29 April 2025)

The meeting is scheduled with the following details:

When: Tuesday, 29 April 2025, 09:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Project check.
  4. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

Summary for Discussion Meeting (15-Apr-2025)

Attendance

@milana_cap @sagargurnani @utsav72640 @nikunj8866 @azharderaiya @flexseth @karthickmurugan @estelaris @n8finch (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues and she is also scheduling updates for articles which should be published soon. She also published an article – “What’s new for developers?“.

@atachibana is reviewing and working on issues associated to the older WP versions like 6.3.

@nikunj8866 contributed to the #1894 issue.

Open Floor

@estelaris is getting ready for 6.8 release. She also mentions that during a release, the docs team updates 2 pages in HelpHub.

  1. WP Versions
  2. And the version page itself, see 6.7 as an example

Then these 2 other pages are also updated. we need permission to access them because the updates are manually done then they have to be pushed via WordPress sandbox (WP.org‘s backend).

  1. Roadmap
  2. History

She would be adding the above process to the handbook soon.

@flexseth asked whether it is still the best practice to install the the repo locally, then create a PR for submitting changes to the developer.wordpress.org? What’s the best way to submit simple fixes and also contribute code samples?

To which @milana_cap replied that if he wants to contribute to the installation itself, that’s #meta and he needs to install it locally. But, if he wants to contribute code samples, he just needs to submit the user notes to reference and someone will review and publish it from #core

Agenda for Discussion Meeting (15-Apr-2025)

The meeting is scheduled with the following details:

WhenTuesday, 15-Apr-2025 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the next triage.
  4. Project check.
  5. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

[Announcement] New meeting times for the Documentation Team

Currently active Documentation team contributors voted on meeting times and we have a new set on trial:

Please note that these meeting times can and will be changed again if the team finds them unfit.

Meetings in April:

Meetings in May:

If you have any questions or concerns, do post them in the comments below.

#announcements, #meetings

Summary for Discussion Meeting (04-Mar-2025)

Attendance

@sumitsingh @Karthick @Troy @estelaris @milana_cap

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Project Checks

@karthickmurugan has completed several HelpHub issues related to WordPress 6.7, and they are now ready for review before further progress. Most of these issues are documented in the following triage issue: #1841.

#docs, #meetings, #summary