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
Five contributors attended, and a single question ended up carrying the entire session: what are the Office Hours actually for? The answer we arrived at is that each session should center on one topic announced in advance, rather than a walk through open tickets. A second theme emerged from that discussion and proved to be the most valuable part of the hour: what keeps contributors without a technical background from becoming active on 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/?
No note-taker had been designated beforehand, so Sumit Singh wrote this recap. A note-taker will be named ahead of the next session. Everything listed under Decisions was agreed in the meeting; the Recommendations are proposals that still require the team’s confirmation. Feedback is welcome before the next Tuesday meeting, either 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
Saidul Islam Bokul attended the Office Hours for the first time. He works as a Full Stack Digital Marketer, has been active on WordPress.org since 2023, contributes to the Bengali translations, and wrote the recap of the Tuesday meeting on July 21. His outside perspective shaped the session. Andrew Ssanya is a Digital Skills Facilitator at Edutech Club in Kampala and contributes as a note-taker. Vasantsinh Rajput is a freelance WordPress developer who mentors the team’s note-takers.
Topics
1. What the Office Hours are for
Sumit opened with a candid observation: a good number of people commit to attending during the Tuesday meeting, yet few of them appear in the session itself. That observation quickly became a question of purpose. The common ground we reached is that the Office Hours depend on a topic that is known in advance and draws in the people who care about it. Reviewing and clearing open tickets is organizational work, and it belongs in the TT-Admins meeting. This carries forward the separation of formats set in motion on June 27 (Write and publish the meeting-formats proposal, #3536). As a compromise, roughly 15 minutes of each session remain reserved for tickets that have clearly gone stale.
The discussion also revealed that two distinct problems had been folded into one: the purpose of the Office Hours, and the lack of commitment within the TT-Admins group. Each calls for its own remedy.
2. How the topic gets chosen
The process we settled on: propose three clearly distinct topics from the topic list, put them to the weekly Tuesday meeting for selection, and confirm the winner before the session. Those three should address questions that genuinely move the team, such as the status of credits or badges, rather than fine-grained organizational matters. To keep the selection from reflecting only the organizers’ vantage point, Saidul was asked directly for his read as a newcomer. His choice: Note-taking and publication workflow: who does what, and how? (#3565). Vasant should be in the room for it, since he mentors the note-takers. A ticket for prioritizing topics is already on file (Set up prioritization for Office Hours topics, #3538).
3. Getting started on GitHub without a technical background
The most valuable stretch of the session, and it came from Saidul. He described plainly how the standard advice, go find yourself an issue on GitHub, stops him in his tracks: his background is marketing, and he has never worked with the platform. Note-taking, by contrast, comes naturally to him, because it aligns with how he already works.
Asked which would help more, a workshop on GitHub or a weekly guided session in which the group works through tickets together, his answer was unequivocal. The basics first, the guided work second. Without a foundation, even guided work remains disorienting, and the same holds for other contributors arriving from marketing and content roles.
Sumit then demonstrated live what an entry point without technical prerequisites looks like: in the WordPress/Learn repository, 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. for translation tickets, select a Bengali one, volunteer as a reviewer, examine the linked document, and comment on the outcome. Contributions of this kind also surface on the WordPress.org profile. Verifying reported problems, broken links among them, counts as a contribution in its own right, even when the fix comes from someone else. Saidul committed to taking on a first ticket the following day; Andrew intends to join after his next note-taking assignment.
4. The issue backlog and the target of 100
As of July 26, the WordPress/Learn repository held 545 open issues. At that volume, a newcomer has no way of telling which ticket matters. The target for the next six months is no more than roughly 100 open issues, and Sumit confirmed it as the team’s principal goal.
Vasant made the arithmetic plain: five people meeting once a month will not clear 500 tickets. Sumit therefore sketched a lightweight alternative, namely selecting five to ten tickets per week, working through them in 15 to 30 minutes, commenting, and closing them after a short grace period if no one responds. That is essentially the former Thursday triage session, which has not convened in a long time. Its real value never lay in the triage itself, but in following along and asking questions, which is precisely what new contributors need. A restart hinges on three or four people being dependably available, so that the work does not settle back onto the same few shoulders. How triage and the TT-Admins meeting relate to one another is already tracked in TT-Admins meeting and Triage: separate or merge (#3476).
5. Local language groups
Sumit placed the purpose of the Office Hours in a broader frame: part of the point is to include people who speak neither English nor German, and to let them contribute in their own language. In the German-speaking region, a Training Team subgroup of roughly 15 people has taken shape. What remains unresolved is the connection between the international team and local groups: translation, visibility for local work, and a discernible path from a local group into the wider project. The subject goes on the topic list in its own right.
6. Visibility: recordings and a channel of our own
Vasant proposed recording recurring tasks as short videos and sharing them with the group, so that anyone who misses a meeting can still pick up the work. The GitHub demo from this session is the first candidate. This intersects with the note-taking workshop that has been pending for some time (Host the Block Editor workshop for Note Takers, #3478 and Record the screencast tutorial for Note Takers, #3479): the sensible sequence is to demonstrate the process first and derive a written guide from it. Sumit expanded the idea into a dedicated YouTube channel for Learn WordPress, along with additional social media accounts, on the grounds that not every kind of content belongs on WordPress.tv. Vasant then set a clear order of priority: recruit new admins and distribute the existing workload first, social media after that. Sumit concurred. This subject, too, goes on the topic list.
7. Organization
The Office Hours topic list currently resides in a personal repository. It belongs in the Learn repository, together with a template that allows anyone to propose a topic; the ticket for this already exists (Migrate the Office Hours topic list into the Learn GitHub, #3537). Sumit takes on the template, with the existing list and the current topic template available as a starting point.
On admitting new contributors the principle is straightforward: anyone willing to help should be able to take part. Saidul and Andrew are to be added without delay. In practice this runs into a constraint. A dedicated private Slack channel for the TT-Admins was not approved, so the group relies on a private group conversation that Slack caps at nine people, and those nine seats are taken. The existing private channel #training-guides was raised as a possible way around this, a space where guides and TT-Admins could convene. That remains a suggestion rather than a decision: the guides need a room of their own in which to support one another. The venue for the TT-Admins conversation is therefore still open, and the request to the 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. team will be filed again, this time with the obstacle documented.
Props
Andrew did outstanding work on the lesson thumbnails, and everyone present congratulated him during the session.
Decisions
#
Decision
1
Every Office Hours session gets one main topic, announced in advance; reviewing and clearing open tickets belongs in the TT-Admins meeting
2
Topic selection: three distinct topics from the topic list, a vote in the Tuesday meeting, confirmation before the session
Roughly 15 minutes per session for old tickets; whatever is no longer relevant gets closed
5
Six-month goal: reduce open issues in WordPress/Learn from 545 to approximately 100
6
The topic list moves into the Learn repository (#3537); Sumit creates a template
7
Saidul and Andrew join the TT-Admins conversation without delay; the venue for that conversation still has to be settled
8
Next meeting: Saturday, August 22, 2026, 14:00 UTC (#3535)
What comes out of this session
New issues, with numbers to be added once they are created:
A foundational GitHub introduction for contributors without a technical background, delivered as a concise written guide or a recording of 20 to 30 minutes, linked from the onboarding page and the handbook. Owner still to be named.
A closing rule and a plan for reducing the backlog: put the rule in writing, report the count monthly in the Tuesday meeting, and revisit the target after three months.
File the request for a private TT-Admins channel again, with the obstacle documented and an interim arrangement recorded.
To be added as comments on existing issues rather than as new tickets:
New subjects for the topic list: connecting local language groups with the international team, a video and social media presence for the Training Team, and onboarding new TT-Admins.
Action Items
Task
Owner
Due
Write and publish this recap
sumitsingh
2026-08-02
Select three topics and put them to a vote in the Tuesday meeting
team-reps
2026-08-11
Create the topic template in the Learn repository (#3537)
sumitsingh
2026-08-22
Post notes and a revised agenda for the TT-Admins meeting
sumitsingh
2026-07-27
Set and announce a fixed day and time for the TT-Admins meeting
sumitsingh
2026-08-22
Settle the venue for the TT-Admins conversation and add sibokul and andrewssanya
sumitsingh
2026-08-02
File the channel request with the Meta team again
team-reps
2026-08-22
Prepare the guided triage session and confirm availability (#3476)
team-reps
2026-08-22
Take on a first ticket: comment on a Bengali translation review
sibokul
2026-07-27
Record short walkthroughs of recurring tasks and share them
sumitsingh, vasantrajput
open
Draft a proposal for a YouTube and social media channel
sumitsingh
2026-08-22
Join the GitHub sessions after the next note-taking assignment
andrewssanya
open
Design the foundational GitHub introduction
to be determined
open
Recommendations (for the team to confirm)
#
Recommendation
1
Announce the main topic at least two weeks ahead, in Slack and in the Tuesday meeting
2
Place the 15-minute ticket round at the end of the session, so that it cannot crowd out the main topic
3
Put the closing rule in writing: no activity for a year, a comment setting a two-week notice, then closure, with reopening on objection
4
Give the foundational GitHub introduction a named owner instead of leaving it as an idea
5
Before launching a YouTube and social media channel, establish who will maintain it over the long term
Next meeting
Saturday, August 22, 2026, 14:00 UTC (local time), issue #3535. Moderation and note-taking will be assigned in advance.
Main topic:Note-taking and publication workflow: who does what, and how? (#3565). The aim is a written workflow with named responsibilities for turning meeting notes into published posts. The documented path runs from a GitHub draft through a review of roughly 48 hours to a post on Make WordPress, though it has yet to be confirmed in practice. Guiding questions: who takes notes during the meeting, and how are those notes structured? How does the review work in practice, and who gets notified? Who holds editor access for make.wordpress.org/training? Could we assemble a pool of rotating note-takers, as we do for moderation? And what is the smallest note that still merits publication?
Get involved
You are welcome to contribute, whether or not you attend the Office Hours. If you are new and unsure where to begin, translation reviews in the Learn repository are an entry point that requires no technical background.
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.
This was the second session in the new Office Hours format. Since not all participants were available on time and the Learn Zoom account was not accessible at the start, the meeting continued on a private Zoom account.
In terms of content, the meeting picked up the open topics from April 18. Sumit prepared a first version of the 2026 goals, which the team discussed both in substance and in process. The group also discussed how onboarding for new contributors can be made simpler and clearer. Several ideas came up, including improving the handbook and reviving the Guide Program. These topics will be explored in more depth and made concrete in one of the next sessions.
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
The introductions were shorter than at the kick-off. Huzaifa Al Mesbah from Bangladesh introduced himself as a returning contributor to the Training Team. He has been active in the WordPress community since 2023, mainly in the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and Test teams, and was recognized as a Noteworthy Contributor with WordPress 7.0. Huzaifa now wants to engage more in the Training Team, which is great news for us, as we welcome an experienced WordPress developer on board. From his perspective as a newcomer to the Training Team, he noted that many people attend the weekly SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ meetings, but the path into active contribution remains unclear.
Topics Discussed
1. 2026 Goals
Discussion:
Sumit prepared a first draft of the 2026 goals and gathered feedback from the team several times. Rico then wrote a revised version on top of that. Both documents will now be read together and consolidated into an official 2026 goals list.
Sumit emphasized that the goals also matter for external communication, for example when contributors at a 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. ask about the team’s focus areas.
We discussed that we are late with defining the 2026 goals. The problem, however, is not that we have no goals, but rather that we have too many, which creates the risk that none of them get achieved. In that context, we also discussed whether it makes sense to define goals on a yearly cycle at all. Experience shows that toward the end of the year we have other priorities than setting goals for the next year. What matters most is that we have goals everyone understands, with a clear purpose, a timeline, and concrete work for implementation. As an alternative approach, the group considered a longer-term goals list from which, for example, the three most important items are picked each quarter and worked on concretely.
For the wording, the goals will be formulated according to SMART criteria (specific, measurable, attractive, realistic, time-bound). The goals will also be aligned with our vision and with the goals of the broader WordPress community, so that they remain connected in content. After the internal evaluation, the consolidated goals list will be published on Make WordPress Training, so that the discussion and decision can happen across the whole team.
Outcome:
Two working documents exist: a first draft by Sumit (with many comments) and a version by Rico.
Both will be read, commented on, and merged at the next meeting by June 27.
The consolidated goals will be formulated according to SMART criteria and aligned with the vision and the community goals.
A model with a longer-term goals list, from which three quarterly priorities are selected for concrete implementation, will be evaluated.
After the evaluation, the goals will be published so that the discussion and decision can happen across the whole team.
Open questions:
Which content from both documents will be taken over?
Which three goals get the highest priority?
Which vision points and community goals should we use for the alignment?
Do we keep the yearly cycle or move to a rolling, quarterly model?
2. Training Handbook Revision
Discussion:
The main problems identified in April still exist: outdated content, a lesson order that is hard to follow, and duplicated titles with different content. Muhibul is working on critical sections. Rico proposed consolidating the handbook first and then translating in a targeted way. A good first step would be to revise the entry sections “About” and “Getting Started” so that they can be translated into different languages when needed. From a newcomer’s perspective, Huzaifa pointed out that the landing page should make the next sensible step clearer.
The group also discussed whether it makes sense to translate the entire handbook at all. A full translation would significantly increase the maintenance and update effort, because every change would have to be carried over to all language versions.
The group also discussed introducing a “Last Reviewed” entry per handbook page. Unlike the original publication date (“first published”), “Last Reviewed” shows at a glance when a page was last checked. This makes the maintenance need visible and manageable, instead of relying on the original date. Vasant added the example of WPForms, where documentation pages show not only the update date but also when the page was last reviewed and who is responsible. A similar display could increase the motivation of contributors to work on individual pages.
Everyone agreed that the handbook must again become a central rulebook that we follow. When content becomes outdated or no longer current, the handbook is updated first. The handbook is the most important rulebook for our teamwork.
Outcome:
Continue the inventory of outdated and duplicated content in the TT-Admins pool.
Prioritize the revision of the “About” and “Getting Started” entry sections so that they can be translated into other languages when needed.
Critically evaluate a full translation of the handbook, since it would significantly increase the maintenance effort.
Prioritize the revision of the handbook landing page.
Introduce a new “Last Reviewed” field instead of “first published”. Use the WPForms example as a reference for the display.
Anchor the handbook as the central rulebook: changes in how we work are reflected in the handbook first.
Open questions:
Who (role or group) takes over which inventory areas?
Who implements the “Last Reviewed” field technically?
Which additional displays (responsible person, review date) do we adopt from the WPForms example?
Which languages do we translate the entry sections into, and who maintains them?
3. Sensei and Learn WordPress Issues
Discussion:
Since the update to WordPress 7.0, Rade can no longer see or edit the templates on Learn WordPress in the Site Editor. Requests to the 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. team have so far gone unanswered. Rico wants to understand why it keeps happening that the lesson order inside a learning path gets mixed up. Specifically, he wants to know what triggers it, how to prevent it, and how a repair looks if it happens anyway. Without that knowledge, no one wants to work with Sensei, which cannot be in the team’s interest. A direct contact with Sensei developers may be useful. The participants agreed that Sensei has been repeatedly problematic, but a migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is not realistic in the short term.
For the long-term maintenance of the extensive content on Learn WordPress, it is also essential to define the classification of lessons cleanly, for example through a field for the applicable WordPress version. Otherwise, the team will one day face a content base that is fully outdated and could only be deleted. This topic therefore has high priority.
Outcome:
Bug reports are collected and escalated to the Meta team.
A direct contact with Sensei developers will be sought, focusing on triggers, prevention, and repair of the lesson order issue.
Classification fields for lessons (for example WordPress version) will be defined and introduced with high priority.
Caching and Sensei issues will be addressed together with the Meta team.
Open questions:
Who from the Sensei team can contribute to the root cause analysis?
Which fields do we need at a minimum for the classification of lessons?
4. Onboarding and Guide Program
Discussion:
Huzaifa observed that 30 to 40 people attend the weekly Slack meetings, but many of them do not contribute actively. Rico noted that this impression may not be entirely accurate, because many activities of contributors are not immediately visible. They happen in 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/, in regional groups, and in other places. At the same time, there are surely people who only attend the Tuesday meeting and otherwise find no connection. To improve exactly this, the Guide or Mentor Program should be reactivated, so that no contributors are left who would like to do something but do not know what.
Outcome:
Reactivate the Guide or Mentor Program and promote it in the Slack channel and during onboarding.
Clear entry path on the handbook landing page.
Open questions:
Who takes care of reactivating the Guide or Mentor Program?
How are regional groups connected to the team?
5. Badge System Reform
Discussion:
The participants discussed the fundamental problem of the badge system. Badge hunters take up noticeable team time because they sign up for roles without bringing the basics along, and after receiving the badge, they are no longer active. Since this cannot be solved at the global level, the Training Team should develop its own pragmatic approach. This way, we avoid losing more time both through badge hunters themselves and through endless discussions about the badge system.
Outcome:
Collect concrete measures that the Training Team can implement on its own, without the Make team.
Communicate clearly to the whole team, with responsibilities and a timeline for the implementation.
Set up a review of the improvements in one year.
Open questions:
Where do we collect the suggestions?
Who takes care of turning them into a clear action plan?
6. Help Scout and Zoom Access for TT-Admins
Discussion:
The Zoom access was not available at the start of the session, because verification runs through Help Scout, and Help Scout access is only open to Team Reps. Muhibul explained that the Meta team has declined to extend the access, because the account also holds sensitive inboxes from other teams. Rade proposed a workaround: export the Help Scout tickets as a CSV, review them in the TT-Admins pool, and transfer only the relevant ones into GitHub issues. Rico pointed out that in his company a single Zoom account is shared with a passkey among ten people.
Outcome:
CSV export as an interim solution, with manual triage by TT-Admins.
In the medium term, talk with the Meta team about a leaner workflow.
The Zoom link will from now on be documented in the GitHub issue.
Open questions:
Who sets up the CSV export workflow?
How is responsibility for the Zoom account handled in the interim?
7. 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
Discussion:
A specific note-taker incident led to the proposal of a mandatory “Block Editor Basics” workshop. Sumit takes over the concept. Vasant complements it with a screencast tutorial for recurring TT tasks.
Outcome:
Sumit hosts the live workshop, records it, and publishes it on Learn WordPress.
Vasant creates a screencast tutorial.
Both formats are anchored in onboarding as a mandatory step before taking on the note-taker role.
Open questions:
Who handles the editing of the recordings?
Where do we publish the workshop, and how do we communicate the “mandatory workshop”?
8. Meeting Organization and Next Meeting
Discussion:
Starting with the next meeting, Sumit will take over the Zoom link preparation through the Learn account and document it in the GitHub issue. The moderator informs the Slack channel the day before the session and one hour before the start, and publishes the main topic in advance.
We all agreed that the Office Hours meeting must not turn into a Coffee Hours meeting, even though there is a clear need for social exchange. An Office Hours meeting needs detailed preparation: the tasks from the previous meeting are reviewed, and clear agenda items for the current meeting are set. Both are communicated in advance, so that participants can prepare and the meeting runs efficiently. The meeting concept serves as the reference.
Vasant proposed that the tasks decided at the meeting be communicated to everyone afterwards, with an invitation for several people to sign up per task and work on it together.
Outcome:
Sumit hosts the next meeting and provides the Zoom link.
The reminder routine becomes binding (day before and one hour before).
Meeting flow follows the published concept; adjustments are documented in the handbook.
After the meeting, an issue list is created with one issue per task, where people can sign up to work on it.
Next meeting: Saturday, June 27, 2026, 14:00 UTC.
Open questions:
Who takes notes on June 27?
Which tasks go into the issue list?
Decisions
#
Decision
Consensus?
1
The 2026 goals will be consolidated from two working documents: a first draft by Sumit and a revised version by Rico. All TT-Admins comment on both by June 27
Yes
2
Three prioritized main goals will then be published as a blog post on Make WordPress Training
Yes
3
A separate TT-Admins meeting after the Tuesday Slack meeting
Yes
4
Sumit takes over the Zoom link generation through the Learn account and documents it in the GitHub issue
Yes
5
The Block Editor workshop becomes mandatory before the note-taker role
Yes
6
Vasant additionally creates a screencast tutorial for the note takers
Yes
7
After each meeting, an issue list is created with one issue per task; contributors sign up there themselves
Yes
8
The moderator follows the defined meeting concept; adjustments are made immediately and documented in the handbook
Yes
9
A “Last Reviewed” field will be introduced in the handbook, instead of “first published.”
Yes
10
Next Office Hours meeting on June 27, 2026, 14:00 UTC, moderation by @sumitsingh
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
Date: April 18, 2026 Time: 14:00–15:00 UTC Platform: Zoom Recording: Not recorded Moderator: Rico F. Lüthi (@rfluethi) Note-Taker: Rico F. Lüthi (@rfluethi)
This was the first meeting of the Training Team’s new Office Hours format. The format replaces the previous Coffee Hours, which generated more than 90 ideas over roughly eight sessions but resulted in very little concrete follow-through. The Office Hours are designed to close that gap: informal in tone, but clearly outcome-oriented, with actionable next steps from meeting to meeting.
As outlined in the proposal, the format initially runs as a three-month pilot phase. The goal of this kick-off was to establish the basic structure, success criteria and organizational approach together, so that future sessions can focus directly on substantive work.
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
The introductions highlighted the geographic and biographical breadth of the team. Paths into the WordPress community vary widely: from a developer whose first contribution grew out of frustration, to a manager of local language projects, to community supporters and digital skill facilitators. @sonaliprajapati shared her experience from the Indian WordPress community. This diversity is relevant to the direction of the Office Hours because it shows the range of needs and perspectives that contributors bring to the format.
Topics Discussed
1. 60-Minute Structure
Discussion:
On the question of meeting duration, @rjekic noted that while 60 minutes should be set as the frame, many meetings would likely end earlier in practice. This point mattered to the group because the format is intended to be distinct from the previous Coffee Hours, which were enjoyable but not outcome-oriented.
@sumitsingh argued that the real value of the Office Hours lies in the live connection. In SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, international contributors do not get to know each other personally, which is essential for building trust and long-term commitment to the team. This argument was a key factor in the group’s conscious decision against a purely asynchronous format.
There was consensus that perfect English should not be a prerequisite. Open exchange with the broader community takes priority.
Outcome:
Duration: 60 minutes, flexible downward
Character: informal in tone, outcome-oriented in output
Linguistic openness as a deliberate principle
Open questions: None.
2. Recurring Agenda Items
Discussion:
The group developed an agenda structure that gives each meeting a reliable framework without losing the informal character. A central point of discussion was the advance announcement of the main topic: this was introduced specifically so that non-native English speakers can prepare both in terms of content and language. This addresses a real barrier for international contributors.
It was also agreed that moderation and note-taking will rotate among team members in order to distribute responsibility. In addition, at least one team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. should be present at each meeting to ensure overall coordination.
Outcome:
The following items will be a fixed part of every session:
Welcome & onboarding
Brief introductions
Topic presentation (5–10 minutes) on the main topic
Open discussion
Review of open action items from previous meetings
Definition of next steps including responsible persons
Setting the date, moderator and note-taker for the next meeting
Open questions: None.
3. Onboarding New Contributors
Discussion:
A major focus of the discussion was how to prevent new contributors from dropping off after their initial engagement — particularly after WordCamps. The team’s experience shows that motivation is often high at first but fades quickly without concrete, low-barrier tasks. Thumbnail creation and translations were cited as examples of suitable entry-level tasks.
This observation led to a broader point: the Training Team needs specialized groups so that both new and existing contributors can get involved and achieve results quickly. Three types were discussed: the existing Guides, topic-specific groups for developing new learning paths, and regional groups for localized learning resources.
Coordination of these groups is to run through the TT-Admins and the Office Hours. An important point raised by the group: transparency is essential so that it remains clear to everyone why particular decisions were made. Without this transparency, the group concluded, the team risks losing touch with the broader community.
Outcome:
Low-barrier entry tasks (thumbnails, translations) as first points of contact
Development of specialized groups: Guides, topic groups, regional groups
Active promotion of these groups within the Training Team
Transparency in coordination as a coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. principle
Open questions:
How will the specialized groups be promoted and coordinated in practice?
4. Success Criteria for the Pilot Phase
Discussion:
@andrewssanya proposed an iterative, agile approach: each meeting identifies concrete problems, and progress on their resolution is reviewed in the following meeting. The group adopted this proposal and expanded it into a definition of success criteria.
The decisive point in the discussion was the distinction from pure attendance numbers. The group agreed that even a small but active group justifies the format, as long as topics are demonstrably turned into issues and worked on. This definition is important for the later evaluation of the pilot phase and protects the format from being prematurely judged by quantitative metrics alone.
Outcome:
Success = combination of attendance and concrete project progress
Attendance numbers alone are not a criterion
Progress review from meeting to meeting
Open questions: None.
5. Organization via 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/
Discussion:
The decision to organize via GitHub was unanimous, since the Training Team already works with it and no additional tooling barrier should be introduced. Topic proposals are collected as issues at wpt-office-hours / issues; the respective moderator selects the agenda from these.
@rfluethi encouraged all participants to actively contribute to shaping the repository. Specifically, it was agreed that @andrewssanya and @rfluethi will review the existing repository templates and the Training Team’s issue templates for potential improvements.
After the pilot phase, the repository is to be transferred into the official Training Team structures. This temporary solution was chosen deliberately to allow the pilot to start quickly without waiting for formal processes.
Transfer to the official Training Team repository after the pilot phase
Open questions: None.
6. Tracking Open Action Items
Discussion:
For tracking action items, the group deliberately opted to use the Training Team’s existing issue system rather than building a parallel tracking structure in the pilot repository. The rationale: Office Hours tasks should not exist in isolation alongside the rest of the team’s work, but be part of it. To still distinguish them from the broader backlog, a dedicated label will be introduced.
A dedicated Office Hours issue label will be introduced
Yes
4
Moderation and note-taking rotate among team members
Yes
5
At least one team rep should be present at each meeting to ensure overall coordination
Yes
6
Pilot phase success = combination of attendance and project progress
Yes
7
Next Office Hours on May 23, 2026, 14:00 UTC, moderation: @rjekic
Yes
Rationale for Decision 4 (Rotation): Rotation was chosen deliberately as a countermodel to fixed moderation, in order to distribute responsibility and give different team members the opportunity to actively shape the format.
Rationale for Decision 6 (Success criteria): The proposal came from @andrewssanya as part of an iterative, agile approach. The group explicitly followed the reasoning that even small, active groups justify the format, as long as topics are demonstrably turned into issues.
Publish call for Training Table lead at 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
Follow up with the 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. Team regarding the TT-Admins Slack channel
Additional topics discussed during the meeting that led to action items but are not listed as separate topics above: establishing an admin roster (TT-Admins), scheduling preferences via poll, Training Team representation at the WordCamp Europe Contributor DayContributor DayContributor 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://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, and setting up a dedicated TT-Admins Slack channel.
