diff --git a/booknews.Rmd b/booknews.Rmd index 99a3a9cd7..c78ae317e 100644 --- a/booknews.Rmd +++ b/booknews.Rmd @@ -2,9 +2,9 @@ ## Dev version +- 2026-06-25, add note for editors that authors should record their responses (#1021, `@robitalec`) - 2026-06-12, clarify expections for volunteer form for eds and revs (#1015; thansk to @joelnitta) - 2026-06-25, clarify manual removal of holding label (#1020, `@robitalec`). - - 2026-05-21, better document reviewer search in Airtable (#1009, #1010). - 2026-06-12, add mention of testit (#1014). - 2026-05-29, link in reviewer guide to stats template for stats reviews (#1012) diff --git a/softwarereview_author.Rmd b/softwarereview_author.Rmd index dd720ee7b..06144c55d 100644 --- a/softwarereview_author.Rmd +++ b/softwarereview_author.Rmd @@ -81,7 +81,7 @@ If you intend to submit an accompanying manuscript for your package, rOpenSci ha - An [editor](#editors) will review your submission within 5 business days and respond with next steps. The editor may assign the package to reviewers, request that the package be updated to meet minimal criteria before review, or reject the package due to lack of fit or overlap. - If your package meets minimal criteria, the editor will assign 1-3 reviewers. They will be asked to provide reviews as comments on your issue within 3 weeks. -- We ask that you respond to reviewers' comments within 2 weeks of the last-submitted review, but you may make updates to your package or respond at any time. Your response should include a link to the updated [NEWS.md](#news) of your package. Here is [an author response example](https://github.com/ropensci/software-review/issues/160#issuecomment-355043656). Once the response is commited, [submit it using the bot](bot_cheatsheet.html#submit-response-to-reviewers). We encourage ongoing conversations between authors and reviewers. See the [reviewing guide](#reviewerguide) for more details. +- We ask that you respond to reviewers' comments within 2 weeks of the last-submitted review, but you may make updates to your package or respond at any time. Your response should include a link to the updated [NEWS.md](#news) of your package. Here is [an author response example](https://github.com/ropensci/software-review/issues/160#issuecomment-355043656). Once the response is commited, [submit it using the bot](#submit-response-to-reviewers). We encourage ongoing conversations between authors and reviewers. See the [reviewing guide](#reviewerguide) for more details. - Any time package changes are likely to alter the results of [the automated `pkgcheck` checks](https://docs.ropensci.org/pkgcheck), authors can request a re-check with the command, `@ropensci-review-bot check package`. - Please notify us immediately if you are no longer able to maintain your package or to respond to reviews. You will then be expected to either retract a submission, or to find alternative package maintainers. You can also discuss maintenance issues in the rOpenSci slack workspace. - Once your package is approved, we will provide further instructions about the transfer of your repository to the rOpenSci repository. diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index 91706d058..9e9e42a04 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -318,7 +318,7 @@ In general, at least one reviewer should have prior reviewing experience, and of - Upon each review being submitted, - Write a comment thanking the reviewer in your own words. - Record the review by typing a new comment `@ropensci-review-bot submit review time