[llvm] [llvm][docs] Document how to ask for things other than commit access (PR #146340)

[David Spickett via llvm-commits]

https://github.com/DavidSpickett created https://github.com/llvm/llvm-project/pull/146340

This is the implicit process but useful to spell it out I think. To give folks more confidence in asking.

Inspired by https://discourse.llvm.org/t/request-github-issue-triage-permission-for-labeling-clang-issues/87126/1

>From 11f5a1bb3694e6593dfb3e569d8930b1eb8880bd Mon Sep 17 00:00:00 2001
From: David Spickett <david.spickett at linaro.org>
Date: Mon, 30 Jun 2025 11:56:40 +0000
Subject: [PATCH] [llvm][docs] Document how to ask for things other than commit
 access

This is the implicit process but useful to spell it out I think.
To give folks more confidence in asking.

Inspired by https://discourse.llvm.org/t/request-github-issue-triage-permission-for-labeling-clang-issues/87126/1
---
 llvm/docs/DeveloperPolicy.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst
index 6b60812df83bd..c0e0c019714bf 100644
--- a/llvm/docs/DeveloperPolicy.rst
+++ b/llvm/docs/DeveloperPolicy.rst
@@ -550,6 +550,17 @@ after they are committed, depending on the nature of the change).  You are
 encouraged to review other peoples' patches as well, but you aren't required
 to do so.
 
+Obtaining Other Access or Permissions
+-------------------------------------
+
+To obtain access other than commit access, you can raise an issue like the one
+for obtaining commit access. However, instead of including PRs you have authored,
+include evidence of your need for this type of access.
+
+For example, if you are helping to triage issues and want the ability to add
+labels, include links to issues you have triaged previously and explain how
+having this ability would help that work.
+
 .. _discuss the change/gather consensus:
 
 Making a Major Change