I have a question with regard to updating the various recipes. I’m working at EPFL in Switzerland, at C4DT, and we’re currently looking into sovereign solutions for web services.
I put together an example at https://cloud.c4dt.org with various recipes. I really appreciate all the work which has been done here. The tradeoff between usability / flexibility of coop-cloud is unique, from what I saw. However, a lot of recipes are old - jitsi (> 1year), nextcloud is a bit behind (trying to get involved there), and others.
I’m a programmer since 1981, but I really appreciate what LLMs can do. So a lot of the code I’m writing nowadays comes from LLMs. But I know that some people think that LLMs are devil’s work (well, they are…), and don’t want to touch them. So my question is this:
would you appreciate me getting more involved over the coming months in updating various recipes by carefully proposing PRs done by LLMs, and tested on our server? Or is that a no-go for you?
I cannot promise I’ll hang around for long. We’re currently looking at various ways of deploying things, and I couldn’t convince everybody yet with the good foundation of coop-cloud 
But having all these people writing docker-compose files in their corner is definitely sub-optimal. So if something like coop-cloud can become a collection of up-to-date and easy-to-deploy repository of docker-compose files, that would be awesome!