Skip to content

Add AI policy to contribution guide#3959

Open
blnicho wants to merge 6 commits into
Pyomo:mainfrom
blnicho:ai-policy
Open

Add AI policy to contribution guide#3959
blnicho wants to merge 6 commits into
Pyomo:mainfrom
blnicho:ai-policy

Conversation

@blnicho
Copy link
Copy Markdown
Member

@blnicho blnicho commented May 19, 2026

Summary/Motivation:

This PR adds an AI contribution policy to our contributor guide based on discussions we've had at the Pyomo developer meetings. This is meant to be a "living" policy that will be regularly updated as the tools and our observations evolve. Feedback and comments are welcome.

Changes proposed in this PR:

  • Add AI contribution policy to the contributor guide
  • Update PR template with an "AI-Use Disclosure" section

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

  1. I agree my contributions are submitted under the BSD license.
  2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

@blnicho blnicho requested review from jsiirola and mrmundt May 19, 2026 18:01
Comment thread doc/OnlineDocs/contribution_guide.rst Outdated
Comment thread doc/OnlineDocs/contribution_guide.rst Outdated
Comment thread doc/OnlineDocs/contribution_guide.rst Outdated
Comment on lines +191 to +192
PR and issue. Help us out by keeping comments short and direct. PR review comments
can be marked as resolved without commenting "Done" on every one.
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.

I am hesitant about the second sentence on PR review comments. We have gone back and forth about how people should resolve comments (e.g., should they wait until the reviewer says it's good?).

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.

I often respond to comments (manually) saying I have completed a requested change.

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.

But maybe I should not do that?

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.

Yeah, that's why I don't think I like the guidance here. Even we don't universally follow this.

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.

I'm fine with removing it and will make that change.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (2a8e709) to head (be9df8e).
⚠️ Report is 73 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3959      +/-   ##
==========================================
+ Coverage   90.11%   90.13%   +0.02%     
==========================================
  Files         908      909       +1     
  Lines      108378   109274     +896     
==========================================
+ Hits        97660    98492     +832     
- Misses      10718    10782      +64     
Flag Coverage Δ
builders 29.11% <ø> (-0.01%) ⬇️
default 86.09% <ø> (?)
expensive 35.14% <ø> (?)
linux 87.62% <ø> (-1.99%) ⬇️
linux_other 87.62% <ø> (+<0.01%) ⬆️
oldsolvers 28.07% <ø> (+<0.01%) ⬆️
osx 83.06% <ø> (+0.01%) ⬆️
win 85.37% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread .github/PULL_REQUEST_TEMPLATE.md
blnicho and others added 3 commits May 19, 2026 14:36
Co-authored-by: Miranda Mundt <55767766+mrmundt@users.noreply.github.com>
Co-authored-by: John Siirola <jsiirola@users.noreply.github.com>
Removed redundant instruction about marking PR review comments as resolved.
Review process:
- [ ] ALL AI-generated content was rewritten by the PR author
- [ ] ALL AI-generated content was thoroughly reviewed and verified by the PR author
- [ ] AI-generated content was contributed directly to the repository
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.

Is the intent behind this line to check if "CoPilot did it for me"? If so, I wouldn't say it's entirely clear.

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.

I think this section is meant to help us understand the extent to which the contributor reviewed the AI-generated content but this was a change suggested by @jsiirola so I'm hoping he'll also chime in.

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.

The original template was a request for free-response from the author. My concern is that they won't know what we are looking for and could write anything from a novel to the equivalent of "LGTM". The idea here is for a simple template to prompt them to to directly answer our most important questions.

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