From b31b4117e044d05e6f79a00a2fdc63065999708c Mon Sep 17 00:00:00 2001 From: mpadge Date: Tue, 16 Jun 2026 09:12:50 +0200 Subject: [PATCH 1/4] describe new EiC 'ping editors' bot command --- softwarereview_editor.Rmd | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index 9ade986d8..d226ef0b8 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -106,7 +106,17 @@ Could you add a more detailed comparison to the packages you mention in the READ - Initially tag each new full submission with ` 0/editorial-team-prep` -- Find a handling editor (potentially including yourself). +- Issue the following command to email all editors a notification that we're seeking volunteers for the submission: + + ``` + @ropensci-review-bot ping editors + ``` + + Editors can express interest by clicking on a link in their email. + Each click will automatically send a notification email to the EiC informing them who has clicked. + EiC's may automatically assign editors to issues, but may first like to confirm via a brief Slack exchange. + +- If nobody responds, more active solicitation may be necessary. Currently available editors are indicated on the [*Editorial Dashboard*](https://dashboard.ropensci.org), and editorial workloads should be distributed as evenly as possible, through referring to the [*Dashboard* charts of recent editorial load](https://dashboard.ropensci.org/editors.html#past-ed-load). The EiC may also recruit a guest editor to handle any submission, as described in the [sub-section below](#guesteditor). @@ -364,4 +374,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 ba7e42dfa1e7014fa09791ea658e53ea2a0efb80 Mon Sep 17 00:00:00 2001 From: mpadge Date: Thu, 25 Jun 2026 10:08:44 +0200 Subject: [PATCH 2/4] thanks @maelle, updated now ... 'may first like to ask directly via Slack to ensure editors are willing to be assigned.' Hopefully that's now clearer? --- softwarereview_editor.Rmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index d226ef0b8..7fce5457f 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -114,7 +114,7 @@ Could you add a more detailed comparison to the packages you mention in the READ Editors can express interest by clicking on a link in their email. Each click will automatically send a notification email to the EiC informing them who has clicked. - EiC's may automatically assign editors to issues, but may first like to confirm via a brief Slack exchange. + EiC's may automatically assign editors to issues, but may first like to ask directly via Slack to ensure editors are willing to be assigned. - If nobody responds, more active solicitation may be necessary. Currently available editors are indicated on the [*Editorial Dashboard*](https://dashboard.ropensci.org), and editorial workloads should be distributed as evenly as possible, through referring to the [*Dashboard* charts of recent editorial load](https://dashboard.ropensci.org/editors.html#past-ed-load). From 30dd295a39620ad08d2256c3513c6829fd624ab5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Fri, 26 Jun 2026 10:29:19 +0200 Subject: [PATCH 3/4] news item --- booknews.Rmd | 1 + 1 file changed, 1 insertion(+) diff --git a/booknews.Rmd b/booknews.Rmd index 078494bbc..0c44fbab6 100644 --- a/booknews.Rmd +++ b/booknews.Rmd @@ -2,6 +2,7 @@ ## Dev version +- 2026-06-26, describe new EiC 'ping editors' bot command (#1018). - 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 88c74ba5f6fe5c928b2d13c174a9a577d8b5d255 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Fri, 26 Jun 2026 11:51:44 +0200 Subject: [PATCH 4/4] add automatic translations --- softwarereview_editor.es.Rmd | 12 +++++++++++- softwarereview_editor.pt.Rmd | 12 +++++++++++- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/softwarereview_editor.es.Rmd b/softwarereview_editor.es.Rmd index 36fbcbd77..c0c8787c9 100644 --- a/softwarereview_editor.es.Rmd +++ b/softwarereview_editor.es.Rmd @@ -106,7 +106,17 @@ Si un paquete tiene funcionalidad que se solapa con otros paquetes, requerimos q - Etiqueta inicialmente cada nuevo envío completo con ` 0/editorial-team-prep` -- Encuentra alguién del equipo editorial para que se encargue del envío (incluido tú, potencialmente). +- Ejecuta el siguiente comando para enviar por correo electrónico a todos los editores una notificación indicando que estamos buscando voluntarios para la edición: + + ``` + @ropensci-review-bot ping editors + ``` + + Los editores pueden manifestar su interés haciendo clic en un enlace que aparece en su correo electrónico. + Cada clic enviará automáticamente un correo electrónico de notificación al editor en jefe (EiC) informándole quién ha hecho clic. + Los EiC pueden asignar automáticamente editores a los números, pero tal vez prefieran preguntarles primero directamente a través de Slack para asegurarse de que los editores estén dispuestos a ser asignados.Expandir comentarioComentario en la línea R117Resuelto + +- Si nadie responde, podría ser necesario realizar una convocatoria más activa. Quiénes están disponibles actualmente se indican en la página [*Panel Editorial*](https://dashboard.ropensci.org), y las cargas de trabajo editoriales deben distribuirse de la forma más uniforme posible, remitiéndose al [*Cuadro de envíos*, gráficos de carga editorial reciente](https://dashboard.ropensci.org/editors.html#past-ed-load). También se puede designar a una persona editora invitada para encargarse de cualquier envío, tal como se describe en la [subsección siguiente](#guesteditor). diff --git a/softwarereview_editor.pt.Rmd b/softwarereview_editor.pt.Rmd index d88c8afc0..cd4399391 100644 --- a/softwarereview_editor.pt.Rmd +++ b/softwarereview_editor.pt.Rmd @@ -106,7 +106,17 @@ Você poderia adicionar ao README uma comparação mais detalhada em relação a - Inicialmente, marque cada novo envio completo com ` 0/editorial-team-prep` -- Encontre alguém da equipe editorial para que fique responsável pelo envio (incluindo você, potencialmente). +- Execute o seguinte comando para enviar por e-mail a todos os editores uma notificação informando que estamos buscando voluntários para a edição: + + ``` + @ropensci-review-bot ping editors + ``` + + Os editores podem manifestar interesse clicando em um link no e-mail recebido. + Cada clique enviará automaticamente um e-mail de notificação ao editor-chefe (EiC), informando quem clicou. + Os editores-chefes podem designar editores para as edições automaticamente, mas talvez prefiram perguntar diretamente pelo Slack primeiro, para garantir que os editores estejam dispostos a aceitar a designação.Expandir comentárioComentário na linha R117Resolvido + +- Se ninguém responder, pode ser necessário fazer uma solicitação mais ativa. As pessoas da equipe editorial atualmente disponíveis estão indicadas no [*Painel editorial*](https://dashboard.ropensci.org) As cargas de trabalho editoriais devem ser distribuídas da maneira mais uniforme possível, consultando os [gráficos de cargas editoriais recentes no *Painel editorial* ](https://dashboard.ropensci.org/editors.html#past-ed-load). A pessoa que ocupa o papel de EiC também pode recrutar alguém como editora convidada para acompanhar alguma submissão, conforme descrito na [subseção abaixo](#guesteditor).