Tag Archives: meeting

Velda 11:12 pm on February 17, 2026
Tags: , meeting,   

Documentation team meeting notes – February 17, 2026

Where: #docs channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/
When: Tuesday, February 17, 2026 at 14:00 UTC
Meeting Facilitator: @sagargurnani
Note Taker: @supernovia
Find the complete meeting on Slack.

Next Meetings

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 3, 2026 at 14:00 UTC
Facilitator: @supernovia
Note Taker: @azharderaiya

Discussion Meeting

Where: #docs channel on Slack
When: Monday, March 10, 2026 at 14:00 UTC
Facilitator: @estelaris

Next Meeting Volunteers & Facilitation Resources

After a request for facilitators and note-takers for the March 3 meeting, @supernovia agreed to facilitate, and @azharderaiya will take notes. This will be the first time for each of them in these roles, so @zzap shared these guides:

@zzap also noted that the team no longer keeps a roll-call style attendance list in meeting notes, and @sagargurnani will connect with @azharderaiya privately to help guide him through the note-taking process.

Project Checks: Contributions

The team is now down to 689 open issues, with 64 issues closed in the past week alone. @zzap and @estelaris both thanked everyone for their hard work, with special recognition for those working on the blocks overhaul.

Open Floor

Handling Old & Deprecated Issues

@estelaris raised a question: since the inventory work is surfacing very old issues (6.3 and older), should issues for blocks that have already been updated to 6.9 be closed?

Decision:

  • Yes — close them, referencing the newer issue number where applicable.
  • Exception: If a feature was introduced in an old version and was never documented in later updates, keep it open.
  • For deprecated blocks with broken images from old versions: remove the broken image from the article and close the issue with a comment noting the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. was deprecated and will no longer be updated. Contributors are encouraged to follow this same approach when encountering similar issues.

WP Credits Program Updates

Handbook Review by @rossanatrujillo: @estelaris shared that @rossanatrujillo, her mentee from the WP Credits program, is reviewing the Docs handbook in both Spanish and English and has submitted her first draft for review:

  • Google Doc — Handbook Review Draft
  • Anyone is welcome to read and leave notes. The first part is in Spanish, the second in English.
  • The goal is for this review to help update the handbook.

@estelaris expressed appreciation for the program, noting that mentoring is a mutual learning experience around best approaches, goals, and reasons behind handbook content.

Contribution Pathways

@supernovia shared three “contribution pathway” one-pagers created by @clk87:

Goals for these guides:

  • Provide clear, step-by-step entry points for new and existing contributors.
  • Eventually be linked from the main contribution index (final location still to be decided).
  • Support a growing pool of 200+ student contributors looking for ways to contribute, with more students coming.

@zzap thanked the team for this work and plans to review the documents and possibly adapt them for the Docs gamification initiative.

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 by the repository owner. https://github.com/ Automations, /assign, and Workflow Improvements

@awetz583 reported another instance where /assign failed to assign an issue in GitHub.

@zzap clarified that /assign can fail when:

  • Someone is already assigned to the issue, or
  • The issue has a status label other than “To do.”

All current automations (including /assign behaviors) are custom-built by @zzap. There are many edge cases that can’t be covered, or are too expensive to run because GitHub would need to process all issues. The automations are good for getting things started but need refining and/or re-doing. @zzap expressed openness to revisiting these workflows and @clk87 may be able to assist with this effort.

@supernovia raised a related question: can contributors be unassigned if they self-assign and then abandon an issue?

Current situation:

  • No automatic unassigning for inactivity.
  • Admins can manually unassign people from issues.
  • If someone uses /assign on an already assigned issue, they receive an automated notice advising them to contact @zzap.

Review Process

@supernovia asked whether anyone can review issues, or if a certain status is required first — and whether allowing broader reviews could help clear the backlog.

  • @zzap noted it’s difficult to give a blanket answer; it depends on what is being reviewed and what needs attention.
  • @estelaris confirmed that anyone can review, and that the team will be reviewing more often now that systems are getting back in order.
  • @supernovia suggested the idea of a preliminary review step.
  • @estelaris explained that related issues are being gathered together, with the goal of updating as much as possible up to 6.9 so the team is ready for 7.0.

