Review info in codemeta.json

[maelle]

@ropensci/editors

For onboarded packages codemeta.json will include review metadata, a minima review URL + rOpenSci as provider.

Now in ropensci/codemetar#23 (comment) @cboettig says "it would be natural to include the review author & editor here too". Technically we could get this information from GitHub (and even have a pre-digested table somewhere on GitHub, not only the private Airtable) but do we want to have reviewers and editor(s) listed in codemeta.json given that we ask reviewers for authorization before including them in DESCRIPTION?

[sckott]

I think it's okay to include them.

[karthik]

I think this could be a checklist item so that we have consent. For editors it would be easy since there are only 4 of us.

[maelle]

Ok so the digested open table would take that into account.

And for past reviews, would we try and contact former reviewers or just not include them?

[noamross]

I sort of think its fine to include them without asking. For DESCRIPTION files, there's a little more implication by including people in the Author: field that they are "participants", even with the 'rev' role. But in codemeta.json, the Review is a separate field. I'd only ask reviewer permission if we were to include additional contact information.

[maelle]

Cool, now I just need to think of how/where to make the digested table Review number, Reviewers, Editor available for everyone.

[maelle]

To be generated from the Airtable to a public csv

• one line by package, or one line by person involved editor/reviewer
• package name
• onboarding issue URL/issue number
• editor name and GitHub username
• reviewer1 to reviewerN (reviewer4?) name and GitHub username
• approved or not (i.e. when the badge is green, no info added to codemeta.json before that)

Currently the review deduced from an rOpenSci peer-review badge includes only provider and URLs, cf https://github.com/ropensci/codemetar/blob/387456e9d62fdb9be936a089d7173e8d21d783b8/codemeta.json#L451 but with such info it'll include "editor" and "author" (= reviewers), each person will have a name and URL (GitHub profile).

[maelle]

@karthik could you start by making the information you use for the badges available as an API? So that I could query it with an issue number, and it'd return me the status (instead of my asking GitHub API). In the packages/ page I'd like to be able to assign the right badge color without using a badge.

[karthik]

Sure, let me work on that

[maelle]

A csv dump would be just fine, I'd memoise it

[karthik]

Sure, I can also do a json dump if that's easier

[maelle]

as you prefer

[maelle]

@karthik in https://badges.ropensci.org/json/onboarded.json the entry 127 lacks a pkgname. It's googleLanguageR