Gathering federation proposal feedback thread #311
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#311
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
from
@yusf
:Great stuff! ❤️
Some feedback/suggestions:
FYI @trav @3wordchant
I think one of the aims of the federation should be to coordinate paid work on coop cloud things.
Also I feel like the process as far as setting up should involve a ratification or at least a concedement of some sort of foundational document derived from the proposal.
@mayel whoa great suggestions. The difference between consensus and consent-based decisions is still a little fuzzy to me. I believe the aim of the Co-op Cloud federation proposal is to bootstrap with a minimally complicated system so that everyone can quickly grok the structure and voting procedure.
Agree with this, tracking down abstains is going to be arduous so this makes sense to add.
and
@cas
this is crucial! The overall budget will be quite shoe-string so it will be important to discuss how the funds ought be dispersed.