Action Items

  • For any /assign misbehavior, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @zzap directly.
  • Revisit and possibly redesign current workflows and automations.
  • @clk87 may be able to help with automation improvements.
  • Work through the backlog of abandoned or stalled issues.
  • @sagargurnani to connect with @azharderaiya to guide him through note-taking.
  • @zzap to review @clk87‘s contribution pathway documents and explore gamification integration.
  • Team to revisit assignment/abandonment workflows and work through the backlog of stalled issues.
  • Anyone interested is welcome to review @rossanatrujillo‘s handbook draft (ES) and leave feedback.

#docs, #meeting, #summary

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

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 by 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

noumantech 6:36 am on January 12, 2024
Tags: docs-meeting, meeting,   

Summary of Docs Team meeting January 9, 2024

Attendance

@leonnugraha  @milana_cap  @ninianepress @atachibana @hellosatya @cold-iron-chef @fitehal @anandau14 @estelaris @noumantech Async: @sagargurnani

Housekeeping

Project Checks

@milana_cap shared the update about closing #293 and hopes to complete the image blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. by next week.

@atachibana reviewed the #291 and will work on it.

@leonnugraha reviewed and closed #300, and working on #463.

 @sagargurnani worked on #203 and completed the ticket.

Open Floor

@estelaris shared the work on the post about translating HelpHub and said she would post it on #polyglots and x-post it to #docs. It will be ready before tomorrow’s polyglots meetings.

@estelaris guided @hellosatya on how to start documentation with the Docs team.

@milana_cap shared the style guide, and @ninianepress shared the onboarding information with the newcomers.

@milana_cap shared the top priority issues of end-user docs with the @noumantech

@estelaris emphasized translating first the site map and writing or improving the language style guide.

#docs-meeting, #meeting, #summary

noumantech 7:44 pm on September 6, 2023
Tags: , meeting,   

Summary of Docs Team Biweekly Meeting (September 05, 2023)

Attendance

@noumantech @cold-iron-chef  @sagargurnani @marcio-zebedeu @leonnugraha @milana_cap  @estelaris @611shabnam @javiercasares @devmuhib @jyolsna @atachibana 

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next Meetings Facilitators and Note Takers

Project Checks

@milana_cap added contributing docs and Serbian language to the new HelpHub repo. She has also started working on #1102 and started retiring old articles that are moved to the Advanced Administration Handbook. @milana_cap created a new project board for inventory of end user docs and collected all HelpHub articles and categories via REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/

@sagargurnani completed the #935, self-assigned #203, and asked @milana_cap about the status of #935.

@611shabnam is still working on #678 and her progress is slow due to deadlines in the current month.

@leonnugraha shared the progress of US Contributors Day. He completed and closed #694, #973, #947, #936, #937, #941, and #975.

@jyolsna completed #974 by updating the screenshots.

@marcio-zebedeu is working on #978 and needs more time to complete it.

@cold-iron-chef is behind on one issue and will complete it by next week.

@estelaris shared his plans to start work on Future plans for HelpHub, the documentation team handbook, and finish the WP End-user docs inventory. @milana_cap and @estelaris discussed the schedule to collaborate on various days on these tasks.

Open Floor

@estelaris shared the Figma design for the proposed design of HH’s landing page and asked the Docs Team to have a discussion for approval. Matt is not happy with the design and needs improvement in fonts and spacing. @milana_cap raised a concern about the wasting of space in the categories section of the landing page design.

@leonnugraha shared screenshots from the Figma design and suggested an increase in the font size of headings. @estelaris mentioned that the current heading font size in the template should be suitable for all languages. @cold-iron-chef supported the point of general rules for different languages by sharing her experience with French/English Websites.

@estelaris asked everyone to leave comments on the Figma File and told team members to Click on the :speech_balloon: icon if anyone has a problem leaving comments.

