Dev-squad update: Triage sessions planning

Welcome

The WordPress Training Team helps people learn to use, extend, and contribute to WordPress through learn.wordpress.org.

Are you new to the team?

Getting Started – Join the team through this self-guided onboarding program

Current Focus Areas – What we’re currently focusing on

Already onboarded and ready to get involved?

See How we use GitHub to get started on one of our 6 project boards

Meetings (Calendar)

You can join these meetings from the #training Slack channel:

Weekly meeting: Thursdays 00:00 UTC

Dev-squad GitHubGitHub GitHub 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 be the repository owner. https://github.com/ triage: Thursdays 07:00 UTC

See Meeting Details for more information.

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:

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:

APAC dev-squad sessions will be held on Tuesdays at 06:00 UTC
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.

Duration

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

A short introduction and welcome
Review any open PRs
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.

Benjamin Evans 12:33 am on March 11, 2023

This all looks great! Once you’ve run a couple of sessions, please let us (team reps) know how we can best help elevate your work in the team. For example, would a slot to report your work in the weekly meetings be effective? Or perhaps a monthly update of how many issues were triaged?

No need to answer now. Please give it some thought 😃
Jonathan Bossenger 1:59 pm on March 17, 2023

The first triage session took place as planned on Tuesday, with myself and @alexstine attending. The meeting lasted for 30 minutes, and during that time we focused on open Pull Requests.

We triaged 4 open PRs, and either added necessary labels, or tagged the PR creator to ask them to either refresh the PR, or fix any conflicts that exist.
- Amit Patel 7:18 am on March 21, 2023
  
  I missed the previous session since I was in the company annual meet. Can anybody let me know what will the time of the triage session for APAC time zone?
  - Jonathan Bossenger 7:27 am on March 22, 2023
    
    @amitpatelmd I’m going to work on getting these meetings added to the meeting calender, so we can see them in our own timezone’s there.
    - Benjamin Evans 4:21 am on March 23, 2023
      
      @psykro I’ve added these to the meeting calendar for you. Please confirm they’re correct ☺️
      - Jonathan Bossenger 7:40 pm on March 24, 2023
        
        Thanks @bsanevans that looks correct to me.
Jonathan Bossenger 7:15 am on May 30, 2023

Hi folks. I’m circling back here with an update and a change suggestion.

Since this post, we’ve had 2 APAC dev-squad triage sessions and no AMER sessions.

I have been running the APAC sessions, but I am finding the time hard to stick to. I was also away for a couple of the scheduled sessions due to local public holidays, and conferences, and no one was available to host while I was away.

Therefore my suggestion is to move the APAC triage sessions to every Thursday morning at 7:00 am UTC. This is a time that I can generally safely commit to, so unless I am away for a specific reason, I can be sure to be around to run these sessions every week. If the proposed time does not suit everyone in the APAC timezone, please feel free to suggest an alternative time, and I will try to accommodate this.

If any dev-squad member in the AMER timezone would also like to host a session, please comment on this post, with your suggested day/time. Otherwise, we’ll just continue with the APAC sessions for now.
- Jonathan Bossenger 7:48 am on June 14, 2023
  
  It seems that no one has a problem with the new suggested time, therefore dev-squad meetings will move to 07:00 UTC on Thursdays, starting next Thursday, 22 June 2023.
  
  @bsanevans could I ask you to update the meeting time in the calendar?
  - Benjamin Evans 5:58 am on June 15, 2023
    
    https://make.wordpress.org/meetings/#training is now updated to “weekly on Thursdays at 7UTC”.
    - Jonathan Bossenger 7:29 am on June 15, 2023
      
      Thank you!

Welcome

Meetings (Calendar)

Triage sessions

Duration

Proposed agenda

Share this: