Improving new Recipe onboarding #571
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#571
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?
In the recipes-wishlist I created
.gitea/issue_template/recipe.mdso people filing issues get a nice little text when adding a new Recipe Wish. Similar to thisorganisingrepository.The template also prepopulates the issue with the markdown which ends up in the
README.mdfile in the future recipe. To see this text click here.This might not be best template text. But I figured when looking at the issues people are filing, things could be made more explicit structured as it will slightly reduce work for maintainers.
Seems a bit much for a wishlist template tbh. I thought the format of coop-cloud/recipes-wishlist#26 was pretty accessible. Being a maintainer is hard but also you're in a better position to answer those metadata questions after you've been in the config trenches. Might scare people off throwing in good recommendations? Some thoughts.
Yah, I agree. I was a bit carried way. Thanks for the sanity check 🤣
I also went absolutely wild on the Gitea templates when I first found them. Then I deleted them all 🙃 With great power comes unexpected waves of galaxy brain impulses. Dog bless us all.