Test chat moderator guide by juanmaguitar · Pull Request #108 · WordPress/test-handbook

juanmaguitar · 2026-01-23T11:55:01Z

Partially addresses #11

This PR adds a comprehensive moderator guide for running <test-chat> meetings, based on actual Test Team Chat
sessions from January 14 and January 22, 2026.

It only addresses the <test-chat> portion of issue #11. Guidelines for <test-triage> meetings remain to be documented in a future PR.

Changes

New Documentation:

Added team-reps/test-chat-moderator-guide.md with detailed instructions for moderators

Restructuring:

Converted team-reps.md to a directory structure (team-reps/index.md)
Added the moderator guide as a child page under Team Reps
Updated bin/handbook-manifest.json to reflect the new structure
Added reference link in team-reps duties section

What's Included

The Test Chat Moderator Guide covers:

Pre-meeting preparation checklist
Step-by-step meeting structure with 8 sections:
1. Opening/Welcome
2. Attendance Check
3. Share Agenda
4. Meeting Notes Announcement
5. Test Team Discussions
6. Open Floor
7. Announcements (Ecosystem, Test Team, Call for Testing)
8. Closing
Example phrases extracted from actual meetings for each section
Moderator tips for facilitating discussions, GitHub integration, and time management
Common situations with suggested responses
Post-meeting tasks checklist
Quick reference for meeting flow with timing
Resources and links section
Full example opening sequence

- Introduced a new `index.md` for the Test Team Reps, detailing roles and responsibilities. - Added a new `test-chat-moderator-guide.md` to assist moderators in running Test Team Chat meetings. - Updated the `handbook-manifest.json` to reflect the new structure and links for the Test Team Reps and the Chat Moderator Guide.

SirLouen

The structure is good, I only have two concerns:

Changing the code blocks for quote blocks to facilitate reading in the blog
I'm not sure if we need to add the "suggestions". I would prefer that each organizer has his/her own style for leading the meeting. A simpler template with the basic elements, a maybe some key suggestions like these:

Facilitate discussion:

Let participants share their thoughts
Ask clarifying questions when needed
Summarize key points
Acknowledge contributions

But not adding those elements:

Understood! 👍

Personally, I like to see each personality in action. And some users and certain cultures, like certain areas of India, feel too intimidated by clear instructions to inhibit themselves when they are in place.

SirLouen · 2026-01-23T12:31:04Z

team-reps/test-chat-moderator-guide.md

+```
+_Or:_
+```
+@aquí We are starting now today's <test-chat>


SirLouen · 2026-01-23T12:31:12Z

team-reps/test-chat-moderator-guide.md

+## Example Full Opening Sequence
+
+```
+[14:02] Moderator: @aquí Hey everyone! Please join us in #core-test for this week's Test Team chat.


SirLouen · 2026-01-23T12:31:18Z

team-reps/test-chat-moderator-guide.md

+
+**Announce meeting start:**
+```
+@aquí Hey everyone! Please join us in #core-test for this week's Test Team chat.


SirLouen · 2026-01-23T12:32:19Z

team-reps/test-chat-moderator-guide.md

+### 2. Attendance Check
+
+**Request attendance:**
+```


Instead of code blocks, I would use quotes with > because they respect the horizontal overflow and makes easier to read.

Also code blocks in the blog don't have the "copy" button (contrarily to Github), so the code block dont provide that easily copy-pasteability value

SirLouen · 2026-01-23T12:35:30Z

team-reps/test-chat-moderator-guide.md

+
+**Link to agenda:**
+```
+Today's chat agenda can be found [here](LINK_TO_AGENDA). Please take a look.


If you add here a quote, beware because it might be interpreted as a link.

SirLouen · 2026-01-23T12:52:53Z

team-reps/test-chat-moderator-guide.md

+- Core Reports: https://make.wordpress.org/core/reports/
+
+### Regular Reports
+- Week in Test: Published weekly at make.wordpress.org/test


We are changing this in February to one pe month, Month in Test

SirLouen · 2026-01-23T12:53:04Z

team-reps/test-chat-moderator-guide.md

+
+### Regular Reports
+- Week in Test: Published weekly at make.wordpress.org/test
+- Test Team Update: Bi-weekly metrics report


These are changing to one per week

SirLouen · 2026-01-23T12:54:42Z

team-reps/test-chat-moderator-guide.md

