From 24681624eb369c51d1c7f548585c7b7319546cd5 Mon Sep 17 00:00:00 2001
From: Achill Gilgenast <achill@achill.org>
Date: Thu, 15 Jan 2026 19:51:01 +0100
Subject: [PATCH] docs: mention to open issues when a merge happend without
 maintainer response
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

See the meeting notes from the 2026-01-19:
(https://docs.postmarketos.org/policies-and-processes/governance/team-meetings/meeting-notes.html)

> Discussed pmaports!7770, possibly limiting the wait period for maintainer
> approval from 2 weeks to 1 week.
>
> We discussed to keep 2 weeks and make an issue template for “had to merge
> without maintainer review”, the new process will then be that the template
> gets filled out if a MR has to be merged without maintainer review after
> two weeks. The maintainer can then either say that they plan to review
> future merge requests, or indicate that they don’t want to maintain the
> thing anymore, or just not respond (which implies that they don’t want
> to maintain anymore). That way we should be able to get the listed
> maintainers to reflect reality better.
>
> Everyone reading this, please make sure you are not listed as maintainer
> for packages that you don’t plan to do reviews for anymore :)

Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7770>
---
 .../Maintainership_status_of_package.md               | 11 +++++++++++
 docs/approval-rules.md                                |  3 ++-
 2 files changed, 13 insertions(+), 1 deletion(-)
 create mode 100644 .gitlab/issue_templates/Maintainership_status_of_package.md

diff --git a/.gitlab/issue_templates/Maintainership_status_of_package.md b/.gitlab/issue_templates/Maintainership_status_of_package.md
new file mode 100644
index 000000000..f6209e833
--- /dev/null
+++ b/.gitlab/issue_templates/Maintainership_status_of_package.md
@@ -0,0 +1,11 @@
+<!-- Use this template to kick off the discussion for a package with (presumably)
+     inactive maintainers and the future for the maintainership of the package.
+-->
+
+### Information
+
+* Package name:
+* Maintainers of the package:
+* MR that had no maintainer response, if applicable:
+
+/label ~maintainership-status
diff --git a/docs/approval-rules.md b/docs/approval-rules.md
index 89dfe10a7..f60f477cf 100644
--- a/docs/approval-rules.md
+++ b/docs/approval-rules.md
@@ -13,7 +13,8 @@ it is sufficient to solely have the approval a team member.
 
 If there is no package maintainer or the package maintainer does not
 reply within 2 weeks from the time the MR was opened, then any 2 approvals are
-required.
+required. When you merge a MR with no maintainer response, open a issue with the
+issue template: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/new?description_template=Maintainership_status_of_package>.
 
 If there are multiple maintainers, an approval from any maintainer is sufficient
 to satisfy the "approval by the package maintainer" criteria (i.e., not every