-
This is based on the rOpenSci code reviews: https://devguide.ropensci.org/
@zkamvar and @finlaycampbell are assigned.
-
Submitting Author Name: William Gearty
Submitting Author Github Handle: @willgearty
Other Package Authors Github handles: (comma separated, delete if none) @sckott, @maelle
Repository: https://git…
-
```md
{fig-alt="Localization process cicle: we create a Pull Request with the first automatic translation, that translation get tw…
-
Based on this aborted post: https://github.com/ropensci/onboarding/blob/90fa3e86d20180ed92371ee649e217209d5e588d/posts/2017-01-16-year-in-reviews.Rmd
-
Submitting Author Name: Øystein Sørensen
Submitting Author Github Handle: @osorensen
Repository: https://github.com/LCBC-UiO/galamm
Version submitted: 0.1.1.9000
Submission type: Stats
Badge…
-
@noamross Really like your suggestion about including a bit more about the review. Trying to think how best to do this using existing vocabularies, since it makes interoperability of data so much eas…
-
@mpadge (& others) do you think it'd make sense to have a reminder for the author response 12 days or so after both reviews are in?
It'd however require a way to detect the author response once it'…
-
As @jeroen pointed out today, it would be more scalable and potentially more effective to enforce security a the user level rather than for each package.
We could think about this in terms of how …
-
I recently participated as a reviewer in the [rOpenSci onboarding](https://github.com/ropensci/onboarding) process for Open Science related R packages. It got me thinking about whether ACEMS could pro…
-
e.g., here https://github.com/ropensci/onboarding/issues/23 pinged using both reviewers handles, but one had already submitted a review, but other hadn't