4 Commits

Author SHA1 Message Date
e54ec4b121 Merge branch 'main' into mayel-patch-4 2026-05-06 12:04:23 +00:00
ab65f6bed7 Merge pull request 'add sudo in front of group add' (#1) from mayel-patch-1 into main
Reviewed-on: #1
2026-05-06 10:18:15 +00:00
51e9145b96 Update docs/federation/organisers.md 2026-05-06 10:15:53 +00:00
807370bdd7 add sudo in front of group add
otherwise fails in some scenarios
2025-10-01 15:33:34 +00:00
3 changed files with 2 additions and 8 deletions

View File

@ -4,12 +4,6 @@ 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

View File

@ -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:

View File

@ -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