diff --git a/.gitea/PULL_REQUEST_TEMPLATE.md b/.gitea/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..5c24bac
--- /dev/null
+++ b/.gitea/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,16 @@
+---
+name: "Collabora pull request template"
+about: "Collabora pull request template"
+---
+
+<!-- 
+Thank you for doing recipe maintenance work!
+Please mark all checklist items which are relevant for your changes.
+Please remove the checklist items which are not relevant for your changes.
+Feel free to remove this comment.
+-->
+
+* [ ] I have deployed and tested my changes
+* [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
+* [ ] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
+* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
diff --git a/MAINTENANCE.md b/MAINTENANCE.md
new file mode 100644
index 0000000..5c26a2f
--- /dev/null
+++ b/MAINTENANCE.md
@@ -0,0 +1,31 @@
+# Collabora Recipe Maintenance
+
+All contributions should be made via a pull request. This is to ensure a
+certain quality and consistency, that others can rely on.
+
+## Maintainer Responsibilities
+
+A recipe maintainer has the following responsibilities:
+
+- Respond to pull requests / issues within two weeks
+- Make image security updates within a week
+- Make image major updates every three months
+
+In order to fullfill these responsibilities a recipe maintainer:
+
+- Has to watch the repository (to get notifications)
+- Needs to make sure renovate is configured properly
+
+## Pull Requests
+
+A pull request can be merged if it is approved by at least one maintainer. For
+pull requests opened by a maintainer they need to be approved by another
+maintainer. Even though it is okay to merge a pull request with one approval, it
+is always better if all maintainers looked at the pull request and approved it.
+
+## Become a maintainer
+
+Everyone can apply to be a recipe maintainer:
+1. Watch the repository to always get updates
+2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
+3. Once the pull request gets merged you will be added to the [collabora maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/collabora-maintainers).
diff --git a/README.md b/README.md
index 9de9cc9..2184a4d 100644
--- a/README.md
+++ b/README.md
@@ -4,14 +4,15 @@
 
 <!-- metadata -->
 
+* **Maintainer**: [@stevensting}(https://git.coopcloud.tech/stevensting)
 * **Category**: Apps
-* **Status**: 3, stable
+* **Status**: 4, stable
 * **Image**: [`collabora`](https://hub.docker.com/r/collabora/code), 4, upstream
-* **Healthcheck**: No
-* **Backups**: No
-* **Email**: 3
-* **Tests**: 2
-* **SSO**: No
+* **Healthcheck**: Yes
+* **Backups**: N/A
+* **Email**: N/A
+* **Tests**: No
+* **SSO**: N/A
 <!-- endmetadata -->
 
 ## Basic usage