Recipe maintainership #38

New Issue

3wordchant · 2026-01-09T01:42:06Z

3wordchant commented

2026-01-09 01:42:06 +00:00

Ah yeah, I hadn't noticed the official maintainer bit. Maybe we should also both add ourselves to that list? I'll do it if you do... (is there some process there?).

Originally posted by @nicksellen in #37 (comment)

> Ah yeah, I hadn't noticed the official maintainer bit. Maybe we should also both add ourselves to that list? I'll do it if you do... (is there some process there?). _Originally posted by @nicksellen in https://git.coopcloud.tech/coop-cloud/mastodon/pulls/37#issuecomment-29658_

❤️ 1

3wordchant commented

2026-01-09 01:43:53 +00:00

@nicksellen @ammaratef45 the process is still coming together, I think the most coherent is Traefik's, details here: coop-cloud/traefik#60

Personally I would definitely like to adopt the same model where only maintainers can merge PRs.

And I would definitely be open to you joining as maintainers @ammaratef45 @nicksellen.

@benjaminlyng what do you think?

@nicksellen @ammaratef45 the process is still coming together, I think the most coherent is Traefik's, details here: https://git.coopcloud.tech/coop-cloud/traefik/issues/60 Personally I would definitely like to adopt the same model where only maintainers can merge PRs. And I would definitely be open to you joining as maintainers @ammaratef45 @nicksellen. @benjaminlyng what do you think?

3wordchant commented

2026-01-09 01:44:22 +00:00

And actually on reflection I'm more than happy dropping out as a maintainer and leaving it to you 3 😅

decentral1se commented

2026-01-09 09:11:04 +00:00

👉 https://docs.coopcloud.tech/maintainers/maintain/ 👈

ammaratef45 commented

2026-01-10 06:48:44 +00:00

Thanks for offering @3wordchant but I'll pass on being a maintainer for the mastodon recipe for now, I have few other recipes that I would rather focusing on and don't have other maintainers

👍 2

3wordchant commented

2026-01-10 07:16:21 +00:00

👉 https://docs.coopcloud.tech/maintainers/maintain/ 👈

Oh wow how did I miss / forget about this, ｉｎｃｒｅｄｉｂｌｅ.

@benjaminlyng what are your thoughts on us copypasting the Traefik MAINTENANCE.md and fiddling the permissions as described on that page?

And @nicksellen would you like to join the party?

> 👉 https://docs.coopcloud.tech/maintainers/maintain/ 👈 Oh wow how did I miss / forget about this, ｉｎｃｒｅｄｉｂｌｅ. @benjaminlyng what are your thoughts on us copypasting the Traefik `MAINTENANCE.md` and fiddling the permissions as described on that page? And @nicksellen would you like to join the party?

❤️ 1

nicksellen commented

2026-01-10 12:14:41 +00:00

Yes, would be happy to be added.

One point I would like to get clearer on is the release process. My last two PRs were completed and merged, but I did not know if I should do a release.

One of the PRs would need an entry added in the releases notes, but as it wasn't being released at that moment, I didn't have a version number to use for the release note file.

For the traefik PR template it says to add a release note -> https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/.gitea/PULL_REQUEST_TEMPLATE.md and then links to this page to explain about release notes https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes where it's just a todo item to document it.

Yes, would be happy to be added. One point I would like to get clearer on is the release process. My last two PRs were completed and merged, but I did not know if I should do a release. One of the PRs would need an entry added in the releases notes, but as it wasn't being released at that moment, I didn't have a version number to use for the release note file. For the traefik PR template it says to add a release note -> https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/.gitea/PULL_REQUEST_TEMPLATE.md and then links to this page to explain about release notes https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes where it's just a todo item to document it.

❤️ 2

decentral1se commented

2026-01-10 16:17:06 +00:00

One point I would like to get clearer on is the release process. My last two PRs were completed and merged, but I did not know if I should do a release.

It's up to yourselves as new maintainers 😄 Before it was just cowgirl release mode whenever anyone had time.

One of the PRs would need an entry added in the releases notes, but as it wasn't being released at that moment, I didn't have a version number to use for the release note file.

You can throw everything in a next file: docs.

For the traefik PR template it says to add a release note -> https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/.gitea/PULL_REQUEST_TEMPLATE.md and then links to this page to explain about release notes https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes where it's just a todo item to document it.

Docs patches welcome! Didn't get to finish it yet 🤸‍♀️ In general, we notice that those things are common pitfalls for contributors and cause breakage on deploy but we just need to all build up the habit when doing maintenance work. Please feel free to adapt / change 🥇

> One point I would like to get clearer on is the release process. My last two PRs were completed and merged, but I did not know if I should do a release. It's up to yourselves as new maintainers 😄 Before it was just cowgirl release mode whenever anyone had time. > One of the PRs would need an entry added in the releases notes, but as it wasn't being released at that moment, I didn't have a version number to use for the release note file. You can throw everything in a `next` file: [docs](https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes). > For the traefik PR template it says to add a release note -> https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/.gitea/PULL_REQUEST_TEMPLATE.md and then links to this page to explain about release notes https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes where it's just a todo item to document it. Docs patches welcome! Didn't get to finish it yet 🤸‍♀️ In general, we notice that those things are common pitfalls for contributors and cause breakage on deploy but we just need to all build up the habit when doing maintenance work. Please feel free to adapt / change 🥇

👍 1

3wordchant commented

2026-01-26 18:44:47 +00:00

OK @nicksellen I heard from Benjamin, $life_stuff ongoing, will rejoin when possible. So I think please go ahead and submit a PR to add yourself to the README! (And for a million bonus points, copypasting MAINTENANCE.md here.

OK @nicksellen I heard from Benjamin, `$life_stuff` ongoing, will rejoin when possible. So I think please go ahead and submit a PR to add yourself to the README! (And for a million bonus points, copypasting `MAINTENANCE.md` here.

benjaminlyng commented

2026-02-03 13:19:03 +00:00

Hi! Trying to ease back into the world. Welcome abord @nicksellen! Iv'e only just volunteered as a maintainer and still haven't found my way around it. Actually i'd be more comfortable if I wasn't a maintainer and that there was a more gitops-ish workflow where I could create a PR and everything relating to releases was automatic from there.

Personally I would definitely like to adopt the same model where only maintainers can merge PRs.

But that's another discussion.

Again welcome!

Hi! Trying to ease back into the world. Welcome abord @nicksellen! Iv'e only just volunteered as a maintainer and still haven't found my way around it. Actually i'd be more comfortable if I wasn't a maintainer and that there was a more gitops-ish workflow where I could create a PR and everything relating to releases was automatic from there. > Personally I would definitely like to adopt the same model where only maintainers can merge PRs. But that's another discussion. Again welcome!

❤️ 2

decentral1se commented

2026-02-04 10:15:42 +00:00

We're all discovering this maintainer process right now together, so please open issues and draw up proposals, docs patches, etc. It would be really appreciated @benjaminlyng! We need to make being a maintainer as simple and straightforward as possible for taking care of the entire config commons present and future, so now is the time to have that discussion 🙃 More general issues are usually opened up here: https://git.coopcloud.tech/toolshed/organising/issues

Sign in to join this conversation.

5 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/mastodon#38