Triage Squad GitHubGitHubGitHub 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/ triage: Biweekly on Thursdays 07:00 UTC
Date: June 27, 2026 Time: 14:00 to 15:00 UTC (local time) Platform: Zoom Recording: internal, not published Moderator: Sumit Singh (@sumitsingh) Note-taker: Rico F. Lüthi (@rfluethi)
This session had three participants. The items in the Recommendations section are therefore explicitly recommendations, not team decisions. Please share feedback by the next weekly Tuesday meeting, as a comment on this post or in the #trainingSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel.
Participants
Name
WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile
Ibrahim Nasir joined for the first time. He is a Support Engineer at Proper Fraction LLC, has been active on WordPress.org since 2019, and works mainly in the Support team. His experience can help the team with organizational questions.
Context
The session focused on two things: an open review of participation and of how the meeting formats are scoped, and a joint pass through the Office Hours issues in the WordPress/Learn repository. There are around 526 open issues in total; seven of the Office Hours issues were closed in this session. One observation from the group: many people attend the weekly Tuesday meetings, but many of them only read along. For the Office Hours, there is little feedback on whether the format works.
Topics
1. Meeting formats: Office Hours, TT-Admins, and the Tuesday meeting
The group discussed that the Office Hours should be cancelled if they do not reach higher attendance, and that the format is promoted too little at the Tuesday meetings and in the monthly reports. It is striking that the Triage meeting, which has not run for months, is mentioned all the time, while the Office Hours meeting is not. Office Hours without participants are effectively a TT-Admins meeting.
The proposal is to clearly separate the three formats, so it is obvious which topics belong where. The two additional formats (Office Hours and TT-Admins) are public and minuted, so everyone can take part and absent contributors can follow up asynchronously.
Format
Cadence
Purpose
Which topics belong here
Tuesday meeting (main meeting)
weekly
Central information and coordination for the whole team
Overall status, announcements, open proposals and votes, reports from Office Hours and TT-Admins
Office Hours
monthly, public, minuted
Substantive discussion and idea evaluation
Cross-cutting and strategic topics, new ideas and their viability, proposal preparation, open questions, onboarding topics
TT-Admins meeting
scheduled regularly, cancelled when not needed
Administrative processes and issue tracking
Issue triage and backlog maintenance, administrative decisions, responsibilities, operational work
A coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. task of the Office Hours is to evaluate new ideas together first (in a brainstorming issue) before anyone writes a proposal. Small-scale admin and triage work does not belong in the Office Hours; it belongs in the TT-Admins meeting. Whether the TT-Admins meeting and the Triage meeting are kept separate or merged is still to be decided. The split should be written up as a proposal (#3536), discussed, evaluated, and anchored in the handbook.
2. Collaboration instead of single proposals
Ideas should be evaluated together before anyone takes on the effort of a proposal. This is the core task of the Office Hours as a public, minuted space, and the reason a regular live meeting is needed despite fluctuating attendance: direct exchange is hard to replace asynchronously. Sumit shared the view that too few people confirm an idea and drive it forward.
3. Issue pass
Strategy: close completed and outdated tickets, and reopen on objection. Seven of the Office Hours issues were closed in this session. The regular cleanup of the backlog is a standing goal for the coming meetings. The individual issues are listed in the Action Items.
4. Badge system
The badge system feels intransparent to parts of the team. The plan is to collect ideas internally in issue #3487 first, turn them into a public proposal (#3539), and then build a work list with responsibilities and a clear checklist. Important to note: the official badges on profiles.wordpress.org are not assigned by the Training Team alone, but in coordination with the Community and MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. teams. The team can clearly define its own contributor recognition; changes to the official badges require coordination with the responsible teams.
5. 2026 goals
Instead of yearly goals, the team should set shorter goals (about three months), so newcomers see the current plans. The goals should be written using the SMART method (specific, measurable, attractive, realistic, time-bound) and stay connected to the team vision and the wider WordPress goals (#3475).
6. Organization and next meeting
If it is decided to continue the Office Hours, the next meeting will probably be on July 26, 2026, 14:00 UTC (#3535). Because Rico cannot attend the Saturday Office Hours in July, the group discussed whether the meeting could move to a Sunday (July 26) as an exception. Otherwise it should take place on Saturday, July 25. Sumit will clarify this.
Recommendations (for the team to confirm)
#
Recommendation
Consensus of attendees
1
Close all issues that have not been touched for a year; reopen on objection by the people involved
Yes
2
Set shorter goals (about three months), write them with SMART, and align them with the vision and the community goals
Yes
3
Add the Office Hours as a fixed item in the weekly meetings and minutes, mention them in the monthly reports, and promote them more visibly
Yes
4
Collect badge ideas, open a proposal, develop a checklist and responsibilities, and coordinate with Community and Meta
Yes, as a proposal
5
Next meeting probably Sunday July 26, 2026 (as an exception) or Saturday July 25, 14:00 UTC, pending Sumit’s clarification
Reach out to Nikola and Maria as a fallback for WordCampWordCampWordCamps 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. Europe
Host the BlockBlockBlock 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. Editor workshop for Note Takers
Define badge-hunter filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. measure
Migrate the Office Hours topic list into the Learn GitHubGitHubGitHub 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/
Date: probably Sunday, July 26, 2026 (as an exception), otherwise Saturday, July 25, 2026; Sumit to confirm Time: 14:00 UTC Issue:#3535 Moderator: open Note-taker: open
#13 Meeting formats: separate Tuesday meeting, Office Hours, and TT-Admins
#14 Office Hours topic collection: migrate the personal project board into the Learn GitHub
#15 Office Hours topics: let contributors prioritize so urgent items surface
#16 TT-Admins meeting and Triage: clear separation vs. merge
#17 Badge system reform: proposal, checklist, and responsibilities with Community and Meta
Get involved and resources
Everyone is welcome to contribute, whether or not they join the Office Hours. Please share feedback on the recommendations by the next Tuesday meeting, as a comment or in Slack.
