Add fields for users/maintainers in recipes.json / recipe metadata? #307
Closed
opened 2022-04-01 10:45:58 +00:00 by decentral1se
·
3 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#307
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.mdalongside the Category, Status, etc.abrato 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