From 5b3c7f3c5e7d1c077c3daa9879349e23545ebba1 Mon Sep 17 00:00:00 2001 From: Bogdan Drutu Date: Thu, 11 Jan 2024 06:50:28 -0800 Subject: [PATCH] Clarify that maintainer should escalate approvers as well (#1840) --- community-membership.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/community-membership.md b/community-membership.md index 333ba4b7c..93ae0703a 100644 --- a/community-membership.md +++ b/community-membership.md @@ -212,8 +212,9 @@ The following apply to the subproject for which one would be a maintainer. - Define milestones and releases. - Decides on when PRs are merged to control the release scope. - Mentor and guide approvers, reviewers, and contributors to the subproject. -- Escalate *reviewer* and *maintainer* workflow concerns (i.e. responsiveness, - availability, and general contributor community health) to the TC. +- Escalate *reviewer*, *approver*, *maintainer* and other workflow concerns + (i.e. responsiveness, availability, and general contributor community health) + to the TC. - Ensure continued health of subproject: - Adequate test coverage to confidently release - Tests are passing reliably (i.e. not flaky) and are fixed when they fail