Skip to content

review ai-updates text after feedback from @yabellini#1013

Open
mpadge wants to merge 2 commits into
ai-updatesfrom
ai-updates2
Open

review ai-updates text after feedback from @yabellini#1013
mpadge wants to merge 2 commits into
ai-updatesfrom
ai-updates2

Conversation

@mpadge
Copy link
Copy Markdown
Member

@mpadge mpadge commented May 25, 2026

@yabellini You wisely suggested we needed an example of AI usage disclosure. This is a PR to the ai-updates branch that does that. I've done as a separate PR so you can see what's changed. We really only have one good example to date, and it's of a package still under review. I'll keep an eye on progress, and update link and description if and when things get that far, but hopefully this should help people understand.

Good idea - thanks 👍


Checklist for dev guide maintainers, do not delete 😸

  • Review of the content in the initial language.
  • News item.
  • Translation of the content in other languages.
  • Review of the translations.

@mpadge mpadge requested a review from yabellini May 25, 2026 09:16
Copy link
Copy Markdown
Member

@maelle maelle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot! As noted elsewhere, I feel we might first want a blog post with a list of example usage + commentary. Then we can come back to updating the dev guide. What do y'all think?

Comment thread softwarereview_author.Rmd
A very general rule-of-thumb is the greater the use of generative AI tools in an rOpenSci submission, the more documentation we will expect, and the more we will expect such tools to have been used _systematically_.
Systematic tool usage includes any approach which transparently and progressively details the contribution of generative AI tools to software production.

- Please provide easy-to-find details or links on any usage of generative AI tools in your documentation, like in [this package](https://apaf-bioinformatics.github.io/HydraR/#robot-use-of-generative-ai).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add example text/structure so that one does not need to go read the link? especially as it could disappear.

Comment thread softwarereview_author.Rmd
Systematic tool usage includes any approach which transparently and progressively details the contribution of generative AI tools to software production.

- Please provide easy-to-find details or links on any usage of generative AI tools in your documentation, like in [this package](https://apaf-bioinformatics.github.io/HydraR/#robot-use-of-generative-ai).
- A very general rule-of-thumb is the greater the use of generative AI tools in an rOpenSci submission, the more documentation we will expect, and the more we will expect such tools to have been used _systematically_.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does "systematically" mean here? intentionally?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even if the next item clarifies, this sentence doesn't look accessible.

Comment thread softwarereview_author.Rmd Outdated

- Please provide easy-to-find details or links on any usage of generative AI tools in your documentation, like in [this package](https://apaf-bioinformatics.github.io/HydraR/#robot-use-of-generative-ai).
- A very general rule-of-thumb is the greater the use of generative AI tools in an rOpenSci submission, the more documentation we will expect, and the more we will expect such tools to have been used _systematically_.
- Systematic tool usage includes any approach which transparently and progressively details the contribution of generative AI tools to software production.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a bit vague? sorry 😬

@mpadge
Copy link
Copy Markdown
Member Author

mpadge commented May 29, 2026

Thanks a lot! As noted elsewhere, I feel we might first want a blog post with a list of example usage + commentary. Then we can come back to updating the dev guide. What do y'all think?

Blog post PR is ropensci/roweb3#1310 - we could wait for that before moving ahead here, if you want? but that might take a couple of weeks, so I'd prefer to merge this, and update again in response to that blog post.

@maelle
Copy link
Copy Markdown
Member

maelle commented May 29, 2026

From a quick skim, that post is more ambitious than what I was envisioning: what I meant is a blog post full of links to issue comments in software-review, and code source that was mentioned in software-review. Actual examples. Could be a first/second post?

@maelle
Copy link
Copy Markdown
Member

maelle commented May 29, 2026

So, in short, a post about what we have observed in software review threads since our first post on AI. What was good, in particular, so not shaming anyone 😁

Comment thread softwarereview_author.Rmd Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants