generated from coop-cloud/example
stevensting
09f1cfc690
continuous-integration/drone/push Build is failing
Closes #8 Reviewed-on: #16
32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
# 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).
|