feat: Draft resolution for multi-node funding

.gitignore

@@ -1,3 +1,3 @@
 site/
 .venv
-.~
+*~

docs/federation/handbook.md

@@ -17,23 +17,3 @@ We try to gather as many "case studies" as possible, stories & concrete examples
 ## Monthly updates
 
 We have decided we'll try to do monthly progress updates. These will be published on the Co-op Cloud blog. It's a pretty loose format and we're basically just copy/pasta'ing things to a public pad during the month: ["This month in Co-op Cloud"](https://pad.autonomic.zone/YHKn4vHORmS6wjN1t2zi5A?both). Feel free to add your items to the monthly agenda and they will be included! All the previous posts can be seen [here](https://coopcloud.tech/blog/).
-
-## Kite Flying Hours
-
-The "Kite Flying Hour" is a weekly public moment where anyone can "drop by" into a Jitsi call and ask/do/propose whatever and meet some people who are currently working on the project. We haven't worked it all out but our process for now is the following.
-
-Someone from Autonomic will volunteer to be present and talk about the project for an hour weekly from 15:00 CEST - 16:00 CEST. We announce the hour via our socials: A [pinned toot](https://social.coop/web/statuses/106528094828958420) on [`@coopcloud@social.coop`](https://social.coop/@coopcloud) and a post to the `#coopcloud:autonomic.zone` room.
-
-Here is some invitation boilerplate which you can use:
-
-> Hey folks, you're all warmly invited to the Co-op Cloud Kite Flying Hour at `$X_TIME` `$Y_TZ` `$Z_DATE` over in [meet.jit.si/CoopCloudKiteFlyingHour](https://meet.jit.si/CoopCloudKiteFlyingHour)!
->
-> Inspired by exquisite childhood memories of [flying kites, eating popsicles and looking at clouds](https://norwichhistory.org/norwich-a-z-j-is-for-jigsaw/), it's an open hour to come hang out online and discuss/co-work/lurk/etc. around the [Co-op Cloud](https://coopcloud.tech/) project.
->
-> There are no "stupid questions"! It's a space to inquire, be curious and have a good time and get to know each other.
->
-> We take notes and doodle on [this collaboratively editable pad](https://pad.autonomic.zone/VtyrLUl9RWaJGgEDrncQUw?view). If you don't have time to attend, feel free to drop your questions and some contact details also, so we can get in touch. This is only the first Kite Flying Hour in a recurring series of Kite Flying Hours.
->
-> Hope to see you there! ☁️ 🌞 🖥️
-
-To work around Hedgedoc length limits, [we keep past content from the kite-flying pad here](./kite-flying-pad-archive).

docs/federation/organisers.md

@@ -22,18 +22,3 @@ Welcome to the organisers guide! Organisers are folks who focus on the social wo
 
 We're still working out what it looks like to do this kind of work in the project. If you like the idea of this kinda of work and/or are already doing it, please send patches to improve this documentation :rocket:
 
-## Kite Flying Hours
-
-The "Kite Flying Hour" is a weekly public moment where anyone can "drop by" into a Jitsi call and ask/do/propose whatever and meet some people who are currently working on the project. We haven't worked it all out but our process for now is the following.
-
-Someone should volunteer to be present and talk about the project for an hour weekly, alternating between 12 and 19 UTC each week. We schedule the call [in a shared calendar](https://coopcloud.tech/ics/kite-flying.ics) (which people can subscribe to in calendar apps) and announce the hour via our socials: A pinned toot on [`@coopcloud@social.coop`](https://social.coop/@coopcloud) and a post to the `#coopcloud:autonomic.zone` room.
-
-Here is some invitation boilerplate which you can use:
-
-> Hey folks, you're all warmly invited to the Co-op Cloud Kite Flying Hour at `$X_TIME` `$Y_TZ` `$Z_DATE` over in [vs.autistici.org/CoopCloudKiteFlyingHour](https://vs.autistici.org/CoopCloudKiteFlyingHour)!
->
-> Inspired by exquisite childhood memories of [flying kites, eating popsicles and looking at clouds](https://norwichhistory.org/norwich-a-z-j-is-for-jigsaw/), it's an open hour to come hang out online and discuss/co-work/lurk/etc. around the [Co-op Cloud](https://coopcloud.tech/) project.
->
-> There are no "stupid questions"! It's a space to inquire, be curious and have a good time and get to know each other.
->
-> We take notes and doodle on [this collaboratively editable pad](https://pad.autonomic.zone/VtyrLUl9RWaJGgEDrncQUw). If you don't have time to attend, feel free to drop your questions and some contact details also, so we can get in touch. This is only the first Kite Flying Hour in a recurring series of Kite Flying Hours.

docs/federation/resolutions/draft/043.md

@@ -0,0 +1,59 @@
+---
+title: "Resolution 043: Budget 018: Multi-Node Coop Cloud"
+---
+
+- Topic: Budget 018: Multi-Node Coop Cloud
+- Date: 2026-07-16
+- Deadline: 2026-07-30
+- Size: Large
+- Budget: 2000€, with possibility of extension in future resolutions
+- Who will implement this: @amras and other willing contributors
+- Duration: Until the budget is exhausted or all goals are met. Estimated end of October 2026.
+
+## Motivation
+Coop Cloud's recipes and tooling were developed to support vertical, single-VPS infrastructure. This was sufficient for a time, because the early member coops used single-VPS infrastructure. However, several newer members have a need for swarms distributed across multiple machines.
+
+In an ideal world we would like to see a plug-and-play model, where user-members of a Coop Cloud instance can contribute multiple (low-power, unreliable) devices to construct a robust network- without relying on a data center.
+
+## Goals
+
+### The Desired Configuration
+- Has one manager node, containing the load balancer
+- Has two worker nodes, which do not rely on local persistent storage
+- Has two data storage nodes
+- Runs abra and at least two recipes
+- Can survive the death of one or both worker nodes, and one data storage node - with only a momentary loss of data/access
+- Provides routing ingress from any node in the swarm
+
+### Example issues to be addressed
+- distributed storage, in particular:
+    * object storage
+    * databases
+    * filesystem/volumes
+ - abra limitations, e.g.:
+	* log retrieval
+	* fetching container status
+	* running commands on remote containers
+- conventions for `deployment:` tags
+
+### Limitations that won't be addressed
+- There are usecases where an operator would want to distinguish between sensitive data stored in one location, and open data accessible to all storage nodes. For this project, we should assume no data is sensitive.
+- While worker nodes and data storage nodes can be treated as unreliable, we will assume there will be only one manager node and a central load balancer. In practice, this would mean that a VPS is still required for a coop cloud deployment - though it could be arbitrarily small and store no user data.
+
+## Project structure and Accountability
+- The hub for this initiative is a toolshed Project
+	- Day-to-day discussions can be held within issue comments
+	- Hours are logged under specific issues
+- An open meeting would be held once a month at a set date, until the conclusion of this project. Any federation members are welcome to join and ask about the status of the project.
+- At the conclusion of the project, or after major milestones, a demo will be presented, e.g. during a Kite Flying hour.
+
+## Budget
+- 2000€, with the possibility to negotiate an extension in the future.
+- Standard rate of 20€/hour
+
+### Work consists of
+- Meetings and Demos
+- Investigating and integrating upstream tools (garage, docker volume plugins, rsync, etc.)
+- Writing documentation and guides for docs.coopcloud.tech
+- Modifying existing recipes
+- Creating and investigating test deployments

docs/federation/resolutions/in-progress/042.md

@@ -0,0 +1,22 @@
+---
+title: "Resolution 042: Bunk Computer Cooperative to join the federation as a member"
+---
+
+- Topic: Resolution 042: Bunk Computer Cooperative to join the federation as a member
+- Date: 2026-06-18
+- Deadline: 2026-07-03
+- Size: large
+
+## Summary
+
+Bunk Computer Cooperative uses abra and coop cloud to manage infrastructure for their clients. Bunk has also contributed to the Keycloak and Nextcloud recipes, and one Bunk member is doing financial administration for the federation.
+
+## Details
+
+In Maren's words:
+
+> Bunk has been using coop cloud since we started our co-op. Once we learned about co-op cloud, it was apparent to all three of our members that co-op cloud's structure was super smart. Tooling maintained by a federation of the co-ops that use it is set up for long term sustainability, and we want to contribute to that sustainability just as we benefit from it. We hope to upstream our work on co-op cloud whenever possible, and have already done some of that with Nextcloud and Keycloak.
+
+@ammaratef45:matrix.org from [RTM](https://resisttechmonopolies.online/) happy offered to vouch.
+
+Bunk's representative to the federation will be Maren. She can be reached at `@maren:matrix.bunk.computer` on Matrix or `maren@bunk.computer` on email.

docs/intro/contact.md

@@ -31,4 +31,10 @@ Pick the right medium for your interests.
 
     [Email Us](mailto:helo@coopcloud.tech){ .md-button .md-button--primary }
 
+- __Online call__
+
+    Join our weekly(ish) low-pressure drop-in call, "Kite flying"
+
+    [Fly a kite](/intro/kite-flying){ .md-button .md-button--primary }
+
 </div>

docs/intro/get-involved.md

@@ -12,7 +12,7 @@ We are happy to have designers, critical thinkers, artists, hackers, documenters
 
 There are a number of "roles" such as "operator", "maintainer", "organiser" which we've tried to come up with to make it more clear how you can relate to the project and how you can find ways to be involved which suit your interests. If you don't fit one of these roles, that is fine.
 
-We have [an irregular online check-in](/federation/organisers/#kite-flying-hours) for contributors of this project to let each other know what we're working on, how much time we've spent on it and how to coordinate further work.
+We have [an irregular online check-in](/intro/kite-flying) for contributors of this project to let each other know what we're working on, how much time we've spent on it and how to coordinate further work.
 
 We have a [status page](/intro/bikemap) showing what we are aiming to achieve in the near future. That gives a good overview of where we're going together.
 

docs/intro/kite-flying.md

@@ -0,0 +1,11 @@
+# Kite-flying
+
+The "Kite Flying Hour" is a weekly public moment where anyone can "drop by" into a Jitsi call and ask/do/propose whatever and meet some people who are currently working on the project. 
+
+We meet on Thursdays, alternating between 12 and 19 UTC each week. You can find out when the next call is by adding [our shared calendar](https://coopcloud.tech/ics/kite-flying.ics) to your calendar application, or look out for an announcement via [`@coopcloud@social.coop`](https://social.coop/@coopcloud) and a post to the `#coopcloud:autonomic.zone` room.
+
+Participation in kite-flying can be compensated at €20/hour; see Co-op Cloud Federation [Resolution 024](/federation/resolutions/passed/024) for details.
+
+We take notes and doodle on [this collaboratively editable pad](https://pad.autonomic.zone/VtyrLUl9RWaJGgEDrncQUw?view). If you don't have time to attend, feel free to drop your questions and some contact details also, so we can get in touch. 
+
+To work around Hedgedoc length limits, [we keep past content from the kite-flying pad here](./kite-flying-pad-archive).

mkdocs.yml

@@ -66,6 +66,7 @@ nav:
       - "Inspirations": intro/inspirations.md
       - "Project Status": intro/bikemap.md
       - "Managed Hosting": intro/managed.md
+      - "Kite flying hour": intro/kite-flying.md
       - "Get In Touch": intro/contact.md
       - "Credits": intro/credits.md
       - intro/get-involved.md
@@ -138,12 +139,14 @@ nav:
               - federation/resolutions/passed/037.md
               - federation/resolutions/passed/038.md
               - federation/resolutions/passed/039.md
+              - federation/resolutions/passed/041.md
           - "Stalled":
               - federation/resolutions/stalled/013.md
               - federation/resolutions/stalled/030.md
           - "In Progress":
               - federation/resolutions/index.md
               - federation/resolutions/in-progress/040.md
+              - federation/resolutions/in-progress/042.md
       - "Minutes":
           - federation/minutes/index.md
           - "Recently":