Dev-squad update: Triage sessions planning

This post summarises the discussions that followed the dev-squad proposal.

After the initial proposal post, the following Training Faculty Admins indicated their interest in taking part in dev-squad:

  1. @digitalchild
  2. @courane01
  3. @meaganhanes
  4. @amitpatelmd
  5. @alexstine
  6. @psykro

Triage sessions

With @digitalchild, @amitpatelmd, and @psykro all on similar APAC-friendly timezones, and @courane01, @meaganhanes, and @alexstine on similar AMER-friendly timezones, it was agreed that dev-squad triage sessions would alternate weekly:

  1. APAC dev-squad sessions will be held on Tuesdays at 06:00 UTC
  2. AMER dev-squad sessions will be held on Tuesdays at 22:00 UTC

The first dev-squad sessions will be held in the APAC timeslot on Tuesday, 14 March 2023 at 06:00 UTC.

The following week the dev-squad sessions will be held in the AMER timeslot on Tuesday, 21 March 2023 at 22:00 UTC.

From there on, the sessions will alternate between APAC and AMER timeslots.

All dev-squad meetings will be held in the #meta-learn channel in the WordPress Slack instance.


To start, the sessions will be 30 minutes in length. However, this can be extended on a case-by-case basis if needed.

Proposed agenda

Below is a proposed agenda for each triage session

  1. A short introduction and welcome
  2. Review any open PRs
  3. Triage any open bugs

This a reminder that the goal of dev-squad triage sessions is to help move PRs and issues forward, not to physically review/verify them. Triage sessions can also focus on either PRs or bugs, and do not have to cover both in a single session.