Adding Amras to the list of members

Including email as the most reliable way to reach me;
I'll add a website when that's running again.

docs/federation/funding-applications/ford-foundation.md

@@ -4,7 +4,7 @@ title: Ford foundation
 
 # Ford foundation
 
-> Status: **pending**
+> Status: **rejected**
 
 * [Previous material](https://notes.bonfire.cafe/nlnet-bonfire-coopcloud-hosting)
 * [Application](https://fordfoundation.forms.fm/2023-digital-infrastructure-insights-fund-rfp/forms/9724)

docs/federation/kite-flying-pad-archive.md

@@ -4,6 +4,12 @@ title: Kite Flying "Open Agenda" archive
 
 From https://pad.autonomic.zone/VtyrLUl9RWaJGgEDrncQUw?edit#
 
+## Next kite flying (open community meeting)
+
+[Schedule (ICS link)](https://coopcloud.tech/ics/kite-flying.ics) (subscribe in your calendar app)
+
+---
+
 ## 2026-02-12
 
 Here: p4u1, mo, apfelwurm

docs/federation/membership.md

@@ -8,7 +8,7 @@ title: Membership
 | --------- | --------- | -------- |-------- |
 | Agaric    | - | - | `@wolcen:matrix.org` |
 | [Autonomic](https://autonomic.zone) | - | - | `@3wc`, `@cas`, `@knoflook`, `@travvy`, `@aadil` |
-| [Bonfire](https://bonfirenetworks.org) | - | - | `@mayel:matrix.org` + Ivan (`@cambriale:matrix.org`) |
+| [Bonfire](https://bonfirenetworks.org) | ✅ | - | `@mayel:matrix.org` + Ivan (`@cambriale:matrix.org`) |
 | [Doop.coop](https://doop.coop) | - | - | `@yusf:gottsnack.net` |
 | [EOTL](https://eotl.supply) | - | - | `@basebuilder:pub.solar` |
 | [Karrot](https://karrot.world) | - | - | `@nicksellen:matrix.org` |
@@ -22,3 +22,4 @@ title: Membership
 | [MIR](https://mirnet.org/) | ✅ | - | `@sixsmith:matrix.org` |
 | [Red Abya Yala](https://abyayala.sutty.nl/) | - | - | `@fauno:sutty.nl` |
 | [Merri-bek tech](https://www.merri-bek.tech/) | - | - | `coop-cloud-delegate@merri-bek.tech`|
+| Amras | - | - | `coop-cloud@joinmeonmy.quest` |

docs/federation/organisers.md

@@ -26,7 +26,7 @@ We're still working out what it looks like to do this kind of work in the projec
 
 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, alternating between 12 and 19 UTC each week. We announce the hour via our socials: A [pinned toot](https://social.coop/@coopcloud/113555815289767778) on [`@coopcloud@social.coop`](https://social.coop/@coopcloud) and a post to the `#coopcloud:autonomic.zone` room.
+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:
 

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

@@ -0,0 +1,35 @@
+---
+title: "Resolution 039: Amras Ciaszczyk to join the federation as a member"
+---
+
+- Topic: Resolution 039: Amras Ciaszczyk to join the federation as a member
+- Date: 12-05-2026
+- Deadline: 26-05-2026
+- Size: large
+
+## Summary
+
+Amras maintains one of our recipes and facilitates half of kite-flying sessions, their membership will allow participation in the decision making and mutual accountability.
+
+## Details
+
+In Amras' own words:
+
+
+> I started using abra a few years ago, when I needed a stack to
+host services for my polycule. Last year, I talked with d1 at CCC and
+became more involved in the community. Since then, I've taken on
+facilitating the 12 UTC Kite Flying sessions and assigned myself as the
+mumble recipe's maintainer.
+
+> I'm also in the process of starting a small hosting, advice, and
+services provider under community-first and sustainability principles.
+
+> I'm already active in the Co-op Cloud community and on the periphery of
+a few organizing discussions. I'd like to formalize my role and become a
+bona fide member. My main motivation is to submit and vote on proposals
+related to the tasks I'm performing.
+
+@ammaratef45:matrix.org from [RTM](https://resisttechmonopolies.online/) is happy to vouch!
+
+To talk to Amras they are @amras0000:matrix.org and can be emailed at r039@joinmeonmy.quest

docs/maintainers/maintain.md

@@ -32,7 +32,16 @@ You can start by reading The Maintainers Proposal: [`R025`](https://docs.coopclo
 
 It is important that only recipe maintainers have write permissions to the repository. As it currently stands, every member of the [Co-operators Team](https://git.coopcloud.tech/org/coop-cloud/teams/co-operators) has write permissions to all recipe repositories for convenience while we are missing enough maintainers.
 
-To change this, create a new team on [`git.coopcloud.tech/coop-cloud/teams`](https://git.coopcloud.tech/org/coop-cloud/teams) for your specific recipe, e.g. `mycoolrecipe-maintainers`. Add yourself and any other maintainers and don't forget to add the recipe repository itself on the repositories tab. Remove your recipe repository from the [list of repositories for the Co-operators Team](https://git.coopcloud.tech/org/coop-cloud/teams/co-operators/repositories) so that write permissions are removed.
+To change this:
+
+1. Log into git.coopcloud.tech as an administrator account (e.g. `coopcloud`)
+2. Create a new team on [`git.coopcloud.tech/coop-cloud/teams`](https://git.coopcloud.tech/org/coop-cloud/teams) with the following settings:
+
+    - Name: e.g. `mycoolrecipe-maintainers`
+    - Repository access: Specific repositories
+    - Permission: Administrator access 
+3. Add maintainers as "Team Members" on the "members" tab, and add the recipe repository on the "repositories" tab 
+3. Remove your recipe repository from the [list of repositories for the Co-operators Team](https://git.coopcloud.tech/org/coop-cloud/teams/co-operators/repositories) so that write permissions are removed.
 
 ### Repository Permissions
 

docs/operators/tutorial.md

@@ -56,7 +56,7 @@ Abra can't deploy any applications in future steps unless it can run `docker` co
 groups | grep docker
 
 # if the docker group doesn't already exist, add it manually
-groupadd docker
+sudo groupadd docker
 
 # add user to docker group
 sudo usermod -aG docker $USER

mkdocs.yml

@@ -133,15 +133,16 @@ nav:
               - federation/resolutions/passed/031.md
               - federation/resolutions/passed/033.md
               - federation/resolutions/passed/034.md
+              - federation/resolutions/passed/035.md
               - federation/resolutions/passed/036.md
+              - federation/resolutions/passed/037.md
               - federation/resolutions/passed/038.md
           - "Stalled":
               - federation/resolutions/stalled/013.md
               - federation/resolutions/stalled/030.md
           - "In Progress":
               - federation/resolutions/index.md
-              - federation/resolutions/in-progress/035.md
-              - federation/resolutions/in-progress/037.md
+              - federation/resolutions/in-progress/039.md
       - "Minutes":
           - federation/minutes/index.md
           - "Recently":