Skip to content

feat: add genai policy to templates#288

Open
lwasser wants to merge 6 commits intopyOpenSci:mainfrom
lwasser:genai-template
Open

feat: add genai policy to templates#288
lwasser wants to merge 6 commits intopyOpenSci:mainfrom
lwasser:genai-template

Conversation

@lwasser
Copy link
Copy Markdown
Member

@lwasser lwasser commented Mar 5, 2026

This PR takes the work we did here:

and turns it into a few check boxes in our issue template. This will then be complemented by a second pr to the peer review guide around new policies.

@lwasser
Copy link
Copy Markdown
Member Author

lwasser commented Mar 5, 2026

IMPORTANT: when we merge this, I think our pyOSMeta build MIGHT break on these issues. We will want to update the model to include Genai tools used as a start, and we may need to increase the lines of hte template that are parsed.

@lwasser
Copy link
Copy Markdown
Member Author

lwasser commented Mar 5, 2026

This is failing because of all-contributors which we are working on now. so we can ignore that failure for now until the new urls are sorted out.


- [ ] This package has a public development history spanning 3-6 months, with commits distributed over time that reflect **iterative, thoughtful development.**
- [ ] All code in this package has been **carefully reviewed by a human**. Its implementation is also understood by the authors submitting the package.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Can we shorten this? OR we can link to more about this. perhaps remove the translation piece

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I'd keep this as-is. There was a decent chunk of folks who didn't look at links present, this forces acknowledgement.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@coatless Does Leah's version below look ok to you? Still includes the bit about communication written by human, but links to our peer-review guide for the translation details.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sure; but, I'll revoice that the more links present across multiple guides the less likely the submitters are going to go to them. Again, these are built-in to the template meaning that unless they copy & paste the URL to visit or switch to preview mode and click it's highly unlikely that these documents will be reviewed.


- [ ] This package has a public development history spanning 3-6 months, with commits distributed over time that reflect **iterative, thoughtful development.**
- [ ] All code in this package has been **carefully reviewed by a human**. Its implementation is also understood by the authors submitting the package.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Suggested change
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). [See more](llms & translation)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Link to section in guide on translation and communication


### If you have a policy around generative AI use in your project, please provide a link to it below:

- _Your link here (remove this line if you don't have a link)_
Copy link
Copy Markdown

@MicahGale MicahGale Mar 12, 2026

Choose a reason for hiding this comment

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

Suggested change
- _Your link here (remove this line if you don't have a link)_
_[Your link here](foo.com) (remove this line if you don't have a link)_

[Read our full generative ai policy here.](https://www.pyopensci.org/software-peer-review/our-process/policies.html#disclosure-of-generative-ai-use-in-pyopensci-reviewed-packages)
- [ ] This package has a public development history spanning 3-6 months, with commits distributed over time that reflect **iterative, thoughtful development.**
- [ ] All code in this package has been **carefully reviewed by a human**. Its implementation is also understood by the authors submitting the package.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Suggested change
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). [Learn more]()

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.

4 participants