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:

• Non-project roles → Meeting facilitator
• Facilitating weekly meetings workflow page, including the writing agenda section.

@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

• @zzap: Almost done with issue #2138 (recording video is remaining). Plans to complete another issue this week.
• @awetz583: Closed three issues: Classic block (#2141), Paragraph block(#2129), and Preformatted block (#2137)
• @estelaris: Closed 40+ issues for 6.4 dev notes. All work had been done previously but none of the issues were formally closed. Each was reviewed and missing links were added.
• @atachibana: Closed 2 issues for WordPress 6.2.
• @sajib1223: Closed 2 issues and 1 spam issue: #2186, #2160
• @rollybueno: Closed the Heading Block Overhaul (#2131) and its sub-tasks, plus 1 spam issue.

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:

• Reviewing an Issue — for more advanced contributors; needs critique and correction before publishing.
• Work on Existing Issues — ready to publish pending final review.
• File High Quality Issues — ready to publish pending final review.

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