Add fields for users/maintainers in recipes.json / recipe metadata? #307
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#307
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?
Right now on https://recipes.coopcloud.tech/recipes.json (which will soon have a web UI @ https://recipes.coopcloud.tech) you can't tell who is using the recipe & who is maintaining the recipe.
This would be super useful to have in the JSON blob with a name & potentially contact details (matrix handle, email?) so that people considering to use the recipe could get in touch with those already using it and/or taking care of it!
This would help facilitate more direct connects between potential users/maintainers. People could just freely get in touch & see how to best to co-operate on keeping the recipe going.
How would this work?
bca2a983c0/README.md
alongside the Category, Status, etc.abra
to parse that and add it to the recipes.jsonProposals for README format?
/cc @3wordchant
This would be really good to have IMHO
Yep sounds like a fantastic proposal @decentral1se, no notes