Skip to content

Add AI Policy - #2046

Open
reinecke wants to merge 9 commits into
AcademySoftwareFoundation:mainfrom
reinecke:feature/add-ai-policy
Open

reinecke wants to merge 9 commits into
AcademySoftwareFoundation:mainfrom
reinecke:feature/add-ai-policy

Conversation

@reinecke

Copy link
Copy Markdown
Collaborator

Summarize your change.

This PR adds an AI coding policy to provide clarity for contributors using AI coding assistants.

This policy is forked from the thoughtful policy provided by OpenImageIO.

@codecov-commenter

codecov-commenter commented Sep 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.48%. Comparing base (a639246) to head (8638df4).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2046   +/-   ##
=======================================
  Coverage   83.48%   83.48%           
=======================================
  Files         182      182           
  Lines       13517    13517           
  Branches     1254     1254           
=======================================
  Hits        11284    11284           
  Misses       2060     2060           
  Partials      173      173           
Flag Coverage Δ
py-unittests 83.48% <ø> (ø)

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


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a639246...8638df4. Read the comment docs.

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

@darbyjohnston

Copy link
Copy Markdown
Contributor

How about attribution just for the PR? Otherwise every commit will need DCO + LLM attribution, which seems like a lot.

Comment thread docs/tutorials/AI_Policy.md Outdated
Comment thread .github/PULL_REQUEST_TEMPLATE.md Outdated
@jminor

jminor commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator

How about attribution just for the PR? Otherwise every commit will need DCO + LLM attribution, which seems like a lot.

The DCO auto-enforcement system checks every commit, but git rebase --signoff makes that easy to batch apply. I agree that requiring the AI disclosure in every commit would be really annoying. I support the idea of only requiring it in the PR, or perhaps in "at least one commit" so we can carry that over into the squashed commit when we land each PR.

@reinecke

Copy link
Copy Markdown
Collaborator Author

I agree that requiring the AI disclosure in every commit would be really annoying.

+1

I support the idea of only requiring it in the PR, or perhaps in "at least one commit" so we can carry that over into the squashed commit when we land each PR.

This seems like a reasonable adjustment to me.

meshula
meshula approved these changes Sep 14, 2026
reinecke and others added 9 commits September 15, 2026 13:33
Signed-off-by: Eric Reinecke <ereinecke@netflix.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
…t been merged yet

Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
… have 1st party support.

Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>

@apetrynet apetrynet left a comment

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.

One minor suggestion, but this looks good to me

Comment on lines +61 to +64
Even when using a coding assistant to write the code, you are strongly
encouraged to write your own PR description, in your own words, if for no
other reason than to force yourself to understand the code well enough to
describe it to others.

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.

Can we highlight this with bold or itallic?

Suggested change
Even when using a coding assistant to write the code, you are strongly
encouraged to write your own PR description, in your own words, if for no
other reason than to force yourself to understand the code well enough to
describe it to others.
**Even when using a coding assistant to write the code, you are strongly
encouraged to write your own PR description, in your own words, if for no
other reason than to force yourself to understand the code well enough to
describe it to others.**

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.

7 participants