-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog post illustrating/promoting codemetar #118
Comments
The blog post should make clear this is all about packages metadata and mention tools aimed at improving other aspects of packages such as |
post-unconf I'm guessing we will have 2-3 weeks of almost exclusively unconf posts then we can fit this one in when we like |
I'm thinking of two tech notes:
|
And maybe a first one presenting #20 because if we do that on json-ld repos it's a good way to explain json-ld at the same time... |
I think that after next release, @cboettig's whybother.Rmd would make a good basis for a short tech note. |
:-) happy to work on that with you! we promised to do something like that long ago, but I feel we're only finally getting to the point where the answer is a bit more convincing. (though would be even better if zenodo also does their integration like it says for Q3 2019 target, but at least now there's SoftwareHeritage!) cc @mbjones |
any news about Zenodo? |
Nope; still watching zenodo/zenodo#1504 though. 👀 👀 |
Just a note on phrasing I was thinking about. codemetar converts local package metadata of the package to a standard format, whilst also enriching it using web data resources when online. |
Also, it is quite obvious, but having good package metadata is good in general so the opinions giving by codemetar is not useless. |
Following a discussion with
codemetar
CEO @cboettigOnce I've started using @sckott's tool that has a copy of all ropensci repos a blog post would
briefly present Codemeta &
codemetar
explain how we (plan to) use it for the registry (and pre-registry building quality checks)
an example aimed at attracting a larger readership, using
extract_badges
over all READMEs of CRAN packages that have a GitHub repo listed under Repository in DESCRIPTION.The title could be "Manage and promote a herd of packages with codemetar" or a better verb than promote, this verb should reflect the goal of Codemeta.
Cc @stefaniebutland, when would it fit in the blog schedule? I'm not sure I'd have written it before unconf.
The text was updated successfully, but these errors were encountered: