Call for maintainers #57

New Issue

Open

opened 2026-01-20 13:50:04 +00:00 by decentral1se · 4 comments

decentral1se commented 2026-01-20 13:50:04 +00:00

Owner

Copy Link

I can help but need support. Who can help?

Sooooo many people run this recipe 🔥

I can help but need support. Who can help? Sooooo many people run this recipe 🔥

stevensting commented 2026-01-20 14:59:28 +00:00

Owner

Copy Link

We were interested and LIT I think @p4u1 @Apfelwurm @moritz @simon

We were interested and LIT I think @p4u1 @Apfelwurm @moritz @simon

👍 1 👀 2 ❤️ 1

simon commented 2026-01-20 15:36:20 +00:00

Owner

Copy Link

Yes, think that makes sense. Maybe we can share the responsibility?
Usually we try to update the recipe at least every 3 months according to this guide. You also plan to run Nextcloud the KolliCloud-way, right?

For improvements on the recipe itself: We currently lack the time to do bigger improvements, but I'm optimistic that this will change in the future

Yes, think that makes sense. Maybe we can share the responsibility? Usually we try to update the recipe at least every 3 months according to [this](https://wiki.local-it.org/s/5a897109-bf7b-4c05-8bb2-d670e449dff8) guide. You also plan to run Nextcloud the KolliCloud-way, right? For improvements on the recipe itself: We currently lack the time to do bigger improvements, but I'm optimistic that this will change in the future

❤️ 1

Apfelwurm commented 2026-01-20 18:29:00 +00:00

Owner

Copy Link

count me in for that one, since i'm standing knee deep in nexctloud operations anyways.
But: I am sometimes bad when it comes to proactive continuity tasks, so not sure, how often i will get to do the basic upgrade chore.

@simon we talked about using alakazam in the future, but as of now we are just deploying our nextclouds with cc

I'm not sure, if i'd be happy with a at least 3 month cycle for nc, since nearly every patch release contains fixes in regards to security, even though they are often only updating the ca certificate bundles or code signing revocation lists, i think this should ideally happen faster than that, if we manage to get a maintainers team put together.

Maybe, we can also talk about fast patch/minor upgrades and slower major upgrades?

count me in for that one, since i'm standing knee deep in nexctloud operations anyways. But: I am sometimes bad when it comes to proactive continuity tasks, so not sure, how often i will get to do the basic upgrade chore. @simon we talked about using alakazam in the future, but as of now we are just deploying our nextclouds with cc I'm not sure, if i'd be happy with a at least 3 month cycle for nc, since nearly every patch release contains fixes in regards to security, even though they are often only updating the ca certificate bundles or code signing revocation lists, i think this should ideally happen faster than that, if we manage to get a maintainers team put together. Maybe, we can also talk about fast patch/minor upgrades and slower major upgrades?

❤️ 1

decentral1se commented 2026-01-20 19:44:05 +00:00

Author

Owner

Copy Link

Does someone want to make a draft MAINTENANCE.md based on https://docs.coopcloud.tech/maintainers/maintain/#maintenancemd-template? The initial idea was that each recipe maintainer group would have autonomy to choose how maintenance is carried out within the limits https://docs.coopcloud.tech/federation/resolutions/passed/025/. I'm fine with whatever schedule works and I think it would be cool to match an actual "real-world" release schedule. That was also what we discussed at CCC? That practices from KolliCloud would "return upstream" so we can work on stability together at the source. We'll have to see what meets a compromise with other speeds. 3 maintainers sounds like enough to me to start!

Does someone want to make a draft `MAINTENANCE.md` based on https://docs.coopcloud.tech/maintainers/maintain/#maintenancemd-template? The initial idea was that each recipe maintainer group would have autonomy to choose how maintenance is carried out within the limits https://docs.coopcloud.tech/federation/resolutions/passed/025/. I'm fine with whatever schedule works and I think it would be cool to match an actual "real-world" release schedule. That was also what we discussed at CCC? That practices from KolliCloud would "return upstream" so we can work on stability together at the source. We'll have to see what meets a compromise with other speeds. 3 maintainers sounds like enough to me to start!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

feature/imaginary

kc_stable

nextcloud-v28

add-theming-v28.0.5

add-theming

update-nginx-conf

split-bbb-onlyoffice-compos

split-onlyoffice-bbb-config

authentik_sso

healthchecks

occ_cmds

auto_app_install

embed_nextcloud_in_iframe

auto_configure_sso

add-postgres-db

13.0.1+32.0.3-fpm

13.0.0+32.0.3-fpm

12.1.0+31.0.6-fpm

12.0.1+31.0.6-fpm

12.0.0+31.0.6-fpm

11.4.0+30.0.6-fpm

11.4.0+30.0.10-fpm

11.3.0+30.0.6-fpm

11.2.0+30.0.6-fpm

11.1.0+30.0.6-fpm

11.0.1+30.0.4-fpm

11.0.0+30.0.4-fpm

10.0.0+30.0.4-fpm

9.2.0+29.0.8-fpm

6.0.11+28.0.10-fpm

6.0.10+28.0.10-fpm

6.0.9+28.0.10-fpm

9.1.2+29.0.5-fpm

6.0.8+28.0.5-fpm

6.0.7+28.0.5-fpm

9.1.0+29.0.5-fpm

9.0.0+29.0.5-fpm

6.0.6+28.0.5-fpm

8.0.1+29.0.3-fpm

8.0.0+29.0.1-fpm

7.0.3+29.0.1-fpm

6.0.5+28.0.5-fpm

7.0.2+29.0.1-fpm

7.0.1+29.0.1-fpm

7.0.0+29.0.0-fpm

6.0.4+28.0.5-fpm

6.0.3+28.0.5-fpm

6.0.2+28.0.5-fpm

5.0.3+27.0.1-fpm

6.0.1+28.0.2-fpm

6.0.0+28.0.1-fpm

5.2.0+27.1.5-fpm

5.1.1+27.1.5-fpm

5.1.0+27.1.3-fpm

5.0.2+27.0.1-fpm

5.0.1+27.0.1-fpm

5.0.0+27.0.0-fpm

4.0.7+26.0.2-fpm

4.0.6+26.0.2-fpm

4.0.5+26.0.2-fpm

4.0.4+26.0.2-fpm

4.0.3+26.0.2-fpm

4.0.2+26.0.2-fpm

4.0.1+26.0.1-fpm

4.0.0+26.0.1-fpm

3.3.2+25.0.6-fpm

3.3.1+25.0.5-fpm

3.3.0+25.0.5-fpm

3.2.0+25.0.4-fpm

3.1.2+25.0.4-fpm

3.1.1+25.0.1-fpm

3.1.0+25.0.1-fpm

3.0.1+25.0.1-fpm

3.0.0+25.0.1-fpm

2.1.4+24.0.6-fpm

2.1.3+24.0.5-fpm

2.1.2+24.0.3-fpm

2.1.1+24.0.2-fpm

2.1.0+24.0.0-fpm

2.0.0+23.0.4-fpm

1.0.0+23.0.1-fpm

Labels

Clear labels

bug

Something is not working

documentation

For issues that are calling out documentation gap

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se fauno flancian Frando iexos jade javielico jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip

No Assignees

4 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#57

No description provided.