@estelaris shared another proposal for the translation and localization of docs for review. The design is not final and it will be published on the next day after the meeting.

#docs, #meeting, #summary

Jenni McKinnon 1:37 pm on May 16, 2023
Tags: , meeting,   

Summary for Docs Team meeting, May 2, 2023

Attendance

@ninianepress @milana_cap @hilayt24 @chaion07 @femkreations @sereedmedia @medesigngood @leonnugraha @kafleg @sonalithakkar @ninthcoder @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap closed 7 issues.

@femkreations completed issue 485.

@leonnugraha reviewed #695.

@larassattidn and 281.

Reminder about Docs Team 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/

For all those that attended the last Docs Team Contributor Day, please be sure to comment on the corresponding GitHub issue with what you worked on that day.

The next Docs Team Contributor Day is May 23, 2023 from 1 PM UTC to 4 PM UTC.

Open floor

@milana_cap asked if there was any feedback from our last Contributor Day.

@ninianepress suggested breakout rooms in Zoom so that contributors who need it can be onboarded. At the next contributor meeting, we will ask if any one is in need of onboarding, then open a breakout room, as needed.

The team decided to continue with a 3-hour long Contributor Day and that the fifth Tuesday in May will be a triage meeting, following the week after our next Contributor Day.

@estelaris wrote Explorations for a notification form between documentation and Rosetta sites and would love contributor feedback in the comments.

#docs, #meeting, #summary

Jenni McKinnon 2:18 am on April 25, 2023
Tags: , meeting,   

Summary for Docs Team meeting, April 18, 2023

Attendance

@leonnugraha @milana_cap @bph @atachibana @james-roberts @ninthcoder @ninianepress @cristianozanca @javiercasares @mujuonly @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@leonnugraha reviewed and closed five HelpHub issues.

@milana_cap worked on fixing six issues we got via HelpHub feedback form at the 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. Torino 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/. Milana is also monitoring HelpHub for new feedback.

@atachibana has completed issues #739 and #744.

@estelaris posted Integrating the Mobile app documentation into HelpHub.

Monthly Docs Team online contributor days

In the last bi-weekly Docs Team meeting, @ninianepress proposed a quarterly and independently-led docs team contributor day, much like the first ever one that was held in 2022, which was @milana_cap‘s idea.

@milana_cap suggested a monthly day, which was decided upon.

In the meeting mentioned above, the docs team discussed a new structure for weekly meetings that would include the monthly contributor day.

For details on this, check out Monthly online Docs Team Contributor Day starts April 2023.

Next Docs Team contributor day details and onboarding

The next meeting will be a monthly online Docs Team Contributor Day, following in suit with the new structure above.

When: Tuesday, 25 April 2023, 1:00-4:00 PM UTC

Where: #docs channel on Slack, and on Zoom.

Please also check out Contributor Day – 25th April, 2023 on 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 by the repository owner. https://github.com/ for onboarding and other details.

If you plan on attending and also on the day, be sure to comment on the GitHub issue with:

  1. Your WordPress.org profile username
  2. Link(s) to the issue(s) you were working on during the Contributor Day

Mobile app documentation structure

@estelaris posted on the Docs Team blog about the WordPress mobile app end-user documentation being integrated into HelpHub:

  • Two options for including the mobile app documentation include:
    • Create one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. mobile app and all the topics as subcategory
    • Add each article inside the categories/subcategories we have now
  • The first option to create a new category was the final team decision.

WCEU Contributor Day Docs Team facilitator

For WordCamp Europe (WCEU) 2023 there will be a Docs Team table and @milana_cap will be leading it.

#docs, #meeting, #summary

Femy Praseeth 2:29 am on April 22, 2022
Tags: meeting,   

Summary of Docs Team Meeting April 19, 2022

Housekeeping

Review of the design for documentation 

The design team has reviewed the design. We are waiting on Josepha’s approval. The mobile version is not ready yet as there are a few items to be resolved. 

  • We now have 4 categories for the content and a submenu with the 4 categories, displayed at the top so users can easily navigate. 
  • The breadcrumbs are included as part of the left navigation (the blue square on the top left). The first 3 lines are the breadcrumbs, followed by the headings in the article. We also have another option (on the 3rd article example) where the breadcrumbs are horizontal, at the top of the TOC blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience..

