[Feature] Label a first issue, and write down how accepted and declined are decided #596

Closed
opened 2026-07-22 16:18:14 +00:00 by brenno · 1 comment
Owner

Found in the pre-publication contributor-journey review.

Evidence: the repository has ten labels — accepted, bug, declined, docs, duplicate, enhancement, needs-info, privacy, security, triage — and none of them is good first issue or help wanted. Before this review the seven open issues were all large: #518 structural debt, #520 release engineering, #541 sidecars to git, #555, #556, #563, #564. There is no GOVERNANCE.md or MAINTAINERS.md.

Why this matters now: AUTHORS.md:16 invites contributors to "add yourself here in your first pull request" while there is nothing sized for a first pull request to point at. The tracker already has a decision process — triage → accepted | declined | needs-info is visibly in use — but it exists only as label names, so a newcomer cannot tell whether a proposal gets an answer or disappears. For a launch whose stated purpose is involving a wider group of people, that is the gap that decides whether anyone stays.

Proposal: add a good first issue label and tag two or three genuinely small items — this review produced several suitable ones (the placeholder email, the Nieuw tab label, the stale file paths in GIT_STORAGE.md, the committed golden failure artefacts). Then six lines in docs/CONTRIBUTING_GUIDELINES.md under Issue Tracking describing the triage path the labels already encode. No governance document needed for one maintainer.

Found in the pre-publication contributor-journey review. **Evidence:** the repository has ten labels — `accepted, bug, declined, docs, duplicate, enhancement, needs-info, privacy, security, triage` — and none of them is `good first issue` or `help wanted`. Before this review the seven open issues were all large: #518 structural debt, #520 release engineering, #541 sidecars to git, #555, #556, #563, #564. There is no `GOVERNANCE.md` or `MAINTAINERS.md`. **Why this matters now:** `AUTHORS.md:16` invites contributors to "add yourself here in your first pull request" while there is nothing sized for a first pull request to point at. The tracker already *has* a decision process — `triage → accepted | declined | needs-info` is visibly in use — but it exists only as label names, so a newcomer cannot tell whether a proposal gets an answer or disappears. For a launch whose stated purpose is involving a wider group of people, that is the gap that decides whether anyone stays. **Proposal:** add a `good first issue` label and tag two or three genuinely small items — this review produced several suitable ones (the placeholder email, the `Nieuw` tab label, the stale file paths in GIT_STORAGE.md, the committed golden failure artefacts). Then six lines in `docs/CONTRIBUTING_GUIDELINES.md` under *Issue Tracking* describing the triage path the labels already encode. No governance document needed for one maintainer.
Author
Owner

Opgelost in #656 (gemerged). make check groen op de gerebasede kop.

Opgelost in #656 (gemerged). `make check` groen op de gerebasede kop.
brenno 2026-07-22 17:30:10 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
LibreKAT/Ocideck#596
No description provided.