From 3fd0549315b870935476f5e0f816a0906e7dd735 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 24 Apr 2026 23:19:25 +0800 Subject: [PATCH] docs(contributing): define allowed comments on Goal issues --- docs/CONTRIBUTING.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index b198451..59ec7ce 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -57,6 +57,19 @@ As soon as you get involved, you must: Each Goal description must include Specs (a Google Document with commenting permissions) and an ETA. +Comments on a Goal issue are only appropriate for: + +- **ETA update** — when the delivery date changes +- **Priority change** — when the Goal is deprioritised or elevated relative + to other Goals (e.g. "pausing this Goal, focusing on X instead") +- **Spec review request** — asking someone to review the Spec document or + address comments left in it + +Everything else — questions, blockers, progress updates, PR links — does not +belong in the Goal issue. Blockers go as `Problem:` sub-issues. Questions go +in the Spec document. Progress is implied by the absence of open Problems and +a valid ETA. + > [!NOTE] > A Goal is represented as a GitHub issue in the relevant repository and has the > following naming pattern: `Goal: [statement]`.