[openstreetmap/openstreetmap-website] Document project roles, permissions, and eligibility criteria (PR #6728)
Minh Nguyễn
notifications at github.com
Wed Jan 21 17:19:17 UTC 2026
@1ec5 commented on this pull request.
> +* View and handle security reports
+* Grant maintainer and triager roles to contributors. Nominations can be from contributors and/or current maintainers, and are discussed and agreed upon by the existing maintainers
+* Other administrative work, including changing some project settings (like enabling CI workflows)
+
+To become eligible for the maintainer role, contributors should show a consistent history of quality in their pull requests, a history of helping other people when reviewing code, and a history of providing actionable guidance to other contributors.
+
+## Triagers
+
+The primary goal of the triagers is to reduce the need for maintainers to manage issues and pull requests.
+
+This goal can be achieved by keeping the issues list small, each issue on topic, and discussions focussed and productive. Anyone in the community can help with most of this work. However, triagers have extra permissions that can help in certain situations.
+
+These additional permissions allow triagers to:
+
+* Close any issue. This can include duplicate issues, off-topic issues, spam, etc
+* Add labels to any issue. This can help highlight bugs, pull requests that need changes, etc
For awareness, the triager role apparently doesn’t come with the ability to edit the labels themselves, just to apply them. I think this is fine but just wanted to head off any potential future misunderstanding.
> +* Other administrative work, including changing some project settings (like enabling CI workflows)
+
+To become eligible for the maintainer role, contributors should show a consistent history of quality in their pull requests, a history of helping other people when reviewing code, and a history of providing actionable guidance to other contributors.
+
+## Triagers
+
+The primary goal of the triagers is to reduce the need for maintainers to manage issues and pull requests.
+
+This goal can be achieved by keeping the issues list small, each issue on topic, and discussions focussed and productive. Anyone in the community can help with most of this work. However, triagers have extra permissions that can help in certain situations.
+
+These additional permissions allow triagers to:
+
+* Close any issue. This can include duplicate issues, off-topic issues, spam, etc
+* Add labels to any issue. This can help highlight bugs, pull requests that need changes, etc
+* Hide any comment. This can be useful for off-topic conversations like issue assignment
+* Rename or edit any issue description. This can be useful when new contributors use the wrong terminology, etc
Triagers can also edit issue relationships and create subissues, which can be helpful for making sense of the backlog.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6728#pullrequestreview-3688429363
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/pull/6728/review/3688429363 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260121/e69a5bac/attachment-0001.htm>
More information about the rails-dev
mailing list