Add note for editors that authors should record their responses#1021
Conversation
mpadge
left a comment
There was a problem hiding this comment.
Another great catch; thanks @robitalec
yabellini
left a comment
There was a problem hiding this comment.
The text in the software review editor in Spanish looks good.
There is no Spanish text for the changes in the file "software review_author".Rmd (I don't know if it is because the translation is lacking or because we have already review that text)
| #### Package promotion {#package-promotion} | ||
|
|
||
| - Direct the author to the chapters of the guide about [package releases](#releases), [marketing](#marketing) and [GitHub grooming](#grooming). No newline at end of file | ||
| - Direct the author to the chapters of the guide about [package releases](#releases), [marketing](#marketing) and [GitHub grooming](#grooming). |
There was a problem hiding this comment.
I think nothing was changed in the content here to translate, right?
There was a problem hiding this comment.
yes! thanks for checking. Line endings again?!
| - 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. |
There was a problem hiding this comment.
Seems like this sentence is missing in the softwarereview_author.pt.Rmd file.. not sure why. So it's not showing here for review the translation. I will add this change.
"Once the response is commited, submit it using the bot."
dev_guide/softwarereview_author.pt.Rmd
Line 84 in 2e65fc0
| - 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. |
There was a problem hiding this comment.
Do we need to update this URL in Spanish also? here:
dev_guide/softwarereview_author.es.Rmd
Line 84 in 2e65fc0
(/es/bot_cheatsheet.es#submit-response-to-reviewers)
Co-authored-by: Beatriz Milz <42153618+beatrizmilz@users.noreply.github.com>
Co-authored-by: Beatriz Milz <42153618+beatrizmilz@users.noreply.github.com>
|
Thanks! |
Small note for editors, related to #832, but for editors to check that authors use the bot to record their responses to reviewers.
Without also cross-referencing the authors guide, it can be easy to miss this as an editor.
Checklist for dev guide maintainers, do not delete 😸