Community organising strategy? #79
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#79
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?
Some ideas in the air:
We probably want a Code of Conduct then also? (#80)
I've been checking out some other projects in general:
Got others?
Does anyone know any folks who would be good to chat about this stuff with? I've always admired the work of https://decentpatterns.xyz/work-with-us/ and would love to see if they'd work with us.
Some others:
Same as #83 (comment) we've got a number of ways we are organising with others like matrix/fedi/blog/autonomic network etc. so I will close this off.