Coopcloud Meeting August¶
Agenda¶
- Federation Stuff / Current state
- Funding for Maintenance work
- Design Operator Collaboration https://git.coopcloud.tech/coop-cloud/organising/issues/467
- HOWTO finish Restore https://git.coopcloud.tech/coop-cloud/backup-bot-two/issues/42
Introductions¶
-
Moritz (Local IT): merging with Make IT Social (another collective), Maintanining Recipes, Maintainig Backupbot, Small fixes in the abra tool
-
p4u1 (Klasse & Methode): maybe starting a workers collective, maintaning some recipes and created a new one (for internal use for now), introduces abra config and a step towards operator collaboration
-
basebuilder (eotl): deep in eotl, trying to get stable releases out, abra recipes for both exists, in november / december some spare cycles for coopcloud, nlnet grant was rejected
Funding Maintenance Work¶
a good idea by d1, would be nice if we can get one or two persons to commit to this. local it might have some resource at the end of the year. could also fund people for just one or two months (instead of per feature)
5000€ in bank account. 10 hrs for orga and 20 hrs for hacking = 600€. would result into about 8 months paid work
- write a propsal @p4u1
- ask people if they can commit @everyone asks in their collective
Backupbot¶
-
spec: https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/pulls/258
-
what to do if multiple backupbot.backup=false / true
- backupbot will ignore false if true was set
-
add recipe lint
-
How to enable / disable per app
-
backupbot.backup=${BACKUPBOT_ENABLE:-true}
-
Backup can't be used without backupbot
-
it's ok for now, can also implement it later
-
Whats left
-
restore and some backup labels
-
restore is tryicky to implement automatically
-
for database e.g. other connections to it should be stopped
-
backwards compatible?
-
introduce a new version label
-
moritz is going to implement the specification
Next Meeting¶
- @moritz poll for lasst 2 weeks in september