From 46feb8a0f1d746b0f9bbf8f35a5d40276ade8b4c Mon Sep 17 00:00:00 2001 From: Victor Lin <13424970+victorlin@users.noreply.github.com> Date: Fri, 26 Apr 2024 10:41:54 -0700 Subject: [PATCH] Remove reference to "biweekly issue triage meeting" We don't have these anymore. --- src/reference/governance.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/reference/governance.rst b/src/reference/governance.rst index 11a6d2ea..bc07c56c 100644 --- a/src/reference/governance.rst +++ b/src/reference/governance.rst @@ -49,7 +49,7 @@ Seek consensus from the Core Team. - Allow enough time for team members to review and register feedback before finalizing a decision. - Summarize the consensus decision publicly (e.g., on a GitHub PR or issue). - Alert the team that a consensus has been reached on major changes (e.g., via Slack or GitHub). - - For critical, urgent, or stalled decisions, arrange a synchronous meeting to review available options and attempt to reach a decision during the meeting (e.g., biweekly Nextstrain meeting, biweekly issue triage meeting, or a special topic meeting). + - For critical, urgent, or stalled decisions, arrange a synchronous meeting to review available options and attempt to reach a decision during the meeting (e.g., biweekly Nextstrain meeting or a special topic meeting). - Minimally, seek consensus with at least one other Core Team member who is familiar with the context. Hold an informal vote to gauge opinion on difficult or subjective decisions (e.g., naming).