Skip to content

Revise Test Team Rep duties and qualifications - #183

Merged
Successfulsebunya merged 3 commits into
trunkfrom
Successfulsebunya-patch-1
Oct 2, 2026
Merged

Successfulsebunya merged 3 commits into
trunkfrom
Successfulsebunya-patch-1

Conversation

@Successfulsebunya

Copy link
Copy Markdown
Member

Updated Test Team Rep duties and qualifications for clarity and consistency.

Updated Test Team Rep duties and qualifications for clarity and consistency.
@github-actions

github-actions Bot commented Aug 14, 2026 •

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Successfulsebunya <mosescursor@git.wordpress.org>
Co-authored-by: nikunj8866 <nikunj8866@git.wordpress.org>
Co-authored-by: ironprogrammer <ironprogrammer@git.wordpress.org>
Co-authored-by: SirLouen <sirlouen@git.wordpress.org>
Co-authored-by: 3kori <r1k0@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@Successfulsebunya
Successfulsebunya requested review from ironprogrammer and nikunj8866 and a lite review from Copilot and removed request for ironprogrammer and nikunj8866 August 14, 2026 21:08

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the Test Team Rep duty list to reflect current cadence, activities, and guidance links.

Changes:

  • Adjusts content cadence (bi-weekly updates, monthly recap) and replaces/updates links to examples.
  • Updates session responsibilities (Patch Testing naming, adds Voice Chat cadence).
  • Clarifies shared responsibility language for the two reps.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread team-reps/index.md
- Write bi-weekly [Test Team Update](https://make.wordpress.org/updates/tag/test/) posts and publish them on the [Team Updates](https://make.wordpress.org/updates/) page.
- Write monthly [Month in Test](https://make.wordpress.org/test/category/month-in-test/) posts and publish them on [Make WordPress Test](https://make.wordpress.org/test/).
- Write agendas for bi-weekly `<test-chat>` sessions ([example](https://make.wordpress.org/test/tag/test-chat-agenda/)).
- Run alternating weekly `<test-chat>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1626181220122300)) and `<Patch Testing>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1785423614352719)) sessions in [#core-test](https://wordpress.slack.com/messages/core-test/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't need to use Copilot's wording here, but I do agree that maintaining links to these guide pages is helpful.

Comment thread team-reps/index.md
- Write bi-weekly [Test Team Update](https://make.wordpress.org/updates/tag/test/) posts and publish them on the [Team Updates](https://make.wordpress.org/updates/) page.
- Write monthly [Month in Test](https://make.wordpress.org/test/category/month-in-test/) posts and publish them on [Make WordPress Test](https://make.wordpress.org/test/).
- Write agendas for bi-weekly `<test-chat>` sessions ([example](https://make.wordpress.org/test/tag/test-chat-agenda/)).
- Run alternating weekly `<test-chat>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1626181220122300)) and `<Patch Testing>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1785423614352719)) sessions in [#core-test](https://wordpress.slack.com/messages/core-test/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the header used at the start of each session in Slack has changed, then use whatever the current convention is. It does look inconsistent.

Comment thread team-reps/index.md Outdated
- Write agendas for bi-weekly `<test-chat>` sessions ([example](https://make.wordpress.org/test/tag/test-chat-agenda/)).
- Run alternating weekly `<test-chat>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1626181220122300)) and `<Patch Testing>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1785423614352719)) sessions in [#core-test](https://wordpress.slack.com/messages/core-test/).
- Write `<test-chat>` session recaps and publish them on [Make WordPress Test](https://make.wordpress.org/test/).
- Run Voice Chat sessions in [#core-test](https://wordpress.slack.com/archives/C03B0H5J0) every **1st Thursday of the month**.

@nikunj8866 nikunj8866 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ironprogrammer ironprogrammer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for these updates, @Successfulsebunya! I've left a little feedback below. Feel free to accept or discard, whatever the current temperature is in team rep world.

Comment thread team-reps/index.md
Comment thread team-reps/index.md
- Write bi-weekly [Test Team Update](https://make.wordpress.org/updates/tag/test/) posts and publish them on the [Team Updates](https://make.wordpress.org/updates/) page.
- Write monthly [Month in Test](https://make.wordpress.org/test/category/month-in-test/) posts and publish them on [Make WordPress Test](https://make.wordpress.org/test/).
- Write agendas for bi-weekly `<test-chat>` sessions ([example](https://make.wordpress.org/test/tag/test-chat-agenda/)).
- Run alternating weekly `<test-chat>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1626181220122300)) and `<Patch Testing>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1785423614352719)) sessions in [#core-test](https://wordpress.slack.com/messages/core-test/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't need to use Copilot's wording here, but I do agree that maintaining links to these guide pages is helpful.

Comment thread team-reps/index.md
- Write bi-weekly [Test Team Update](https://make.wordpress.org/updates/tag/test/) posts and publish them on the [Team Updates](https://make.wordpress.org/updates/) page.
- Write monthly [Month in Test](https://make.wordpress.org/test/category/month-in-test/) posts and publish them on [Make WordPress Test](https://make.wordpress.org/test/).
- Write agendas for bi-weekly `<test-chat>` sessions ([example](https://make.wordpress.org/test/tag/test-chat-agenda/)).
- Run alternating weekly `<test-chat>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1626181220122300)) and `<Patch Testing>` ([example](https://wordpress.slack.com/archives/C03B0H5J0/p1785423614352719)) sessions in [#core-test](https://wordpress.slack.com/messages/core-test/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the header used at the start of each session in Slack has changed, then use whatever the current convention is. It does look inconsistent.

Comment thread team-reps/index.md Outdated
Comment thread team-reps/index.md Outdated

@SirLouen SirLouen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great protocol @Successfulsebunya

@3kori

3kori commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

After talking about this in today's session. This PR is mostly ready to merge; it just needs a bit of an update, as suggested by the comments.
@Successfulsebunya, if you make the changes, we could have this merged ASAP!

Successfulsebunya and others added 2 commits October 2, 2026 07:31
Co-authored-by: Brian Alexander <824344+ironprogrammer@users.noreply.github.com>
Co-authored-by: Brian Alexander <824344+ironprogrammer@users.noreply.github.com>
@Successfulsebunya
Successfulsebunya merged commit 4512bf9 into trunk Oct 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants