Gathering federation proposal feedback thread #311

New Issue

2022-04-15T15:14:32Z

decentral1se commented

2022-04-15 15:14:32 +00:00

No description provided.

decentral1se commented

2022-04-15 15:14:48 +00:00

from @yusf:

An eyebrow was raised upon reading the 4th aim:

Create a support and knowledge sharing network to make setting up new co-operatives easier.

I suppose it should say "setting up new hosting co-operatives easier" or are there wider ambitions at play?

from `@yusf`: > An eyebrow was raised upon reading the 4th aim: > > > Create a support and knowledge sharing network to make setting up new co-operatives easier. > > I suppose it should say "setting up new **hosting** co-operatives easier" or are there wider ambitions at play?

decentral1se added this to the Beta release (software) project 2022-04-15 15:15:13 +00:00

mayel commented

2022-04-17 22:56:49 +00:00

Great stuff! ❤️
Some feedback/suggestions:

Any thoughts on consensus vs consent based decisions? (as in sociocracy) Actually some of the processes laid out feel more sociocratic than consensus-based already.
How about a suggestion to use score voting when appropriate? (for example using https://ukuvota.world) so participants can weigh different options rather than proposals always being a yes/no decision
I'd include a deadline for Maximum Consensus decisions as well (with no shows counting as abstains), as you'll probably find it more difficult to chase down participants when dealing with a federation compared to a tight knit co-op.
Maybe adding a non-aims section, to clearly define the scope of the project.
There seems to be no mention of the economic aspects of the project/federation, like the labour/sustainability of maintainers / hosters / app developers / community gardeners, the hardware, the infrastructure services, and the distribution of value among all these moving parts. Or if out of scope clarifying that as a non-goal.

Great stuff! :heart: Some feedback/suggestions: - Any thoughts on consensus vs consent based decisions? (as in sociocracy) Actually some of the processes laid out feel more sociocratic than consensus-based already. - How about a suggestion to use score voting when appropriate? (for example using https://ukuvota.world) so participants can weigh different options rather than proposals always being a yes/no decision - I'd include a deadline for Maximum Consensus decisions as well (with no shows counting as abstains), as you'll probably find it more difficult to chase down participants when dealing with a federation compared to a tight knit co-op. - Maybe adding a non-aims section, to clearly define the scope of the project. - There seems to be no mention of the economic aspects of the project/federation, like the labour/sustainability of maintainers / hosters / app developers / community gardeners, the hardware, the infrastructure services, and the distribution of value among all these moving parts. Or if out of scope clarifying that as a non-goal.

decentral1se commented

2023-01-18 17:54:59 +00:00

FYI @trav @3wordchant

decentral1se modified the project from Beta release (software) to Federation & abra fixes

2023-01-18 17:55:10 +00:00

cas commented

2023-01-25 19:07:59 +00:00

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.

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.

trav commented

2023-02-16 15:13:26 +00:00

@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.

I'd include a deadline for Maximum Consensus decisions as well (with no shows counting as abstains), as you'll probably find it more difficult to chase down participants when dealing with a federation compared to a tight knit co-op.

Agree with this, tracking down abstains is going to be arduous so this makes sense to add.

There seems to be no mention of the economic aspects

and
@cas

I think one of the aims of the federation should be to coordinate paid work on coop cloud things.

this is crucial! The overall budget will be quite shoe-string so it will be important to discuss how the funds ought be dispersed.

@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. > I'd include a deadline for Maximum Consensus decisions as well (with no shows counting as abstains), as you'll probably find it more difficult to chase down participants when dealing with a federation compared to a tight knit co-op. Agree with this, tracking down abstains is going to be arduous so this makes sense to add. > There seems to be no mention of the economic aspects and @cas > I think one of the aims of the federation should be to coordinate paid work on coop cloud things. this is crucial! The overall budget will be quite shoe-string so it will be important to discuss how the funds ought be dispersed.

decentral1se closed this issue

2023-04-10 21:42:15 +00:00

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#311