From bbb1a61992c058f26af1ca74c9b0714ac7622ef7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Mon, 3 Feb 2025 10:57:09 +0100 Subject: [PATCH 1/6] make transfer less of a requirement --- maintenance_collaboration.Rmd | 9 +++++++-- maintenance_curation.Rmd | 3 ++- maintenance_github_grooming.Rmd | 2 +- pkg_ci.Rmd | 2 +- softwarereview_intro.Rmd | 2 +- 5 files changed, 12 insertions(+), 6 deletions(-) diff --git a/maintenance_collaboration.Rmd b/maintenance_collaboration.Rmd index 92a97c8ba..5e850c131 100644 --- a/maintenance_collaboration.Rmd +++ b/maintenance_collaboration.Rmd @@ -18,7 +18,8 @@ Besides these mostly technical tips, it is important to remember to be kind, and ### Code of conduct {#coc-file} -After transfer to our GitHub organization, [rOpenSci Code of Conduct](https://ropensci.org/code-of-conduct/) will apply to your project. +Once your package is listed into the [rOpenSci registry](https://ropensci.org/packages/all), +the [rOpenSci Code of Conduct](https://ropensci.org/code-of-conduct/) will apply to your project. Please add this text to the README ```markdown @@ -28,7 +29,11 @@ By contributing to this project, you agree to abide by its terms. ``` -And delete the package current code of conduct if there was one. +And + +- If your package was transferred to the rOpenSci GitHub organization, please delete the current code of conduct of the repository if there was one as the default code of conduct of the GitHub organization will appear. + +- If your package was not transferred to the rOpenSci GitHub organization, please replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). ### Contributing guide {#contributing-guide} diff --git a/maintenance_curation.Rmd b/maintenance_curation.Rmd index 851786f8c..afedc29aa 100644 --- a/maintenance_curation.Rmd +++ b/maintenance_curation.Rmd @@ -89,7 +89,8 @@ community and have passed through peer review. They need to be at the time of submission to be reviewed. - Upon acceptance, these peer-reviewed packages are transferred from - the author's GitHub to the "ropensci" GitHub organization + the author's GitHub to the "ropensci" GitHub organization + or alternatively tracked by adding them to a [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json). - Peer-reviewed packages will be in the registry tagged as "peer-reviewed" and have a peer-reviewed badge in their README. diff --git a/maintenance_github_grooming.Rmd b/maintenance_github_grooming.Rmd index 4483d8d25..12acba8f1 100644 --- a/maintenance_github_grooming.Rmd +++ b/maintenance_github_grooming.Rmd @@ -42,7 +42,7 @@ More info about GitHub linguist overrides [here](https://github.com/github/lingu - As the author of an onboarded package, you are now a member of rOpenSci's "ropensci" GitHub organization. By default, organization memberships are private; see [how to make it public in GitHub docs](https://help.github.com/articles/publicizing-or-hiding-organization-membership/). -- Even after your package repo has been transferred to rOpenSci, you can [pin it under your own account](https://help.github.com/articles/pinning-repositories-to-your-profile/). +- Even if your package repo has been transferred to rOpenSci, you can [pin it under your own account](https://help.github.com/articles/pinning-repositories-to-your-profile/). - In general we recommend adding at least an avatar (which doesn't need to be your face!) and your name [to your GitHub profile](https://help.github.com/articles/customizing-your-profile/). diff --git a/pkg_ci.Rmd b/pkg_ci.Rmd index 4b22bc007..28fcde17c 100644 --- a/pkg_ci.Rmd +++ b/pkg_ci.Rmd @@ -102,7 +102,7 @@ You also need to give Codecov access to your github repository, see [Codecov qui Then add a Codecov status badge to the top of your README.md, see [Codecov status badges](https://docs.codecov.com/docs/status-badges). Currently, Codecov has access to all ropensci github repositories by default. -When your repository is accepted and transferred to ropensci, Codecov access should transfer automatically. +If your repository is transferred to the ropensci GitHub organization, Codecov access should transfer automatically. You will need to update the URL of the badge to point to the rOpenSci-hosted repository. For more details, see the [README for the **covr** package](https://github.com/r-lib/covr) for instructions, as well as [`usethis::use_coverage()`](https://usethis.r-lib.org/reference/use_coverage.html) and [`usethis::use_github_action()`](https://usethis.r-lib.org/reference/github_actions.html). diff --git a/softwarereview_intro.Rmd b/softwarereview_intro.Rmd index e4bdb3a4d..ea903eb11 100644 --- a/softwarereview_intro.Rmd +++ b/softwarereview_intro.Rmd @@ -44,7 +44,7 @@ Furthermore, authors and reviewers have the ability to contact privately the edi - Your package README will feature a peer-review badge linking to the software review thread. - Your package will get a [`docs.ropensci.org` docs website](#rodocsci) that you can link from DESCRIPTION. -- Your package repo will be transferred to the rOpenSci organization. +- Your package repo might be transferred to the rOpenSci organization if you agree. - If reviewers [agree to be listed in DESCRIPTION](#authorship), their metadata will mention the review. ## Editors and reviewers {#editors-and-reviewers} From 8c7c52e67901ae5a23dbe3177dfdebd5158afb22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Thu, 13 Mar 2025 15:31:27 +0100 Subject: [PATCH 2/6] tweaks --- softwarereview_editor.Rmd | 8 ++++++++ softwarereview_intro.Rmd | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index b95708911..486b6735a 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -117,6 +117,14 @@ Each submission should be reviewed by *two* package reviewers. Although it is fi package, contact [an rOpenSci staff member](https://ropensci.org/about/#team) so they might contact the authors about transfer to [the `ropensci-books` GitHub organisation](https://github.com/orgs/ropensci-books). +#### If the author want their repository to remain under its current owner + +- [ ] Ask them to make a pull request to the [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) that lists all repositories that have not been transferred. [Example commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). + +- Ask them to replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md) (which means linking to rOpenSci's code of conduct). + + + ### Package promotion: {#package-promotion} - Direct the author to the chapters of the guide about [package releases](#releases), [marketing](#marketing) and [GitHub grooming](#grooming). diff --git a/softwarereview_intro.Rmd b/softwarereview_intro.Rmd index ea903eb11..8d3ddcbad 100644 --- a/softwarereview_intro.Rmd +++ b/softwarereview_intro.Rmd @@ -44,7 +44,7 @@ Furthermore, authors and reviewers have the ability to contact privately the edi - Your package README will feature a peer-review badge linking to the software review thread. - Your package will get a [`docs.ropensci.org` docs website](#rodocsci) that you can link from DESCRIPTION. -- Your package repo might be transferred to the rOpenSci organization if you agree. +- Your package repo will be transferred to the rOpenSci organization if you agree. - If reviewers [agree to be listed in DESCRIPTION](#authorship), their metadata will mention the review. ## Editors and reviewers {#editors-and-reviewers} From 38b47873239641f310b9bd8ac18d6054e9b511eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Thu, 13 Mar 2025 15:37:25 +0100 Subject: [PATCH 3/6] format --- softwarereview_editor.Rmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index 486b6735a..66c3ef398 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -119,7 +119,7 @@ Each submission should be reviewed by *two* package reviewers. Although it is fi #### If the author want their repository to remain under its current owner -- [ ] Ask them to make a pull request to the [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) that lists all repositories that have not been transferred. [Example commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). +- Ask them to make a pull request to the [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) that lists all repositories that have not been transferred. [Example commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). - Ask them to replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md) (which means linking to rOpenSci's code of conduct). From aaca3a214d3c880b19a90efcd430ae2290e22805 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Fri, 28 Mar 2025 14:25:54 +0100 Subject: [PATCH 4/6] Apply suggestions from code review Co-authored-by: mark padgham --- maintenance_collaboration.Rmd | 2 +- softwarereview_editor.Rmd | 8 +++++--- softwarereview_intro.Rmd | 2 +- 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/maintenance_collaboration.Rmd b/maintenance_collaboration.Rmd index 5e850c131..1010517f1 100644 --- a/maintenance_collaboration.Rmd +++ b/maintenance_collaboration.Rmd @@ -33,7 +33,7 @@ And - If your package was transferred to the rOpenSci GitHub organization, please delete the current code of conduct of the repository if there was one as the default code of conduct of the GitHub organization will appear. -- If your package was not transferred to the rOpenSci GitHub organization, please replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). +- If your package was not transferred to the rOpenSci GitHub organization, please replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the rOpenSci GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). ### Contributing guide {#contributing-guide} diff --git a/softwarereview_editor.Rmd b/softwarereview_editor.Rmd index 66c3ef398..5683b6fa2 100644 --- a/softwarereview_editor.Rmd +++ b/softwarereview_editor.Rmd @@ -117,11 +117,13 @@ Each submission should be reviewed by *two* package reviewers. Although it is fi package, contact [an rOpenSci staff member](https://ropensci.org/about/#team) so they might contact the authors about transfer to [the `ropensci-books` GitHub organisation](https://github.com/orgs/ropensci-books). -#### If the author want their repository to remain under its current owner +#### Packages remaining in original GitHub organizations -- Ask them to make a pull request to the [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) that lists all repositories that have not been transferred. [Example commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). +For package authors who wish to retain their repositories in their original GitHub organizations, rather than transfer to github.com/ropensci, editors should: -- Ask them to replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md) (which means linking to rOpenSci's code of conduct). +- Ask package authors to make a pull request to the [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) that lists all repositories that have not been transferred. [Example commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). + +- Ask package to replace the content of the current code of conduct of the repository with the content of the [default code of conduct of the rOpenSci GitHub organization](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). diff --git a/softwarereview_intro.Rmd b/softwarereview_intro.Rmd index 8d3ddcbad..a73d88f82 100644 --- a/softwarereview_intro.Rmd +++ b/softwarereview_intro.Rmd @@ -44,7 +44,7 @@ Furthermore, authors and reviewers have the ability to contact privately the edi - Your package README will feature a peer-review badge linking to the software review thread. - Your package will get a [`docs.ropensci.org` docs website](#rodocsci) that you can link from DESCRIPTION. -- Your package repo will be transferred to the rOpenSci organization if you agree. +- If desired, your package repo may be transferred to the rOpenSci organization. - If reviewers [agree to be listed in DESCRIPTION](#authorship), their metadata will mention the review. ## Editors and reviewers {#editors-and-reviewers} From 6046eaef46bef04837e55488a1405ff4542601d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Fri, 28 Mar 2025 14:47:07 +0100 Subject: [PATCH 5/6] add ES translation --- maintenance_collaboration.es.Rmd | 8 ++++++-- maintenance_curation.es.Rmd | 2 +- maintenance_github_grooming.es.Rmd | 2 +- pkg_ci.es.Rmd | 2 +- softwarereview_editor.es.Rmd | 8 ++++++++ softwarereview_intro.es.Rmd | 2 +- 6 files changed, 18 insertions(+), 6 deletions(-) diff --git a/maintenance_collaboration.es.Rmd b/maintenance_collaboration.es.Rmd index 54fee0f87..a6c42f22d 100644 --- a/maintenance_collaboration.es.Rmd +++ b/maintenance_collaboration.es.Rmd @@ -13,7 +13,7 @@ Además de estos consejos, en su mayoría técnicos, es importante recordar que ### Código de conducta {#coc-file} -Tras el traslado a nuestra organización de GitHub, [el Código de Conducta de rOpenSci](https://ropensci.org/code-of-conduct/) se aplicará a tu proyecto. +Una vez que tu paquete esté incluido en el [registro rOpenSci](https://ropensci.org/packages/all), [el Código de Conducta de rOpenSci](https://ropensci.org/code-of-conduct/) se aplicará a tu proyecto. Por favor, añade este texto al *README* ```markdown @@ -21,7 +21,11 @@ Ten en cuenta que este paquete se publica con un [Código de Conducta para contr Al contribuir a este proyecto, te comprometes a cumplir sus condiciones. ``` -Y eliminar el código de conducta actual del paquete, si lo hubiera. +Y + +- Si tu paquete fue transferido a la organización GitHub de rOpenSci, por favor, elimina el código de conducta actual del repositorio si había uno, ya que aparecerá el código de conducta por defecto de la organización GitHub. + +- Si tu paquete no fue transferido a la organización GitHub de rOpenSci, por favor reemplaza el contenido del código de conducta actual del repositorio con el contenido del [código de conducta por defecto de la organización rOpenSci GitHub](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). ### Guía de contribución {#contributing-guide} diff --git a/maintenance_curation.es.Rmd b/maintenance_curation.es.Rmd index 95bdeee63..eb28c0372 100644 --- a/maintenance_curation.es.Rmd +++ b/maintenance_curation.es.Rmd @@ -54,7 +54,7 @@ Muchos son paquetes de infraestructura que están fuera del alcance de la revisi Los paquetes revisados por pares son aquellos aportados a rOpenSci por la comunidad y que han pasado por la revisión por pares. Tienen que estar [en el ámbito de aplicación](#aims-and-scope) en el momento del envío para ser revisados. -- Una vez aceptados, estos paquetes revisados por pares se transfieren desde el GitHub original a la organización de GitHub ropensci. +- Una vez aceptados, estos paquetes revisados por pares se transfieren desde el GitHub original a la organización de GitHub ropensci o, alternativamente, se realiza un seguimiento añadiéndolos a un [archivo JSON](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json). - Los paquetes revisados por pares estarán en el registro etiquetados como "peer-reviewed" y tendrán una etiqueta de revisado por pares en su archivo *README*. diff --git a/maintenance_github_grooming.es.Rmd b/maintenance_github_grooming.es.Rmd index ad9dd264a..ba88a86e3 100644 --- a/maintenance_github_grooming.es.Rmd +++ b/maintenance_github_grooming.es.Rmd @@ -42,7 +42,7 @@ Más información sobre las anulaciones del lingüista de GitHub [aquí](https:/ - Como responsable de un paquete incorporado, ahora eres miembro de la organización GitHub "ropensci" de rOpenSci. Por defecto, la pertenencia a la organización es privada; consulta [cómo hacerla pública en la documentación de GitHub](https://help.github.com/articles/publicizing-or-hiding-organization-membership/). -- Incluso después de que el repositorio de tu paquete haya sido transferido a rOpenSci, puedes [destacarlo en tu propia cuenta](https://help.github.com/articles/pinning-repositories-to-your-profile/). +- Incluso si el repositorio de tu paquete ha sido transferido a rOpenSci, puedes [destacarlo en tu propia cuenta](https://help.github.com/articles/pinning-repositories-to-your-profile/). - En general, recomendamos añadir al menos una imagen de perfil (¡que no tiene por qué ser tu cara!) y tu nombre [a tu perfil de GitHub](https://help.github.com/articles/customizing-your-profile/). diff --git a/pkg_ci.es.Rmd b/pkg_ci.es.Rmd index 57fba620d..30f6ff10e 100644 --- a/pkg_ci.es.Rmd +++ b/pkg_ci.es.Rmd @@ -113,7 +113,7 @@ También tienes que dar acceso a Codecov a tu repositorio de GitHub, ver [la gu Luego añade una etiqueta de estado de Codecov en la parte superior de tu README.md, puedes consultar [*Status Badges* (etiquetas de estado)](https://docs.codecov.com/docs/status-badges) en la documentación de Codecov. Actualmente, Codecov tiene acceso a todos los repositorios de GitHub de la organización ropensci por defecto. -Cuando tu repositorio sea aceptado y transferido a ropensci, el acceso de Codecov debería transferirse automáticamente. +Si tu repositorio es transferido a la organización GitHub ropensci, el acceso de Codecov debería transferirse automáticamente. Tendrás que actualizar la URL de la etiqueta para que apunte al repositorio alojado en ropensci. Para más detalles, consulta el [README del paquete **covr**](https://github.com/r-lib/covr), así como la documentación de [`usethis::use_coverage()`](https://usethis.r-lib.org/reference/use_coverage.html) y [`usethis::use_github_action()`](https://usethis.r-lib.org/reference/github_actions.html). diff --git a/softwarereview_editor.es.Rmd b/softwarereview_editor.es.Rmd index 9673fa1f4..8e5d7d833 100644 --- a/softwarereview_editor.es.Rmd +++ b/softwarereview_editor.es.Rmd @@ -115,6 +115,14 @@ En general, al menos una debe tener experiencia previa en revisiones y, por supu - Nomina el paquete para que aparezca en un artículo del blog de rOpenSci o en una nota técnica si crees que puede ser de gran interés. Por favor, anota en el *issue* de revisión una o dos cosas que destacables, y etiqueta a `@ropensci/blog-editors` para su seguimiento. - Si el paquete tiene un gitbook asociado (aunque sólo sea parcialmente), ponte en contacto con [alguien del equipo de rOpenSci](https://ropensci.org/about/#team) para que se ponga en contacto con quienes lo mantienen y hable sobre su transferencia a [la página `ropensci-books` organización de GitHub](https://github.com/orgs/ropensci-books). +#### Paquetes que permanecen en las organizaciones originales de GitHub + +Para quienes deseen mantener sus repositorios en sus organizaciones originales de GitHub, en lugar de transferirlos a github.com/ropensci, se debe: + +- Pedir a quién presentó el paquete que haga un pull request al [archivo JSON](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) que enumere todos los repositorios que no han sido transferidos. [Ejemplo de commit](https://github.com/ropensci/roregistry/commit/9568a77c2081f89d58406efcc9089ef83d09fe59). + +- Pedir a quién presentó el paquete que reemplace el contenido del código de conducta actual del repositorio por el contenido del [código de conducta por defecto de la organización rOpenSci GitHub](https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). + ### Promoción de paquetes: {#package-promotion} - Dirige quien presentó el paquete a los capítulos de la guía sobre [publicación de paquetes](#releases), [marketing](#marketing) y [preparación para GitHub](#grooming). diff --git a/softwarereview_intro.es.Rmd b/softwarereview_intro.es.Rmd index 7cee91948..2f2732555 100644 --- a/softwarereview_intro.es.Rmd +++ b/softwarereview_intro.es.Rmd @@ -62,7 +62,7 @@ Además, tanto quienes envían paquete y quienes los revisan tienen la posibilid - El *README* de tu paquete incluirá una etiqueta de revisión por pares que enlaza con el hilo de revisión. - Tu paquete tendrá un [sitio web de documentación en `docs.ropensci.org`](#rodocsci) que podrás enlazar en el archivo *DESCRIPTION*. -- El repositorio de tu paquete será transferido a la organización rOpenSci. +- Si quieres, el repositorio de tu paquete será transferido a la organización rOpenSci. - Si quienes realizaron la revisión [aceptan aparecer en el archivo *DESCRIPTION*](#authorship), sus metadatos mencionarán la revisión. ## Personas responsables de edición y revisión {#editors-and-reviewers} From 9743caa2fbea6b29cd1d3b635104f3894fe0c2a6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABlle=20Salmon?= Date: Fri, 28 Mar 2025 14:51:09 +0100 Subject: [PATCH 6/6] add pt translation --- maintenance_collaboration.pt.Rmd | 8 ++++++-- maintenance_curation.pt.Rmd | 2 +- maintenance_github_grooming.pt.Rmd | 2 +- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/maintenance_collaboration.pt.Rmd b/maintenance_collaboration.pt.Rmd index e9ea70bdf..de9ca8693 100644 --- a/maintenance_collaboration.pt.Rmd +++ b/maintenance_collaboration.pt.Rmd @@ -18,7 +18,7 @@ Além dessas dicas técnicas, é importante lembrar-se de ser gentil e levar em ### Código de conduta {#coc-file} -Após a transferência para a nossa organização no GitHub, o [Código de Conduta da rOpenSci](https://ropensci.org/code-of-conduct/) será aplicado ao seu projeto. +Depois que o seu pacote for listado no [rOpenSci registry] (https://ropensci.org/packages/all), o [Código de Conduta da rOpenSci](https://ropensci.org/code-of-conduct/) será aplicado ao seu projeto. Você deve adicionar este texto ao README: ```markdown @@ -28,7 +28,11 @@ By contributing to this project, you agree to abide by its terms. ``` -Em seguida, exclua o código de conduta atual do pacote, caso exista algum. +E + +- Se o seu pacote foi transferido para a organização rOpenSci GitHub, exclua o código de conduta atual do repositório, se houver um, pois o código de conduta padrão da organização GitHub será exibido. + +- Se o seu pacote não foi transferido para a organização rOpenSci GitHub, substitua o conteúdo do código de conduta atual do repositório pelo conteúdo do [código de conduta padrão da organização rOpenSci GitHub] (https://github.com/ropensci/.github/blob/main/CODE_OF_CONDUCT.md). ### Guia de contribuição {#contributing-guide} diff --git a/maintenance_curation.pt.Rmd b/maintenance_curation.pt.Rmd index 6027648bc..c1159378e 100644 --- a/maintenance_curation.pt.Rmd +++ b/maintenance_curation.pt.Rmd @@ -90,7 +90,7 @@ pela comunidade e que passaram pela revisão por pares. Eles precisam estar [dentro do escopo](#aims-and-scope) no momento em que eles são enviados para serem revisados. - Após a aceitação, esses pacotes revisados por pares são transferidos - do GitHub do(a) autor(a) para dentro da organização "ropensci" no GitHub + do GitHub do(a) autor(a) para dentro da organização "ropensci" no GitHub ou, alternativamente, rastreados adicionando-os a um [arquivo JSON] (https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json). - Os pacotes revisados por pares estarão marcados no registro como "peer-reviewed", e terão um selo de revisão por pares em seu README. diff --git a/maintenance_github_grooming.pt.Rmd b/maintenance_github_grooming.pt.Rmd index 4f8dc5436..94623dcf7 100644 --- a/maintenance_github_grooming.pt.Rmd +++ b/maintenance_github_grooming.pt.Rmd @@ -38,7 +38,7 @@ Mais informações sobre as substituições do GitHub linguist podem ser encontr - Como autor de um pacote integrado, você agora é membro da organização "ropensci" da rOpenSci no GitHub. Por padrão, as participações da organização são privadas; consulte [como torná-la pública na documentação do GitHub](https://help.github.com/articles/publicizing-or-hiding-organization-membership/). -- Mesmo após o repositório do seu pacote ser transferido para a rOpenSci, você pode [fixá-lo em sua conta pessoal](https://help.github.com/articles/pinning-repositories-to-your-profile/). +- Mesmo que o repositório do seu pacote tenha sido transferido para a rOpenSci, você pode [fixá-lo em sua conta pessoal](https://help.github.com/articles/pinning-repositories-to-your-profile/). - Em geral, recomendamos que você adicione pelo menos um avatar (que não precisa ser seu rosto!) e seu nome [no seu perfil do GitHub](https://help.github.com/articles/customizing-your-profile/).