Earlier this year we launched a new initiative called dev-squad. The initial goal of dev-squad was to hold weekly, 30-minute triage sessions to help move PRs and newly opened bugs forward. These triage sessions can focus on either PRs or bugs and do not have to cover both in a single session.
The initial sessions were planned to be held on Tuesdays at 06:00 UTC and Tuesdays at 22:00 UTC, to allow members across different timezones to run triage sessions. After testing these times for about 6 weeks, the meeting time was moved to Thursdays at 07:00 UTC.
Since then, we have managed to run several successful triage sessions, clearing the PR list and triaging any new bugs. However, there are currently some problems.
- We don’t have any official documentation so that anyone could potentially run these sessions.
- The weekly sessions are currently hosted by one person, and this is not sustainable.
- Currently, membership is limited to Training Faculty Admin members only, which limits the number of participants.
- We do not actively encourage new members to take part in or run sessions.
Therefore, I would like to propose that we set the following short-term goals for dev-squad, to grow its membership, and make it more sustainable and successful.
Timeline: by Friday 29 December 2023
Goals:
- Document dev-squad triage sessions
- General format
- Process of triaging pull requests
- Process of triaging new bugs
- Adding triage updates to weekly training team meetings
- Invite other training team contributors to participate in triage sessions
- Open dev-squad membership to all training team members
- Add interested participants to GitHub with the relevant permissions to label issues
- Work towards having more than one triage session host
- Set up a rotation of session hosts
- Plan the host rotation for the first 4 sessions of 2024
Are you interested in joining dev-squad, to help keep the new PR and bug issue list clear? Comment on this post and let us know how you would like to help or join the next dev-squad triage session in the #meta-learn channel on Thursday at 07:00 UTC.