From 3900fba85a6ab9fcf177d2cb135f54c2d19794a9 Mon Sep 17 00:00:00 2001 From: Apfelwurm Date: Thu, 12 Feb 2026 14:34:07 +0100 Subject: [PATCH] add Resolution 037: Adopt alakazam as an official project in the Co-op Cloud Federation --- .../federation/resolutions/in-progress/037.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/federation/resolutions/in-progress/037.md diff --git a/docs/federation/resolutions/in-progress/037.md b/docs/federation/resolutions/in-progress/037.md new file mode 100644 index 0000000..60501ed --- /dev/null +++ b/docs/federation/resolutions/in-progress/037.md @@ -0,0 +1,26 @@ +--- +title: "Resolution 037: Adopt alakazam as an official project in the Co-op Cloud Federation" +--- + +- Topic: Resolution 037: Adopt alakazam as an official project in the Co-op Cloud Federation +- Date: 12-02-2026 +- Deadline: 26-02-2026 +- Size: medium + +## Summary + +We want to adopt the abra wrapper Alakazam (https://git.coopcloud.tech/moritz/alakazam) , which is used by KolliCloud (https://kollicloud.de) as an official project in the Co-op Cloud Federation + +## Details + +As we already disscussed on our Meetup and the Alakazam workshop at 39C3 end of 2025, we want to adopt the abra wrapper Alakazam (https://git.coopcloud.tech/moritz/alakazam), which is used by KolliCloud (https://kollicloud.de) as an official project in the Co-op Cloud Federation. This way, we want to start collaborative effort on teaching, writing docs, writing tests. + +This includes the following (in the long run): + +* tranfering the Alakazam repository to https://git.coopcloud.tech/toolshed +* creating a space in the docs for alakazam and moving the contents of the readme and the nessecary contents of https://wiki.local-it.org/s/kollicloud-wiki/doc/installation-wVp2LfBbg7 +* get others to try alakazam (future Kite-Flying sessions for this) +* write tests for alakazam +* implement the option to use more than one deployment of the same application in one instance +* migrate alaconnect.yml files for the recipe (we have to figure out how multiple instances would allow this in regards to the multiple same apps in one instance) +* migrate the features (that makes sense) into abra