Please add your comments here or in the slack channel.

Discussion 1: @femkreations: How are we handling the Changelog section since some of the Changelog entries are long?

@milana_cap: suggests not to delete the Changelog as it’s a history of the WP docs.
@bph: The Changelog is also used for translation and some locales might be behind on the pages.
@ibdz: We can have 2 different font sizes- one for the parent <li> (date) and one for secondary level <li> (content) to keep it aesthetically pleasing.

It was decided to add pagination to the Changelog. It is accessible and we can limit the number of entries per page, keeping the newest entries on page one and the oldest on page 2.

Discussion 2: @milana_cap: Would the definition list be semantic markup for the Changelog?

 @mburridge suggests the details disclosure element

Discussion 3: @estelaris: What about the FAQs that are on some of the block articles? Are we going to keep them there or can we extract them and create a new FAQs section under resources?

@milana_cap: Thinks all FAQs should be in FAQs and articles that currently have them could link to them.
@atachibana: Suggests keeping it as is, to reduce the cost, and also create independent pages of the FAQ.
@ibdz: Thinks from the user’s point of view, it’s good to have the FAQ attached to the page.

Project updates

@milana_cap:

  • Closed a few more 5.9 block editor end-user issues.
  • All tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets are labeled for docs and GitHub project is ready.
  • We have a new channel #docs-firehose for getting 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 by the repository owner. https://github.com/ updates so that we keep the #docs channel clean

@femkreations:

  • Triaging the Google Doc and creating the Tracker issues for 6.0 end-user documentation.
  • So far, 40 trackers have been added for 6.0 End User Documentation.
  • Will complete the triage by the end of the week.

@estelaris:

All the block editor articles listed in the inventory have been added to the new sitemap.

Open floor

@estelaris and @femkreations to review the following two pages: Block Editor and WordPress Editor to make sure they are not repetitive and if so, merge and delete one. @atachibana: Suggests renaming WordPress Editor to Classic Editor and keeping with TinyMCE.

@milana_cap gave a talk about Docs 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. Athens in person.

@milana_cap to lead the Docs table at the 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/ for WCEU.

#meeting, #summary

Ahmed Kabir Chaion 6:19 am on November 23, 2021
Tags: , meeting,   

Agenda for Docs Team Meeting 23 November 2021

Our next Team meeting is scheduled with the following details:

When: Tuesday, November 23, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Attendance
  2. Note-taker & Facilitator selection for Next Meeting
  3. Project Updates
  4. Revision of Projects that have been put on hold
  5. Open Floor

#agenda, #meeting, #meeting-agenda

Ahmed Kabir Chaion 9:19 am on April 26, 2021
Tags: , meeting,   

Agenda for Docs Team Meeting April 26, 2021

The next meeting is scheduled with the following details:

When: Monday, April 26, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda:

  1. Project Updates
  2. New Member Mentoring
  3. Unified Doc License
  4. Author Attribution to docs
  5. Discussion: Process gap between dev notes release stage and docs team writing about a feature
  6. ‘Meeting Day’ Adjustment
  7. April 2021 Coffee Break
  8. Open Floor

Please feel free to suggest agenda items by commenting on this post or by raising it during Open Floor.

Thank you!

#agenda, #meeting, #meeting-agenda

Ahmed Kabir Chaion 1:16 pm on December 14, 2020
Tags: , meeting   

Agenda for Docs Team Meeting December 14, 2020

The next meeting is scheduled with the following details:

When: Monday, December 14, 2020, 15:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Project Updates
  2. Meeting Times & Holiday Planning Announcement
  3. New Member Mentoring
  4. Monthly Coffee Break December 2020
  5. Google Season of Docs 2020
  6. Discussion: Clarification about the use of GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. by WordPress plugins and themes
  7. Open Floor

#agenda, #meeting