coop-cloud/docs.coopcloud.tech
coop-cloud
/
docs.coopcloud.tech
4
1
Fork 14
Code Issues Pull Requests 2 Releases Activity

add minutes for 2023-05-03 and 2024-02-01

This commit is contained in:
basebuilder 2024-02-22 19:51:38 +01:00
parent 4c778a154f
commit 3455295f9f
3 changed files with 165 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
docs/federation/minutes/2023-05-03.md Normal file
View File

@ -0,0 +1,82 @@
---
title: 2023-05-03
---
# Co-op Cloud Federation Meeting 2023-05-03
Notes from last meeting: https://docs.coopcloud.tech/federation/minutes/2022-03-03/
Metadata
* Time / date: May 3 @ 1500-1630 UTC https://time.is/0330PM_3_May_2023_in_UTC
* Location: https://meet.jit.si/coop-cloud-federation-meeting
* Attending: Autonomic (trav, 3wc), Local-IT (yksflip, Moritz), decentral1se (🐺 /free agent)
* Facilitation: Calix
* Notes: trav
Agenda
_(All times UTC, as sharp as possible)_
* Introductions / checkins (5m)
* How you're doing
* Which organisation are you attached to? (if applicable)
* a fun (or terrible) Co-op Cloud experience you've had recently
* Packaging Rustdesk server 🥳
* Realising backupbot labels didn't work 😱
* Upgrading with missing backups 😅 Deployed 18-20 apps at once, wrote a script 🤯
* Immovable force meets unstoppable bug, no deployments ⛔
* Decisions - what passed, any new proposals? (10m) https://docs.coopcloud.tech/federation/resolutions/
* we review the existing resolutions
* Resolution 005 / process
* trav: sticking to 2 week deadline for proposals?
* d1: there was a meeting where we talked about it being a small decision but then it became medium. G
* trav: ahh mixups happen, I don't feel strongly ultimately.
* yksflip: maybe check-in with cas but call it passed (?). 2 weeks is a good amount of time but can understand you'd want to move on more quickly.
* 3wc: 2 week default good. Very async coordination, espeically if folks have to go back to their co-op to check-in. Fewer people will see it the shorter it is.
* Moritz: how to know size of the decision?
* 3wc: smallest decision size that seems fair.
* d1 in chat: 'who is affected by the decision'
* d1: 2 weeks seems good, simpler to stick to that going forward. Super duper emergency budget
* What does the second point of Resolution 004 mean
* 3wc: first Budget is a budget for these meetings.
* Superduperemergencybudget
* Trav: For emergency work?
* d1: yes, but the part that's missing is to know what is super duper emergency. There are a lot of P1 bugs but they're not all show-stoppers. There are a number of things that need to be fixed quicker than 2 weeks
* 3wc: emergency firefighter. Up to whoever proposes the budget as to what the structure would look like.
* abra fixes Budget / proposal thingy
* https://pad.autonomic.zone/Fp6Zi846TNqATulYFqcJqw
* d1: if this was proposed today, wait 2 weeks and then I'd fix them. Or standing budget?
* trav: suggestion is wait 2 weeks then implement? or agree standing budget?
* 3wc: yes, but also passing emergency budget would also take 2 weeks, no?
* d1: propose this and do 10 hours or do a "10 hours" proposal and fit this into it. Not show-stopping bugs but 2 weeks wont kill us.
* trav: might be worth passing 10h/mo, something/month for fixes, maintenance / emergency. non-binding poll / gitea voting → what to work on. vs having to package bug work together. less bureaucracy.
* d1: can re-work decision 6 into a maintenance budget. Curious how we want to bubble-up the bugs. Board? Label?
* yksflip: standing maintenance makes sense to me.
* federation bootstrap funds 🤑
* trav: there's money leftover from donor
* d1: 6k in the pot, get the work funded.
* trav: buffer tho?
* Moritz: I'm paid from Local IT. How to decide who is doing which fixes?
* d1: people tend to do stuff they want to see done. Some way to share would be good....?
* 3wc: tags. Tickets labeled as part of maintenance budget. If assigned to someone, they are point person. Plot twist: time expectation. Someone takes something on and it's unclear when that's going to happen. Claim things for up to a week or 2 but don't claim it until you're ready to work on it.
* ** we love it **
* **d1 to roll into maintenance proposal**
* doop coop dues waiver https://pad.autonomic.zone/xgd7lLxzT520O4KRXuWyuQ#
* 3wc: yusef posted, side project, low income, would like to participate. 1 year waiver of dues. They seem enthusiastic and helpful person to be around.
* trav: can decide now? " Individuals/groups wanting to join Co-op Cloud who aren’t able to make a financial contribution may request a solidarity free membership." doesn't say how to make decision
* d1: medium seems fine
* Moritz: instead of dues perhaps doing some abra fixes
* Philip: agree on waiving fees for them. How to define time to spend on project. Alternative membership fee, donate time?
* 3wc: part of inspiration for fedration is Co-op Cycle: too complicated to track work and money. Have to track money so wont track work. Like the simplicity. Wage is €20/h, in-kind work contribution would be 30 minutes of work contribution per month.
* d1: reflecting on unions etc, pay dues and also contribute. Something to think about.
* Checkouts
didn't get to:
* Breakout groups?
* Software tools
* Finances
* Outreach
* Development
* next meeting? Is it monthly? I forget.

