Tag Archives: summary

Ritika Roy 8:29 am on November 13, 2025
Tags: , , summary   

Summary of Docs Team Meeting on 11th November

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next meeting:

  1. Where: #docs channel on Slack
  2. When: Tuesday, November 18, 2025 at 07:30 PM GMT+5:30
    Participants and Their Contributions:
    @milana_cap
    1. Facilitated the meeting, welcomed @ritikaroy2830, and shared onboarding resources:
    Onboarding Sessions for Documentation Team
    2. Provided the meeting notes format template:
    Summary of Docs Team meeting Nov 4, 2025
    3. Led project updates, discussed contributor rewards, and explained documentation review roles (First and Second Reviewer).
    4. Closed 4 documentation issues for version 6.8, stating only one left:
    GitHub Issue Tracker.
    5. Announced planned GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ automation for review checklists and notifications.
    6. Clarified roles for HelpHub, DevHub, Handbook, and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ releases documentation.
    7. Guided policy updates for documentation responsibilities on Themes and Plugins handbooks.
    8. Summarised action items: updating reviewing roles, renaming review roles, implementing GitHub automations, and updating the CONTRIBUTING documentation.
    9. Proposed automating replies for documentation issues outside Docs’ scope.
    10. Suggested a triage role for new and open issues classification.
    @atachibana
    Shared experience leading the Docs table at 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. Kansai and translation work. Confirmed willingness to continue as second reviewer for HelpHub.
    @Azhar Deraiya
    Reminded team about submitting contributions via the contributions form on the Docs blog sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.:
    Make WordPress Documentation
    Encouraged contributor submissions for badge assignments.
    @Arslan
    Led 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/. and Docs Table at WordCamp Islamabad 2025; submitted contributions through the contributions form.
    @estelaris
    1. Discussed project responsibilities and defined roles within Docs projects.
    2. Proposed detailed roles for first and second reviewers with checklist requirements.
    3. Emphasised task distribution for efficiency.
    4. Agreed on policy directing off-scope handbook issues to respective teams.
    5. Highlighted the need to update HelpHub and DevHub roles with detailed responsibilities, including issue review and closure.
    6. Recommended asking draft writers for changes when necessary.
    @MosesCursor
    Supported having experienced reviewers fill roles to maintain consistency.

    Main Points Discussed in the Meeting:
    1. Documentation roles are clearly defined with reference to team roles:
    Docs team roles
    2. Two-tier review system agreed upon:
    3. First Reviewer: Checks grammar, structure, style, screenshots, with guides:
    Grammar Guide,
    Writing Tips,
    Tone and Voice Guide
    4. Second Reviewer: Fact-checking and final approval.
    5. GitHub automation planned for checklist reminders and review label notifications.
    6. Policy updates to clarify the Docs team’s scope and proper handling of documentation issues for Themes and Plugins.
    7. Expanded HelpHub and DevHub roles to include issue review, documentation updates, and closure.
    8. Proposal for an issues triage role to handle new and open issues.
    9. Checklist to be created for reviewers detailing responsibilities.
    The End 🙂

#docs, #meeting, #summary

Milana Cap 4:05 pm on November 4, 2025
Tags: , summary   

Summary of Docs Team meeting November 4, 2025

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next meeting:

1. Meeting Time Confusion

  • The meeting began one hour later than planned due to daylight saving time changes.
  • Action:

2. Contributor Recognition Initiative

  • Discussion focused on improving recognition for contributions and clarifying the process for tracking them.
  • Reference post: Rethinking Contributor Recognition in Documentation Team.
  • A new contribution form was introduced to capture contributions not recorded anywhere else.
  • Proposal:
    • Contributors to submit their activities every week via the form.
    • Meeting leads will collect and announce the contributions during the meeting.
    • Weekly contributor badges will be issued and announced.
    • Contributions will be gamified: each submission earns points and titles, contributing to a leaderboard.
  • Action:
    • Contributors are asked to submit their contributions via the form.
    • @milana_cap to publish a detailed post explaining the recognition workflow and gamification proposal.

3. Regular vs. Release Contributions (led by @estelaris)

  • Continuing previous discussions around defining regular and release contributions.
  • Regular contributions include:
    • Attending meetings, writing up meeting notes, or leading meetings.
    • Attending contributor days (e.g., 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., MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area., external events).
    • Submitting issues to update documentation articles.
    • Note: Fixing typos is important but does not count as a regular meaningful contribution.
  • Release contributions refer to tasks related to specific WordPress version releases (e.g., the current 6.9 release). These contributions include:
    • Creating and managing project repositories (e.g., WP 6.9 documentation).
    • Updating articles, submitting new screenshots, reviewing documentation.
    • For developer docs, interacting with the release team, ensuring devnotes are documented (though not writing them).
    • Final tasks are done during the release party (see: Documentation process during a major version release).
  • Discussion around devnotes:
    • Currently, responsibilities for devnotes are unclear and need to be revisited after the 6.9 release.
  • Action: Clarify and document the specifics of release contributions after the 6.9 release.

    4. Conclusion & Next Steps

    • Action items:
      • All contributors should submit their contributions using the form on the Docs blog.
      • The team will review feedback and questions over the next week.
      • A follow-up discussion about contributions will take place in the next meeting.
    • Next Meeting:
      • Date: November 11, 2025
      • Time: 14:00 UTC (new time due to daylight saving time).

    #docs, #summary

    Jenni McKinnon 3:01 pm on September 16, 2025
    Tags: , , summary   

    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

    Akira Tachibana 2:20 pm on August 3, 2025
    Tags: , summary   

    Summary of Docs Team meeting July 29, 2025

    Attendance

    @milana_cap, @atachibana, @azharderaiya, @jadavsanjay, @dhruvang, @areziaal, @nikunj8866, @vasantrajput, @areziaal, @estelaris, @Mosescursor, @rollybueno, @ravigadhiyawp, @dilip2615

    Housekeeping

    Find the complete Transcript of the meeting on Slack.

    Open floor

    Reminder to Proposal

    Responsible AI workflow for creating new documentation for WordPress 6.9
    @estelaris is working on the second part of that proposal so she can present it Mary. If anyone has any comment for the proposal, please leave them on the link.

    Summer break

    [Plan] Meetings will resume on September 2. This is the same as the winter break: no meetings, but feel free to contribute.

    #meetings, #summary

    Jenni McKinnon 5:18 pm on July 22, 2025
    Tags: , , summary   

    Summary of Docs Team meeting July 15, 2025

    Attendance

    @ninianepress, @milana_cap, @atachibana, @dilip2615, @rollybueno, @estelaris, @ravigadhiyawp, @nikunj8866, @azharderaiya

    Housekeeping

    Find the complete Transcript of the meeting on Slack.

    Upcoming meetings

    Project check

    @atachibana reviewed, edited, and closed 4 end-user documentation issues.

    Open floor

    @estelaris shared these updates about the next release:

    For the 6.9 release, I would like to add a process for HelpHub where we can use AI to help us write faster and perhaps have the articles on time for the release. More on that soon as I still need to confirm this with the release team.

    #docs, #meetings, #summary

    Jenni McKinnon 8:27 am on July 2, 2025
    Tags: , , summary   

    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

    Jenni McKinnon 5:59 am on June 18, 2025
    Tags: , , 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

    Nikunj Hatkar 9:40 am on May 7, 2025
    Tags: , , summary   

    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

    Sagar Gurnani 6:18 am on April 2, 2025
    Tags: , , summary   

    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

    Karthick 1:09 pm on March 6, 2025
    Tags: , , 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