Elaborate what the monthly assignments status check entails

Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
This commit is contained in:
John Ericson 2024-01-22 08:38:52 -05:00 committed by GitHub
parent e94a96893f
commit 0bcdb4f5f0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -44,7 +44,10 @@ The team meets twice a week:
1. Triage issues and pull requests from the [No Status](#no-status) column (30 min) 1. Triage issues and pull requests from the [No Status](#no-status) column (30 min)
2. Discuss issues and pull requests from the [To discuss](#to-discuss) column (30 min). 2. Discuss issues and pull requests from the [To discuss](#to-discuss) column (30 min).
Once a month, this slot is used to check the [Assigned](#assigned) column to make sure that nothing bitrots in it. Once a month, each team member checks the [Assigned](#assigned) column for prs/issues assigned to them, to either
- unblock it by providing input
- mark it as draft if it is blocked on the contributor
- escalate it back to the team by moving it to To discuss, and leaving a comment as to why the issue needs to be discussed again.
- Work meeting: [Mondays 13:00-15:00 CET](https://calendar.google.com/calendar/event?eid=NTM1MG1wNGJnOGpmOTZhYms3bTB1bnY5cWxfMjAyMjExMjFUMTIwMDAwWiBiOW81MmZvYnFqYWs4b3E4bGZraGczdDBxZ0Bn) - Work meeting: [Mondays 13:00-15:00 CET](https://calendar.google.com/calendar/event?eid=NTM1MG1wNGJnOGpmOTZhYms3bTB1bnY5cWxfMjAyMjExMjFUMTIwMDAwWiBiOW81MmZvYnFqYWs4b3E4bGZraGczdDBxZ0Bn)