From 38c426178a215f76bf0abfd07c7925670011161a Mon Sep 17 00:00:00 2001 From: Linus Gasser Date: Tue, 21 Jul 2026 08:08:52 +0200 Subject: [PATCH] Removing last TBDs --- MAINTENANCE.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/MAINTENANCE.md b/MAINTENANCE.md index b2dcda2..9e0c683 100644 --- a/MAINTENANCE.md +++ b/MAINTENANCE.md @@ -1,9 +1,5 @@ # Nextcloud Recipe Maintenance -> Status: **DRAFT** — open for discussion with co-maintainers and the wider -> federation. Sections marked _(TBD)_ need collective input before this -> document is considered ratified. - This document describes how the Nextcloud recipe is maintained. It builds on the floor set by [Federation Resolution 025](https://docs.coopcloud.tech/federation/resolutions/passed/025/) and @@ -17,7 +13,7 @@ consistency stay something others can rely on. ## Maintainers Everyone can apply to be a recipe maintainer. -Simply add your self to the list in the README.md and open a new pull request +Simply add yourself to the list in the README.md and open a new pull request with the change. ## Maintainer Responsibilities @@ -88,8 +84,7 @@ Everyone is welcome to apply: [`README.md`](./README.md) and to the list above. 3. Once an existing maintainer merges the PR, you'll be added to the [nextcloud maintainers - team](https://git.coopcloud.tech/org/coop-cloud/teams/nextcloud-maintainers) - _(team to be created if it does not yet exist — TBD)_. + team](https://git.coopcloud.tech/org/coop-cloud/teams/nextcloud-maintainers). Stepping down is symmetrical: open a PR removing yourself, and flag it in the federation channels so the group can plan replacement before falling