Open sckott opened 4 months ago
I agree with this proposal, with a couple of clarifications:
wilds-comp
as the topic tag. @monicagerber are you okay with this?wilds-nf
for nextflow.wilds-comp
. wilds-nf
Agree!
Okay, registry repo is started https://github.com/getwilds/registry - super basic for now
@seankross let me know any thoughts on the registry repo above when you get a chance
WILDS needs consistent metadata across repos within WILDS to be able to improve discovery for users and ourselves via a) github itself, and b) the getwilds website.
At least for me it's important to be able to add/remove/edit/update metadata programmatically. We may not have a lot of repos now, but when we do we will regret using tooling that's manual only
How to metadata?
wilds
prefix to the topics is that topics can be anything, so e.g. a repo could formally be a Dockerfile repo, but have some R code in it - someone may apply a topic liker
orrstats
, etc. to that repo in which case we wouldn't know whether this was really a docker repo or an R repo. So repos can have any topics they like but need to have some exact topics we control so that we can easily identify the different types with code instead of humanswilds-r
: for an R packagewilds-py
: for a Python packagewilds-docker
: for a Dockerfile, or set of fileswilds-comp
: for a Research Compendiawilds-wdl
: for a WDL workflowwilds-nf
: for a Nextflow workflowgh
cli tool usinggh repo edit
with flags--add-topic
/--remove-topic
(docs)/repos/{owner}/{repo}/topics
route with the github api (docs)codemetar
, in particular extract_badges - but there's similar tooling in other languages https://codemeta.github.io/tools/(optional - but I think is kinda the best way to package up metadata across repos)