79
docs/federation/minutes/2024-02-01.md Normal file
View File

@ -0,0 +1,79 @@
---
title: 2024-02-01
---
# Co-op Cloud Federation meeting 2024-02
Date poll: https://crab.fit/coop-cloud-federation-february-2024-576238
Previous notes: https://docs.coopcloud.tech/federation/minutes/2023-05-03/
## Agenda
- check-in
- name
- pronouns
- organisation
- how we're feeling
- anything we want to get out of today
- emotional support for abra bugs
- missed october 2023 membership dues review ([R002](https://docs.coopcloud.tech/federation/resolutions/passed/002/)), what now?
- [backup restore / testing update](https://pad.riseup.net/p/UEC2JUPGb6tmRCZ7RX9X-keep)
- collective abra next release planning
- ✅ bonfire co-op network hosting proposal
- ✅ next meeting
- check-out
- how was the meeting?
- recommendations for next meeting
- what are you doing for the rest of the day?
## Notes
Here: Calix, Mayel, Moritz, p4u1, d1
Facilitating: Calix
Notes: Mayel
- local-it has test framework with Playwright to test deployment, eg. testing customised configs or modified recipes - not testing app functionality but rather customisation or integrations between apps, eg. SSO - so can check if an upgrade would break - would be nice to integrate the tests into the recipes to they can be linked to the version (ie. update recipe when updating a recipe/app) - in future want to automate into CI (eg drone runner) to auto-update recipes and check for failure - will publish test framework next week on coopcloud gitea - run them first on test deployments to check in advance if update works but also then run in prod to make sure thing runs correctly in prod (eg. if email notifs are working in each app) - this does require extra thinking (eg. deleting data created by tests)
- sounds really cool! going to look into playwright. could be handy for federated apps
- sounds like something that orgs like nlnet may fund, maybe can merge these into a proposal to fund this + the more boring coopcloud maintainance
## organise meeting schedule
- would be nice to find a regular rythm for federation meetings instead of needing date polls
- same time? once a month?
- in social.coop TWG they've been getting 2-3 people showing up, maybe just because haven't polled for new regular meeting time for a while
- need someone with capacity to organise (coordination role), whether it's setting up poll or prompting people to join, to get us all in the room
- will someone set up a date poll for march? or re. meeting frequency / how we decide -> Moritz volunteered
### bonfire co-op network hosting proposal
- https://bonfirenetworks.org/hosting/
what co-op cloud combined with servers.coop would do. idea comes from a need from bonfire team, people who are looking to adopt bonfire, individuals, small collectives, large organisations who might not have tech savvy to set up and maintain own hosting / instances, would rather have as a service .. but we decided early on we didn't want to offer hosting ourselves. and we don't want to host any flagship instances (because centralisation). calls for easy way for people to set up and maintain instances. not just infrastructure, labour, savvy, mnaintenance and support, backups. like community-supported agriculture, "community-supported software" = community gets a say in software, have a say in prioritising. large part of funds goes into infra and labour of maintaining / operating. split among participants.
last funding from NLNet, included milestone. prototype instance setup wizard and management dashboard. €3k to start. small tech component, organisational and infra.
what would m like from CC at this stage?
participants help with prototyping
start small - organisational & infrastructural side is
communities already want instances!
not setup wizard required, just send us an email etc. do it by hand
budget avail now
one group focused on open science, one on digital radios, online communities around music. possibilities of them finding grants, other sources of income. donations from community members? assume = there would be funds eventually. might have to be a bit of upfront freebie service, especially as we're prototyping. closed beta as we're trying things out.
### missed october 2023 membership dues
- we were going to review who's paying, how's the amount. we didn't! what to do.
### backup restore / testing update
- after meeting about backup bot in januarry, need to document what already exists and what has been decided, there was a proposal - will followup async
### collective abra next release planning
- some are in process of improving backup/restore (still WIP) and some bugs were also found, so now it's difficult to make a release - many are self-building abra so not an issue for them, but would be good to make a plan first (next time) to avoid large refactors that block releases
- also plan around how long features take to implement, maybe during federation meetings
- proposal for next abra release: some bugs are fixed in main branch but release blocked by backup stuff, so could create a new branch from point where backup stuff was not merged and create release from there, so don't need to worry about incomplete backup stuff, should be pretty easy, that way can finish backup with no rush
- if we do so, need 1 or 2 people to run integration tests + fix any bugs that appear and then do the release - ideally 1 person who has released before (d1 volunteers) + another who hasn't (p4u1 volunteers)
## check out
- in future need to talk about how long meeting can go before starting + agenda prioritisation

4
mkdocs.yml
View File

@ -128,6 +128,10 @@ nav:
- federation/minutes/index.md
- "2022":
- federation/minutes/2022-03-03.md
- "2023":
- federation/minutes/2023-05-03.md
- "2024":
- federation/minutes/2024-02-01.md
- "Digital Tools": federation/tools.md
- "Glossary":
- glossary/index.md