+- List attendees (from thread)
+- Prepare meeting summary for publication
+
+### Common Situations


This snippets could be enough for reference, but I would not include those between the meeting

- Updated formatting for meeting announcements, attendance requests, and agenda sharing to improve readability. - Enhanced instructions for async participation and discussion facilitation. - Streamlined sections for announcements and open floor discussions to ensure a smoother flow during meetings.

juanmaguitar · 2026-01-29T18:02:40Z

Thanks for the feedback, @SirLouen! I've addressed your concerns:

Code blocks → Quote blocks
All example text now uses quote block formatting (>) instead of code blocks for better blog readability.
Simplified to allow moderator personality
I've removed the overly specific example phrases (like "Understood! 👍") and simplified the guide to focus on:
- Basic meeting structure and timing
- General facilitation principles (let participants share, ask clarifying questions, summarize key points, acknowledge contributions)
- Common situations with general guidance instead of prescriptive phrases

The guide now provides a framework while leaving room for each moderator to develop their own style and voice.

- Changed "Week in Test" to "Month in Test" for monthly publication. - Updated "Test Team Update" from bi-weekly to weekly metrics report.

SirLouen · 2026-01-30T17:57:15Z

team-reps/test-chat-moderator-guide.md

+- Gutenberg Releases: Bi-weekly release announcements
+
+### Testing Resources
+- Core Needs Testing: https://core.trac.wordpress.org/report/69


I think that these are redundant with the ones in the top

SirLouen

Some extra

SirLouen · 2026-01-30T18:00:41Z

team-reps/test-chat-moderator-guide.md

+### 1. Opening / Welcome (Start Time)
+
+**Announce meeting start:**
+> @here Hey everyone! Please join us in #core-test for this week's Test Team chat.


Change this two @here references to /here

SirLouen · 2026-01-30T18:01:00Z

team-reps/test-chat-moderator-guide.md

+
+## Quick Reference - Meeting Flow
+
+> 1. Opening & Welcome (2-3 min)


I think this could be a regular numbered list without quotes?

SirLouen · 2026-01-30T18:02:33Z

team-reps/test-chat-moderator-guide.md

+> - [Help Test WordPress X.X](LINK)
+> - We have [Patch Testing Issues](LINK) that need testing
+
+**Standard links:**


We need to update these with the new reports

@here

- Corrected the notification format from @here to /here for meeting announcements. - Updated links for Core Needs Testing and removed outdated Core Patch Testing link. - Improved formatting for the meeting flow section to enhance readability.

juanmaguitar · 2026-02-03T19:16:06Z

@SirLouen I have addressed your feedback. Ready for review again.

SirLouen · 2026-02-06T01:12:11Z

team-reps/test-chat-moderator-guide.md

+> - We have [Patch Testing Issues](LINK) that need testing
+
+**Standard links:**
+- Core Needs Testing: https://core.trac.wordpress.org/report/69


@juanmaguitar I didn't notice before, but if you want to set a specific report instead of a query, then go with this https://core.trac.wordpress.org/tickets/needs-testing

That report is slated to be deprecated and removed

SirLouen · 2026-02-06T01:14:03Z

team-reps/test-chat-moderator-guide.md

+3. Share Agenda (1 min)
+4. Meeting Notes Declaration (1 min)
+5. Test Team Discussions (30-40 min)
+   - Multiple agenda items


According to the MD standard, we cannot mix unordered lists with ordered lists. So here it must be 1., 2. again

huzaifaalmesbah · 2026-02-06T04:41:02Z

team-reps/test-chat-moderator-guide.md

+- https://make.wordpress.org/test/2026/01/21/team-chat-agenda-22nd-january-2026/
+- https://make.wordpress.org/test/2026/01/14/team-chat-agenda-14th-january-2026/
+
+### 4. Meeting Notes Announcement


I’d like to suggest adding a small “Upcoming 4-Week Schedule” section within the Meeting Notes Announcement area.

Something like this:

📅 **Upcoming 4-Week Schedule** * 12 February 2026 – Facilitator: @username1 | Note-taker: @username2 * 26 February 2026 – Facilitator: @username3 | Note-taker: @username4 * 12 March 2026 – Facilitator: (Open) | Note-taker: (Open) * 26 March 2026 – Facilitator: (Open) | Note-taker: (Open) 🙌 If you'd like to volunteer for any open slot, please reply in the thread.

