From 77544162abcfa5ed4471b831838e8db1b4a9b79f Mon Sep 17 00:00:00 2001
From: "Alec L. Robitaille" <robit.alec@gmail.com>
Date: Tue, 23 Jun 2026 16:06:44 -0230
Subject: [PATCH 1/6] note for editors for authors to record response

---
 softwarereview_editor.Rmd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd
index 9ade986d8..72b0a4e0e 100644
--- a/softwarereview_editor.Rmd
+++ b/softwarereview_editor.Rmd
@@ -312,7 +312,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 <review-url> time <time in hours>`, like in [this example](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Upon changes being made, change the review status tag to `5/awaiting-reviewer-response`, and request that reviewers indicate approval with the [reviewer approval template](#approval2template).
+- Upon changes being made, ensure the author [submits their response using the bot](https://devguide.ropensci.org/bot_cheatsheet.html#submit-response-to-reviewers), change the review status tag to `5/awaiting-reviewer-response`, and request that reviewers indicate approval with the [reviewer approval template](#approval2template).
 - If the authors intend to submit an accompanying [Applications](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) manuscript at [Methods in Ecology and Evolution](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indicate to the authors can submit their manuscript after the review has been completed. 
 
 #### Answering reviewers' questions {#reviewersupport}
@@ -364,4 +364,4 @@ For package authors who wish to retain their repositories in their original GitH
 
 #### 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).

From 8412b70aaf3fdce14d946cef9e0e73030a486ef9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= <maelle.salmon@yahoo.se>
Date: Thu, 25 Jun 2026 15:20:54 +0200
Subject: [PATCH 2/6] news

---
 booknews.Rmd | 1 +
 1 file changed, 1 insertion(+)

diff --git a/booknews.Rmd b/booknews.Rmd
index 078494bbc..e5be11885 100644
--- a/booknews.Rmd
+++ b/booknews.Rmd
@@ -2,6 +2,7 @@
 
 ## Dev version
 
+- 2026-06-25, add note for editors that authors should record their responses (#1021, `@robitalec`)
 - 2026-05-21, clarify that stats must start with a pre-sub (#1011).
 - 2026-05-21, add comment on updating Airtable rev-prod for new editors (#1005).
 - 2026-05-21, update docs to require pkg websites at submission (#1004).

From 8f27fcef7d8b6522fe1bbefae9e5b27016baccd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= <maelle.salmon@yahoo.se>
Date: Thu, 25 Jun 2026 15:28:34 +0200
Subject: [PATCH 3/6] translate

---
 softwarereview_author.Rmd    | 2 +-
 softwarereview_editor.es.Rmd | 2 +-
 softwarereview_editor.pt.Rmd | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

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.es.Rmd b/softwarereview_editor.es.Rmd
index 5eb9c771d..5e54266f2 100644
--- a/softwarereview_editor.es.Rmd
+++ b/softwarereview_editor.es.Rmd
@@ -312,7 +312,7 @@ En general, al menos una debe tener experiencia previa en revisiones y, por supu
 - Una vez enviada cada revisión,
   - Escribe un comentario de agradecimiento a las personas que revisaron con tus propias palabras.
   - Registra la reseña escribiendo un nuevo comentario `@ropensci-review-bot submit review <review-url> time <time in hours>` como en [este ejemplo](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Una vez realizados los cambios, cambia la etiqueta de estado de revisión a `5/awaiting-reviewer-response` y pide a las personas a cargo de la revisión que indiquen su aprobación con la [plantilla de aprobación de revisión]{#approval2template}.
+- Una vez realizados los cambios, asegurate de que quien presentó el paquete [envíe su respuesta mediante el bot](#submit-response-to-reviewers), cambia la etiqueta de estado de revisión a `5/awaiting-reviewer-response` y pide a las personas a cargo de la revisión que indiquen su aprobación con la [plantilla de aprobación de revisión]{#approval2template}.
 - Si quien presentó el paquete tiene la intención de presentar un [artículo científico](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) en [*Methods in Ecology and Evolution*](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indícale que pueden presentarlo una vez finalizada la revisión. 
 
 #### Responder a las preguntas del equipo de revisión {#reviewersupport}
diff --git a/softwarereview_editor.pt.Rmd b/softwarereview_editor.pt.Rmd
index 46a05f91b..bc5f9e711 100644
--- a/softwarereview_editor.pt.Rmd
+++ b/softwarereview_editor.pt.Rmd
@@ -312,7 +312,7 @@ Em geral, pelo menos um(a) revisor(a) deve ter experiência prévia em revisão
 - Após o envio de cada revisão,
   - Escreva um comentário agradecendo o(a) revisor(a), com suas próprias palavras.
   - Registre a revisão escrevendo um novo comentário `@ropensci-review-bot submit review <review-url> time <time in hours>` como [neste exemplo](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Quando as alterações forem feitas, altere a etiqueta de status da revisão para `5/awaiting-reviewer-response` e solicite que os(as) revisores(as) indiquem a aprovação usando o [modelo de aprovação de revisão](#approval2template).
+- Quando as alterações forem feitas,  garantir que as pessoas autoras [envie sua resposta por meio do bot](#submit-response-to-reviewers), alterem a etiqueta de status da revisão para `5/awaiting-reviewer-response` e solicite que os(as) revisores(as) indiquem a aprovação usando o [modelo de aprovação de revisão](#approval2template).
 - Se as pessoas autoras tiverem a intenção de enviar um manuscrito de acompanhamento do tipo [*Applications*](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) no periódico [Methods in Ecology and Evolution](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indique que o envio do manuscrito pode ser feito após a conclusão da revisão. 
 
 #### Respondendo às perguntas dos(as) revisores(as) {#reviewersupport}

From 9888adc0729b6f25b81a17821c842ded2862c307 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= <maelle.salmon@yahoo.se>
Date: Thu, 25 Jun 2026 15:40:05 +0200
Subject: [PATCH 4/6] fix

---
 softwarereview_editor.Rmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd
index 72b0a4e0e..282851f94 100644
--- a/softwarereview_editor.Rmd
+++ b/softwarereview_editor.Rmd
@@ -312,7 +312,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 <review-url> time <time in hours>`, like in [this example](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Upon changes being made, ensure the author [submits their response using the bot](https://devguide.ropensci.org/bot_cheatsheet.html#submit-response-to-reviewers), change the review status tag to `5/awaiting-reviewer-response`, and request that reviewers indicate approval with the [reviewer approval template](#approval2template).
+- Upon changes being made, ensure the author [submits their response using the bot](#submit-response-to-reviewers), change the review status tag to `5/awaiting-reviewer-response`, and request that reviewers indicate approval with the [reviewer approval template](#approval2template).
 - If the authors intend to submit an accompanying [Applications](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) manuscript at [Methods in Ecology and Evolution](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indicate to the authors can submit their manuscript after the review has been completed. 
 
 #### Answering reviewers' questions {#reviewersupport}

From 16822746b0fdcdf6c28fd1eeb8ce2b7fc7443260 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= <maelle.salmon@yahoo.se>
Date: Fri, 26 Jun 2026 09:53:24 +0200
Subject: [PATCH 5/6] Update softwarereview_editor.pt.Rmd

Co-authored-by: Beatriz Milz <42153618+beatrizmilz@users.noreply.github.com>
---
 softwarereview_editor.pt.Rmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/softwarereview_editor.pt.Rmd b/softwarereview_editor.pt.Rmd
index bc5f9e711..95694c119 100644
--- a/softwarereview_editor.pt.Rmd
+++ b/softwarereview_editor.pt.Rmd
@@ -312,7 +312,7 @@ Em geral, pelo menos um(a) revisor(a) deve ter experiência prévia em revisão
 - Após o envio de cada revisão,
   - Escreva um comentário agradecendo o(a) revisor(a), com suas próprias palavras.
   - Registre a revisão escrevendo um novo comentário `@ropensci-review-bot submit review <review-url> time <time in hours>` como [neste exemplo](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Quando as alterações forem feitas,  garantir que as pessoas autoras [envie sua resposta por meio do bot](#submit-response-to-reviewers), alterem a etiqueta de status da revisão para `5/awaiting-reviewer-response` e solicite que os(as) revisores(as) indiquem a aprovação usando o [modelo de aprovação de revisão](#approval2template).
+- Quando as alterações forem feitas, garanta que as pessoas autoras [enviem sua resposta utilizando o bot](#submit-response-to-reviewers), alterem a etiqueta de status da revisão para `5/awaiting-reviewer-response` e solicite que os(as) revisores(as) indiquem a aprovação usando o [modelo de aprovação de revisão](#approval2template).
 - Se as pessoas autoras tiverem a intenção de enviar um manuscrito de acompanhamento do tipo [*Applications*](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) no periódico [Methods in Ecology and Evolution](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indique que o envio do manuscrito pode ser feito após a conclusão da revisão. 
 
 #### Respondendo às perguntas dos(as) revisores(as) {#reviewersupport}

From f0d8ba0c6f89d2ce6fd23155662b95fc4174b6f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= <maelle.salmon@yahoo.se>
Date: Fri, 26 Jun 2026 09:57:09 +0200
Subject: [PATCH 6/6] Update softwarereview_editor.es.Rmd

Co-authored-by: Beatriz Milz <42153618+beatrizmilz@users.noreply.github.com>
---
 softwarereview_editor.es.Rmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/softwarereview_editor.es.Rmd b/softwarereview_editor.es.Rmd
index 5e54266f2..4ba3b1748 100644
--- a/softwarereview_editor.es.Rmd
+++ b/softwarereview_editor.es.Rmd
@@ -312,7 +312,7 @@ En general, al menos una debe tener experiencia previa en revisiones y, por supu
 - Una vez enviada cada revisión,
   - Escribe un comentario de agradecimiento a las personas que revisaron con tus propias palabras.
   - Registra la reseña escribiendo un nuevo comentario `@ropensci-review-bot submit review <review-url> time <time in hours>` como en [este ejemplo](https://github.com/ropensci/software-review/issues/705#issuecomment-2984012477).
-- Una vez realizados los cambios, asegurate de que quien presentó el paquete [envíe su respuesta mediante el bot](#submit-response-to-reviewers), cambia la etiqueta de estado de revisión a `5/awaiting-reviewer-response` y pide a las personas a cargo de la revisión que indiquen su aprobación con la [plantilla de aprobación de revisión]{#approval2template}.
+- Una vez realizados los cambios, asegurate de que quien presentó el paquete [envíe su respuesta mediante el bot](#submit-response-to-reviewers), cambia la etiqueta de estado de revisión a `5/awaiting-reviewer-response` y pide a las personas a cargo de la revisión que indiquen su aprobación con la [plantilla de aprobación de revisión](#approval2template).
 - Si quien presentó el paquete tiene la intención de presentar un [artículo científico](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) en [*Methods in Ecology and Evolution*](https://besjournals.onlinelibrary.wiley.com/journal/2041210X), indícale que pueden presentarlo una vez finalizada la revisión. 
 
 #### Responder a las preguntas del equipo de revisión {#reviewersupport}