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

Proposal – the Documentation team meetings time

Lately, it has been noticed that the majority of attendees of Documentation team meetings are from Europe and Asia. Currently, team meeting time is 2 PM UTC, while online Contributor Days are from 1 PM to 3 PM UTC. This is not the most convenient time for the Asian community, especially from the Far East.

During the last meeting, it was concluded that Tuesday, as the meeting day, fits everyone. For the timing, moving back up to 5 hours could improve everyone’s experience and overall attendance.

Therefore, we propose the following options (NOTE: we will not apply a new time to the next meeting):

  1. Tuesday, 9AM UTC
  2. Tuesday, 10AM UTC
  3. Tuesday, 11AM UTC
  4. Tuesday, 12PM UTC
  5. Tuesday, 1PM UTC
  6. the same as it was
  7. something completely different (please, explain in comments)

Please let us know which option is the best for you in the comments. Also, keep in mind that Contributor Days last for 3 hours. They start 1 hour before the usual meeting and end one hour later.

Voting will be open until the next meeting, 8th April, to make sure everyone has enough time to add their vote.

Next meeting timeTuesday, 8 April 2025, 2PM UTC
Next 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/ time

Summary for Discussion Meeting (01-Apr-2025)

Attendance

@milana_cap @sagargurnani @estelaris @karthickmurugan @kafleg @Dhruvang21 @nikunj8866 @snilesh @sirlouen @stephenaturner999 (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Project Checks

@milana_cap reviewed the issues completed by @karthickmurugan and she also has a list of duplicate issues to sort out.

@karthickmurugan had completed many issues which can be seen by here.

Open Floor

@milana_cap raised a concern that the majority of the team at the moment is from Asia. She believes 14:00 UTC is not the best time for the team to attend the meeting because it becomes very late for the team members living in APAC timezones. So, she would propose a poll for new meeting time that will include earlier hours on Tuesdays. The poll would be held today i.e. 02-Apr-2025 and would be initiated by herself.

@sagargurnani discussed how to attract more contributors to be the part of the #docs team and to work on the  #docs. To which @milana_cap said that it needs pushing and announcing it regularly on social media and every single WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. maybe we can work on docs per project, and treat every project as “job posting” create a call, share it everywhere record videos how we do stuff, so that people can be onboarded more easily maybe we need new onboarding stuff.

@estelaris mentioned Matt’s plan for one major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. per year and this will give us opportunity to catch up with all issues and documentation and there’s a need for a plan for that.

P.S. – Please drop your comments with your ideas for attracting more new contributors to the #docs team.

#meetings, #summary

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

X-post: Help Test WordPress 6.8

X-comment from +make.wordpress.org/test: Comment on Help Test WordPress 6.8

Agenda for Discussion Meeting (18-Feb-2025)

Meeting is scheduled with the following details:

WhenTuesday, 18-Feb-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. Design updates by @estelaris.
  6. 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 (04-Feb-2025)

Attendance

@atachibana @ninianepress @sagargurnani @leonnugraha @cwhitmore @dhavalkapadane @joelbarbara @benazeer @zeelthakkar @estelaris @milana_cap (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Project Checks

@atachibana has been working on the issues related to WP6.3 and likes to close them ASAP.

@karthickmurugan has completed 26 tickets, in which 3 of the issues moved to 2nd review and others pending for review.

@joelbarbara had discussed with @estelaris working on tickets related to release 6.2. So, he had worked on his first issue and wanted someone to review it.

@benazeer had worked on WP6.7 issue related to “post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.”, “site tagline” and “verse blocks” and now she is waiting for the review.

@dhavalkapadane he had added screenshots, videos, and steps to #1767 and wanted someone to review it.

Open Floor

@estelaris mentions that because 6.8 is a release with no new features. The docs team should focus on catching up with previous releases and work on anything that’s outstanding.

@ninianepress thinks the idea of trying some A/B testing and changing the name of the Triage meetings is a great initiative. She also thinks that trying something without data isn’t as helpful as it would be to ask people why they don’t attend and/or contribute to those meetings. May be the team could make a quick Google form with different options and a space to add our answers. That way, we have some more insight to make informed plans for further testing.

@ninianepress is also planning on facilitating a Contributor Day this month so she’ll keep everyone posted on that.

#docs, #meetings, #summary