This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 4934ce02838 Simplify the process of adding triage team member (#59892)
4934ce02838 is described below
commit 4934ce02838a684baa54caea4be0be73d328e40c
Author: Jarek Potiuk <[email protected]>
AuthorDate: Mon Dec 29 23:25:05 2025 +0100
Simplify the process of adding triage team member (#59892)
---
ISSUE_TRIAGE_PROCESS.rst | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index 30ade57e3df..5941777f2c4 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -88,16 +88,9 @@ feel free to follow the process for every issue you stumble
upon.
Joining Issue Triage Team
'''''''''''''''''''''''''
-Joining the team is only by invitation from PMC member.
-A [LAZY CONSENSUS] vote must be passed in the PMC private list prior to
invitation.
-The thread should present data points for candidate already helping and
responding to issues, other activities in the project may also be considered.
-Activity in areas/project that is external to Apache-Airflow open source will
not be considered.
+Joining the team is only by invitation from PMC member. Another PMC member
should approve a PR where the triager is added.
Note: the numbers of people in the triage team is limited by ASF. See `list
<https://github.com/apache/airflow/blob/main/.asf.yaml#L143>`_
-An exception to the above rule would be re-adding previous member of the team.
-In that case adding may be done directly by PMC member without the need for
[LAZY CONSENSUS].
-The PR to add should clarify that the person is a previous member and quote
the original PR that added.
-
Removal from Issue Triage Team
''''''''''''''''''''''''''''''
