2025-12-28
Coop-Cloud Meetup @ 39C3¶
Warning: this is no real protocol, since we did not really decide someone to write down something (and what), but it was my try to summarize the conclusive parts. For all attendees, please correct and extend on what i wrote here, if something is missing or wrong :)
Talk about Coop-Cloud¶
Simon and d1 are looking into the old state and maybe update it.
Alakazam workshop¶
Tomorrow 16:15 at the coop-cloud table.
Daily things with coop-cloud (what is nice, what not)¶
- Generally good experience
- SSO stuff is cumbersome
- Keeping an eye on recipe changes is a bit hard
- Onboarding for new users could be easyer
- Catalog has structural problems
- All are using several workarounds
- Upgrading a recipe is cumbersome (there is a proposal to make that better, just has to be implemented)
More cooperation in general/ reflect on kiteflying / talk about finances:¶
- Me try to do it once a month with more static topics
- The radmin role would maybe help to fix to get people payed for stuff through that
- Draft from p4u1 and d1
- Maybe a proposal gets made by kawaiipunk to rise the wage for internal tasks (discussions will follow to refine that idea)
- We want to implement the maintainers proposal to more recipes
- We should implement default guidelines for cooperation/contribution for the recipes, which can be "overwritten" by each reipe maintainers
- We want to experiment with automated testing, for recipes, here it would be great to have some kind of a defined list of what should be tested
- Maybe we could implement a language server for abra
- Idea: Workaround sharing session or blog write ups about the workarounds used
- Idea: move away from the env file in the future via defining a standard over alakazam without breaking the env (like upstream alakazam)
Political Statement in the Documentation¶
d1 puts survey answers to a text and then we work together and decide it in a kiteflying.