Skip to content

Add rule about 1 pkg at a time #878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 27, 2025
Merged

Add rule about 1 pkg at a time #878

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e161f91
Add rule about 1 pkg at a time
maelle Feb 25, 2025
a24c9a7
add pt translation
maelle Mar 7, 2025
2d8bb44
Update softwarereview_author.es.Rmd
maelle Mar 11, 2025
58ba882
Merge branch 'main' into one-at-a-time
maelle Mar 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions booknews.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## dev version

- 2025-02-25, add official rule on submitting one package at once only (`@maurolepore`, #876)

- 2024-09-06, update math guidance for pkgdown based on pkgdown's update (#838)

- 2024-08-30, remove mention of Twitter since rOpenSci no longer maintains an active Twitter account (`@yabellini`, #827)
Expand Down
1 change: 1 addition & 0 deletions softwarereview_author.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ This concise guide presents the software peer review process for you as a packag
- At the submission stage, all major functions should be stable enough to be fully documented and tested; the README should make a strong case for the package.
- Your README file should strive to explain your package's functionality and aims, assuming readers have little to no domain knowledge. All technical tems, including references to other software, should be clarified.
- Your package will continue to evolve after review, the chapter on *Package evolution* [provides guidance about the topic](#evolution).
- Please do not submit several packages at a time: we request you wait until a package has been approved before you submit another one.

## Preparing for Submission {#preparing-for-submission}

Expand Down
1 change: 1 addition & 0 deletions softwarereview_author.es.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ Esta guía condensa el proceso de revisión por pares desde el punto de vista de
- En la fase de envío, todas las funciones principales deben ser lo suficientemente estables como para estar completamente documentadas y testeadas. El *README* tiene que dar una buena impresión de tu paquete.
- El archivo *README* debe esforzarse por explicar las funcionalidades y los objetivos de tu paquete asumiendo poco o ningún conocimiento del dominio. Además, debe aclarar todos los temas técnicos, incluidas las referencias a otros software.
- Tu paquete seguirá evolucionando después de la revisión, el capítulo sobre *Evolución de paquetes* [proporciona orientación sobre el tema](#evolution).
- Por favor, no envia varios paquetes a la vez: te rogamos que espere hasta que un paquete haya sido aprobado antes de enviar otro.

## Preparación para el envío {#preparing-for-submission}

Expand Down
Loading