Contributor documentation improvement thread #116
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#116
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?
Making https://docs.coopcloud.tech/contribute/#compensation-for-contributions better.
Ways to mark tickets that can be worked on, are prioritised, waiting time estimates etc. and create more autonomy for people who have already contributed, got paid and want to get on with doing things they find fun and are useful to the project direction.
Also see #87.
re: #116 (comment) @knoflook since you're picking up a bunch of work right now, we could focus on your experiences so far and try to design a handier way of distributing work based on that? Could be discussed tomorrow or soonish!
i'll be happy to do that :) tomorrow is fine for me!
https://docs.coopcloud.tech/get-involved/