Notices by Co-op Cloud (coopcloud@social.coop)

And, much belated, some tales from last week's kite-flying (🧵 1/4)

First up: great question from a community member, "how to get involved if you're not hosting an instance".

A couple of people on the call figured out there's a way to identify "critical fix" (i.e. pad 🤑) issues using the Gitea API: https://git.coopcloud.tech/api/v1/repos/issues/search?state=open&labels=critical+fix (nothing there right now… see Resolution 31 for how to populate that list! https://docs.coopcloud.tech/federation/resolutions/passed/031/)

We also talked about how to get an account on git.coopcloud.tech to open issues, make pull requests – easiest answer for residents of the fediverse is to send us a DM!

And, we talked about recipe maintainership a little bit; exciting to see more recipes becoming officially maintained. Check out "how to become a maintainer" docs for more: https://docs.coopcloud.tech/maintainers/maintain/

(2/4)

Next, more chat about backup-bot-two¹, our reluctantly-built (but handy!) Docker volume backup script.

There was energy to cut a new release (the latest published version is behind a few nice additions) — including a bugfix that one person at kite-flying ran into — and a brief chat about restore testing, kicked off by an @autonomic member who mentioned they're "using backupbot across 20-30 servers" 🤯

¹ https://git.coopcloud.tech/coop-cloud/backup-bot-two/

(3/4)

Finally, we talked about if there's anything Co-op Cloud can do to help sysadmins meet each other and start building the immense trust needed to share access to each other's systems to help each other out.

Personally, a huge project goal for Co-op Cloud has been reducing sysadmin sadness, and there are certainly a lot of capable and trustworthy people in our orbit… the pieces are maybe there.

Folks talked about "growth at the rate of trust" (starting small and building from there), end-to-end encryption as a means of reducing the trust needed in the first place, and backup-storage as a means of low-trust mutual aid.

(4/4)

–3wordchant

Coming Soon: "Selfhosted Infrastructure Any%", a speedrun-themed livestream demo of setting up some libre software tools using Co-op Cloud.

This Thursday 28 March 2024 @ 8:30pm (20:30) UTC

–3wc

A co-op hosting network proposal is brewing with @bonfire 🎉

> The current proposal is a joint effort between Co-op Cloud and Bonfire Networks, with discussions ongoing with other interested groups. While we are of course focused on a solution for hosting Bonfire instances, the ecosystem could be extended to involve other open source projects as well... We are looking for more partners to build the ecosystem, if you are interested please contact us at team@bonfire.cafe

https://bonfirenetworks.org/hosting/

@zeh @serge yeehaw let us know what you think! also shout-out to https://small-tech.org @aral and co. which is in those docs too 🤓 #inspo -- d1

@Zee thank you so much for the report! ?, that email address wasn't as ready as I thought ? Should work now! —@3wc

the first meeting of the Co-op Cloud Federation is this Friday 3 March @ 15:00 UTC ?

you can read more about the idea behind the Federation here: https://coopcloud.tech/blog/federation-proposal/

if you'd like to attend, especially if you're part of a democratic collective, email us on boop@coopcloud.tech, or join us in the Co-op Cloud Community Organising" room on Matrix: https://matrix.to/#/#coopcloud-comm-org:autonomic.zone

— @3wc

#OpenSource #Co-operatives #Co-ops #Hosting