start policy updates on ai tool usage#1006
Conversation
|
Any ETA? We could aim for a small release that'd have this and the other changes since the last release. I know this is all still very WIP. |
Thanks for the prod - I think this should be merged as quickly as possible. I also think it's okay for an initial first draft of our policies. I hope and expect we'll edit and revise as things proceed, but am happy for you to tweak, approve, and merge when you're ready. Thanks! |
|
I'll generate the translations ASAP. |
maelle
force-pushed
the
ai-updates
branch
4 times, most recently
from
c191b55 to
7220acd
Compare
maelle
requested review from
beatrizmilz and
yabellini
and removed request for
a team
|
@maelle I also just added another checkbox to templates/review.md which will also need translating. |
|
@mpadge I added the missing translations. In such cases I use copy-paste (DeepL interface or https://docs.ropensci.org/babeldown/reference/deepl_translate_clipboard.html), I can only use |
yabellini
left a comment
yabellini
left a comment
There was a problem hiding this comment.
Some Spanish suggestions.
Some comments on the clarity of the instructions.
There is text that is repeated twice; it looks like we should delete one.
| Como se indica en [nuestras políticas generales](#policies-ai) exigimos a todos los autores que envíen propuestas que describan cómo se han utilizado dichas herramientas, y que incluyan enlaces a cualquier aspecto relevante de los repositorios. | ||
| Una regla muy general es que cuanto mayor sea el uso de herramientas de IA generativa en un envío a rOpenSci, más documentación esperaremos y más esperaremos que se hayan utilizado dichas herramientas. *sistemáticamente*. | ||
| El uso sistemático de herramientas incluye cualquier enfoque que detalle de forma transparente y progresiva la contribución de las herramientas de IA generativa a la producción de software. | ||
| Los ejemplos de herramientas sistemáticas de IA generativa van desde [el "spec-kit" de GitHub para el desarrollo basado en especificaciones](https://github.com/github/spec-kit) a [nuestra propia herramienta experimental para documentar las decisiones de diseño de software](https://github.com/ropensci-review-tools/designlens). |
There was a problem hiding this comment.
I have some problems understanding what I'm supposed to do if I use AI in my package to meet the requirements outlined here. I need to check the examples linked in more deeply. I'm wondering if we can link to good examples from a package under review or other packages that have the information as we would like to see.
| El uso de herramientas de IA generativa es aceptable tanto para los autores como para los revisores, pero los revisores no pueden utilizarlas para fundamentar directamente sus decisiones o recomendaciones. | ||
| Por lo general, los revisores deben solicitar la aprobación de los autores y editores antes de utilizar herramientas de IA generativa, y hacerlo públicamente en el hilo de la revisión. | ||
| Al igual que esperamos de los autores, exigimos a los revisores que revelen cualquier uso de herramientas de IA generativa con el mayor detalle posible. | ||
| Algunos ejemplos de uso aceptable son la generación de una visión general de la funcionalidad del paquete, o la iteración a través de un historial Git para proporcionar una visión general de las decisiones de desarrollo. |
There was a problem hiding this comment.
Can we link to some good examples? Or how can you actually do that?
| Examples of acceptable usage include generating an overview of package functionality, or iterating through a Git history to provide an overview of development decisions. | ||
| We ask reviewers to be as transparent as possible. | ||
|
|
||
| ### Use of generative AI tools |
There was a problem hiding this comment.
This looks like it is repeated. It is the same text two times.
I removed it in the Spanish version. I advice to remove in the Portuguese one, I also suggest to remove from here.
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
Co-authored-by: Yanina Bellini Saibene <yabellini@gmail.com>
|
@mpadge @yabellini has great comments on the content. Could you please work on those, and then request a new review from us both? I've removed the PT translation request for now. |
3 participants
Checklist for dev guide maintainers, do not delete 😸