toolshed/organising
toolshed/organising
8
1
Fork 0
Code Issues 120 Pull Requests Releases Activity

difference between the 'who is involved' and 'Who’s already using co-op cloud?' #333

New Issue
Open
opened 2022-07-05 14:48:25 +00:00 by trav · 2 comments
trav commented 2022-07-05 14:48:25 +00:00
Member
Copy Link

the difference between the 'who is involved' and 'Who’s already using co-op cloud?' sections on the website aren't clear. They don't seem like distinct categories to me

the difference between the 'who is involved' and 'Who’s already using co-op cloud?' sections on the website aren't clear. They don't seem like distinct categories to me
👍 1
decentral1se commented 2022-07-18 09:02:14 +00:00
Owner
Copy Link

@trav good point, any suggestions? My initiali thought is that it might be good to separate "user members" from "hoster members" wrt. the federation model we're approaching. But we're not quite there yet... in the meantime, maybe we could just edit these titles to be more clear. "Users of Co-op Cloud" / "Democratic tech collectives"?

@trav good point, any suggestions? My initiali thought is that it might be good to separate "user members" from "hoster members" wrt. the federation model we're approaching. But we're not quite there yet... in the meantime, maybe we could just edit these titles to be more clear. "Users of Co-op Cloud" / "Democratic tech collectives"?
trav commented 2022-07-18 16:48:33 +00:00
Author
Member
Copy Link

yeah I guess "Users of Co-op Cloud" / "Democratic tech collectives" separation makes sense. But yeah once the fed is happening more then "user members" / "hoster members" seems a more apt separation.

yeah I guess "Users of Co-op Cloud" / "Democratic tech collectives" separation makes sense. But yeah once the fed is happening more then "user members" / "hoster members" seems a more apt separation.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
abra-gandi
Abra Gandi plugin
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
democracy
Democratic decision making
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
kadabra
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
recipes.coopcloud.tech
Our recipes catalogue
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas decentral1se fauno kawaiipunk knoflook lambdabundesverband moritz p4u1 simon trav val yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#333
No description provided.
Delete Branch "%!s()"

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?