Enforce the prefixing of comments more #1024

booknews.Rmd

@@ -2,6 +2,7 @@
 
 ## Dev version
 
+- 2026-08-24, enforce the prefixing of comments more (#1024).
 - 2026-06-26, explicitely state that authors should not change their package while it is under review (#1022).
 - 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; thanks to `@joelnitta`)

softwarereview_author.Rmd

@@ -83,7 +83,8 @@ 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.
 - While your package is under review, please refrain from making any change, apart from hot fixes. Indeed, reviewers should be able to review the latest (best until now) version of your software, and that version should not be changing. 
-- 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.
+- 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). If reviewers used prefixes before their comments e.g. ml01, ml02, use them in your response as well.
+- 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.

softwarereview_editor.Rmd

@@ -231,6 +231,7 @@ Please use all of this information to judge whether:
 #### Initial editorial comments
 
 - After automatic checks are posted, use the [editor template](#editortemplate) to guide initial checks (if not already covered by the EiC) and record your response to the submission.
+  Prefix all your comments with numbered codes e.g. ml01, ml02, etc.
   You can also streamline your editor checks by using the [`pkgreviewr` package created by  former editor Anna Krystalli](https://docs.ropensci.org/pkgreviewr/articles/editors.html).
   Please strive to finish the checks and start looking for reviewers within 5 working days.
 - Check against policies for [fit](#aims-and-scope) and [overlap](#overlap).

templates/editor.md

@@ -14,5 +14,7 @@
 
 #### Editor comments
 
+_Prefix all your comments with numbered codes e.g. ml01, ml02, etc._
+
 ---
 

templates/review.md

@@ -40,3 +40,5 @@ Estimated hours spent reviewing:
 ---
 
 ### Review Comments
+
+_Prefix all your comments with numbered codes e.g. ml01, ml02, etc._