docs: 009/010 resolutions are in

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

@@ -0,0 +1,18 @@
+## Resolution 009: Federation common fund buffer - 2023-07-03
+
+- Deadline: 2023-07-17
+- Size: Large
+
+### Summary
+
+The Co-op Cloud Federation has [a common fund](https://opencollective.com/coop-cloud#category-BUDGET) which can be used by federation members by proposing [budgets](https://docs.coopcloud.tech/federation/resolutions/passed/004/).
+
+With Resolution 009, we want to introduce the idea of a common fund buffer.
+
+This buffer is proposed to be set at 1,500 EUR. When the buffer is reached, no more budgets can be proposed. When the fund increases once more, budgets can resume.
+
+The buffer is in place to reserve funds for critical collective spending when we have limited income.
+
+### Details
+
+1,500 EUR is fairly arbitrarily chosen but seems to be a reasonable amount of money to cover situations where, e.g. we need to pay for servers, domains, mail accounts or other common critical infrastructure.

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

@@ -0,0 +1,26 @@
+## Resolution 010: Critical fixes budget - 2023-07-03
+
+- Deadline: 2023-07-17
+- Size: Large
+
+### Summary
+
+We propose to have a standing budget of 10 hrs / month available for fixes in Abra, Co-op Cloud recipes and other critical tools (e.g. recipes.coopcloud.tech) in the Co-op Cloud ecosystem.
+
+A fix is deemed critial when it is listed on this coop-cloud/organising board:
+
+> https://git.coopcloud.tech/coop-cloud/organising/projects/24
+
+This board is collectively gardened by Co-op Cloud participants (both federation members and not). The process for adding a ticket to the board is informal. If in doubt, please seek guidance from others in the Matrix chat if a fix should be flagged as critical.
+
+This budget can be claimed by any volunteer who would like to develop the fix. If the volunteer is not a Co-op Cloud federation member, they must first be "vouched for" by a federation member. This is an informal process which can be arranged via the Matrix chat. This aims to assure agreement on timing and what the fix should contain beforehand.
+
+Fixes can be claimed by assiging yourself to the ticket. If within 1 week there is no updates on the ticket, another volunteer can propose to take over. This process is also informal: please @ the original volunteer and give some reasonable time for them to reply (suggested: 1 day). If the fix is urgent and things need to move faster, please state so on the ticket.
+
+### Details
+
+This budget stands open and available for use until the common fund buffer is reached. Please see Resolution 009 for further details on the buffer.
+
+Please see [Resolution 003](https://docs.coopcloud.tech/federation/resolutions/passed/003/) for details on the hourly rate for this work.
+
+Invoices can be submitted via the Co-op Cloud Open Collective. Please see [these docs](https://docs.coopcloud.tech/federation/finance/#how-to-get-paid-via-open-collective) for how to do that.