Why this would be helpful:

Provides clear visibility of upcoming facilitators and note-takers

Encourages contributors to volunteer ahead of time instead of during the meeting

Helps moderators prepare better in advance

Makes the process more structured and predictable

Reduces last-minute coordination or confusion

Creates more opportunities for new contributors to get involved

I believe this small addition could improve planning, transparency, and engagement without adding much overhead.

@SirLouen @juanmaguitar what do you think about adding this to the Upcoming 4-Week Schedule? Would love to hear your thoughts 🙂

Great suggestion! Added

huzaifaalmesbah · 2026-02-06T04:46:24Z

team-reps/test-chat-moderator-guide.md

+> **Meeting Notes**
+
+**Identify facilitator:**
+> Today's session facilitator and note-taker is **@[YOUR_USERNAME]**


We can write it like this:

Today's session facilitator and note-taker is @[YOUR_USERNAME]

Or, if the roles are handled by different people:

Today's session facilitator is @[FACILITATOR_USERNAME] and the note-taker is @[NOTE_TAKER_USERNAME]

This keeps it flexible and clear depending on whether one or two contributors are taking the roles.

Thanks for the suggestion @huzaifaalmesbah! Added

Leave it open

…ing details - Added optional section for upcoming 4-week schedule with facilitator and note-taker assignments. - Clarified facilitator and note-taker roles when handled by different individuals. - Improved formatting for meeting flow and agenda items for better readability.

@here

…o /here - Updated instances of @here to /here in the guide to ensure accurate notification instructions for meeting announcements.

juanmaguitar · 2026-02-09T11:52:52Z

@SirLouen @huzaifaalmesbah feedback addressed.
Ready for review again!

huzaifaalmesbah

LGTM!

juanmaguitar added 2 commits January 23, 2026 11:45

Remove outdated versioning information from Test Chat Moderator Guide

0b473f3

juanmaguitar mentioned this pull request Jan 23, 2026

Add team rep guidelines for running weekly meetings #11

Open

juanmaguitar requested a review from SirLouen January 23, 2026 11:57

SirLouen previously requested changes Jan 23, 2026

View reviewed changes

SirLouen assigned juanmaguitar Jan 23, 2026

SirLouen added Create Discuss Needs: 1 Review labels Jan 23, 2026

juanmaguitar requested a review from SirLouen January 29, 2026 18:02

Update Test Chat Moderator Guide to reflect reporting frequency changes

3407060

- Changed "Week in Test" to "Month in Test" for monthly publication. - Updated "Test Team Update" from bi-weekly to weekly metrics report.

SirLouen reviewed Jan 30, 2026

View reviewed changes

juanmaguitar requested a review from SirLouen February 3, 2026 19:15

SirLouen reviewed Feb 6, 2026

View reviewed changes

SirLouen requested review from Successfulsebunya, huzaifaalmesbah and nikunj8866 February 6, 2026 01:16

huzaifaalmesbah reviewed Feb 6, 2026

View reviewed changes

juanmaguitar requested review from SirLouen and huzaifaalmesbah February 9, 2026 11:50

Correct notification format in Test Chat Moderator Guide from @here t…

ddb471a

…o /here - Updated instances of @here to /here in the guide to ensure accurate notification instructions for meeting announcements.

huzaifaalmesbah approved these changes Feb 9, 2026

View reviewed changes

SirLouen approved these changes Feb 10, 2026

View reviewed changes

SirLouen merged commit ef1c7db into WordPress:trunk Feb 10, 2026


		## Quick Reference - Meeting Flow

		> 1. Opening & Welcome (2-3 min)

Conversation

juanmaguitar commented Jan 23, 2026

Changes

What's Included

Uh oh!

SirLouen left a comment

Choose a reason for hiding this comment

Facilitate discussion:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juanmaguitar commented Jan 29, 2026

Uh oh!

SirLouen Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

SirLouen left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juanmaguitar commented Feb 3, 2026

Uh oh!

SirLouen Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

huzaifaalmesbah Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Why this would be helpful:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juanmaguitar commented Feb 9, 2026

Uh oh!

huzaifaalmesbah left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

SirLouen Jan 30, 2026 •

edited

Loading

SirLouen Feb 6, 2026 •

edited

Loading

huzaifaalmesbah Feb 6, 2026 •

edited

Loading