feat: maintainers #14

Merged
fauno merged 2 commits from maintainers into main 2026-01-16 06:16:04 +00:00
2 changed files with 33 additions and 0 deletions

32
MAINTENANCE.md Normal file
View File

@ -0,0 +1,32 @@
# Forgejo 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 day
fauno marked this conversation as resolved
Review

What do you think about these responsibilities? I set quite a high bar for the traefik recipe since it is so important. We can either try to be as responsible with forgejo or lower the bar a bit. I'm open for both, just wanted to open a discussion for it :)

What do you think about these responsibilities? I set quite a high bar for the traefik recipe since it is so important. We can either try to be as responsible with forgejo or lower the bar a bit. I'm open for both, just wanted to open a discussion for it :)
Review

i'm not sure about issues within a week, maybe two? but security updates are important yes

i'm not sure about issues within a week, maybe two? but security updates are important yes
Review

ok, let's go with 2 weeks to respond to issues then :) we can always raise the bar later

ok, let's go with 2 weeks to respond to issues then :) we can always raise the bar later
- Make image patch / minor updates within a week
- Make image major updates within a month
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 [forgejo maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/forgejo-maintainers).

View File

@ -3,6 +3,7 @@
[![Build Status](https://build.coopcloud.tech/api/badges/coop-cloud/forgejo/status.svg)](https://build.coopcloud.tech/coop-cloud/forgejo)
<!-- metadata -->
* **Maintainer**: [@p4u1](https://git.coopcloud.tech/p4u1), [@fauno](https://git.coopcloud.tech/fauno)
* **Category**: Development
* **Status**: 5
* **Image**: [`forgejo/forgejo`](https://codeberg.org/forgejo/-/packages/container/forgejo/13-rootless), 4, upstream