From 251670133b1d320baf0d8b32354293991520592d Mon Sep 17 00:00:00 2001 From: Johann Fischer Date: Tue, 3 Sep 2024 15:57:49 +0200 Subject: [PATCH] doc: process for adding a maintainer if the candidate does not have a role There is no clear way for a candidate to assume the role of Maintainer if the candidate is neither a Contributor nor a Collaborator. To avoid disputes and confusion, candidates who are neither Contributors nor Collaborators must be approved by the TSC before they can assume the role of Maintainer. Signed-off-by: Johann Fischer --- doc/project/project_roles.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/project/project_roles.rst b/doc/project/project_roles.rst index ccb74186d9b..b61d163abf9 100644 --- a/doc/project/project_roles.rst +++ b/doc/project/project_roles.rst @@ -133,7 +133,9 @@ in addition to those listed for Contributors and Collaborators: Contributors or Collaborators are promoted to the Maintainer role by adding the GitHub user name to one or more ``maintainers`` sections of the -:ref:`maintainers_file` in the Zephyr repository. +:ref:`maintainers_file` in the Zephyr repository. Candidates who are neither +Contributors nor Collaborators must be approved by the TSC before they can +assume the role of Maintainer. Maintainer approval of pull requests are counted toward the minimum required approvals needed to merge a PR. Other criteria for merging may apply.