From 0bcdb4f5f0830261ecbff1cbc805b215cac1abae Mon Sep 17 00:00:00 2001 From: John Ericson Date: Mon, 22 Jan 2024 08:38:52 -0500 Subject: [PATCH] Elaborate what the monthly assignments status check entails Co-authored-by: Robert Hensing --- maintainers/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/maintainers/README.md b/maintainers/README.md index 585e2b50a..fa321c7c0 100644 --- a/maintainers/README.md +++ b/maintainers/README.md @@ -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) 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)