From db58b29414e66c7b2a25b4d61e324edbb9b8575b Mon Sep 17 00:00:00 2001
From: Michael Baentsch <57787676+baentsch@users.noreply.github.com>
Date: Tue, 10 Sep 2024 14:31:18 +0200
Subject: [PATCH] implementing #10

Signed-off-by: Michael Baentsch <57787676+baentsch@users.noreply.github.com>
---
 .github/pull_request_template.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..d73e185
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,23 @@
+<!-- Please give a brief explanation of the purpose of this pull request. -->
+
+<!-- Does this PR resolve any issue?  If so, please reference it using automatic-closing keywords like "Fixes #123." -->
+
+<!-- As changes to the file `config.yaml` are particularly sensitive because they change GH permissions throughout the project, the following 
+rules apply to PRs affecting this file without exception:
+- [ ] PRs must be approved by 2 members of the OQS TSC
+- [ ] Permissions must not violate permissions documented in GOVERNANCE.md files for sub projects where such files exist
+
+The following goals apply to changes to the file `config.yaml` with exceptions possible, as long as the rationale for the excption is documented by comments in the file:
+- [ ] all sub projects should be treated identically wrt roles & responsibilities as per the detailed list below
+- [ ] teams/team designations are to be used wherever possible; using personal GH handles should only be used in team definitions
+- [ ] Admin changes to the file must be documented by comments as to the rationale of the change
+
+All the following conditions hold
+-    sub project maintainers have admin rights on the sub projects
+-    OQS and sub project release managers have maintainer rights on the sub projects but can themselves set/reset branch protection rules limiting write access to sensitive branches
+-    sub project committers have write rights on all branches of the sub projects but can request branch protection rules limiting this
+-    sub project contributors have write rights on all branches except main on those sub projects
+-    OQS and sub project triage actors have triage rights on all branches of the sub projects
+-    OQS maintainers and LF admins have admin rights on the organization (e.g., org-wide secret management) as well as maintenance rights on the team configurations
+
+-->