Skip to content
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

Closed
maelle opened this issue Apr 25, 2018 · 10 comments
Closed

Blog post illustrating/promoting codemetar #118

maelle opened this issue Apr 25, 2018 · 10 comments
Assignees
Milestone

Comments

@maelle
Copy link
Member

maelle commented Apr 25, 2018

Following a discussion with codemetar CEO @cboettig

Once 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.

@maelle
Copy link
Member Author

maelle commented Apr 25, 2018

The blog post should make clear this is all about packages metadata and mention tools aimed at improving other aspects of packages such as lintr (+ styler) and goodpractice.

@maelle maelle self-assigned this Apr 25, 2018
@stefaniebutland
Copy link
Member

Cc @stefaniebutland, when would it fit in the blog schedule? I'm not sure I'd have written it before unconf.

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

@maelle
Copy link
Member Author

maelle commented Nov 6, 2018

I'm thinking of two tech notes:

  • one explaining the new packages page setup when it's finished (getting closer)
  • one playing with the big codemeta.json of all packages like what @cboettig did in the vignette/article of a package (was it codemetar?).

@maelle
Copy link
Member Author

maelle commented Nov 8, 2018

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...

@maelle
Copy link
Member Author

maelle commented Nov 27, 2019

I think that after next release, @cboettig's whybother.Rmd would make a good basis for a short tech note.

@cboettig
Copy link
Member

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

@maelle maelle added this to the 0.1.9 milestone Jan 8, 2020
@maelle
Copy link
Member Author

maelle commented Jan 8, 2020

any news about Zenodo?

@cboettig
Copy link
Member

cboettig commented Jan 8, 2020

Nope; still watching zenodo/zenodo#1504 though. 👀 👀

@maelle
Copy link
Member Author

maelle commented Mar 11, 2020

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.

@maelle
Copy link
Member Author

maelle commented Mar 11, 2020

Also, it is quite obvious, but having good package metadata is good in general so the opinions giving by codemetar is not useless.

@maelle maelle pinned this issue Apr 2, 2020
@maelle maelle mentioned this issue Apr 2, 2020
21 tasks
@maelle maelle modified the milestones: 0.1.9, 0.2.0 release Jul 21, 2020
@maelle maelle closed this as completed Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants