Skip to content

Adding AI disclosures updates #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sfc-gh-swalia wants to merge 1 commit into
base: main
Choose a base branch
from
+20 −0
Open

Adding AI disclosures updates #259

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,7 @@
### Compliance
- [ ] ASF license headers are present on all new source files
- [ ] No third-party dependencies are added without PMC/IPMC approval

### AI Tool Disclosure (Check the box below if used - Optional)
- [ ] This contribution used AI-assisted tooling (if yes, note tool/model below)

16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,22 @@ on file with the ASF. If you are contributing on behalf of your employer, a
may also be required. Please keep individual commits signed off and attributed to
the correct author so that provenance is clear.

## AI-Assisted Contributions

We welcome contributions that use AI-assisted tooling (GitHub Copilot, Claude,
ChatGPT, etc.). Per the
[ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html):

- You may use any AI tool provided the output does not include third-party
copyrighted material under an incompatible license
- You remain personally responsible for all code you submit, regardless of
how it was produced
- Please disclose AI tool usage in your PR description or commit message
(e.g., `Co-authored-by: Copilot <copilot@github.com>` or a note in the PR)

This is not a gate — it is a transparency practice that helps the community
understand how contributions are produced.

@khush-bhatia khush-bhatia Jul 23, 2026

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.

Wondering if this is required by Apache ? Else I think we should skip it since directionally it looks like most PRs would be assisted by AI tools.

cc @jbonofre

We also want to keep our PR template bounded.

@jbonofre jbonofre Jul 24, 2026

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.

This is not strictly required from ASF standpoint. Especially the co-authored-by statement is not mandatory.

At the ASF, we might ask the AI tool used mostly to verify there's no legal issue (trademark, IP, etc).

I'm expecting from this PR just a link to https://www.apache.org/legal/generative-tooling.html for instance.

@jbonofre jbonofre Jul 24, 2026

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 Apache-2.0 license, and the Apache Individual Contribution License Agreement, both remind contributors that they are responsible for disclosing any copyrighted materials in submitted contributions that are not their original creation. This is as true when using generative AI tooling, as it is when using materials from public websites or code from other open-source projects.

@willpugh willpugh Jul 24, 2026

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 think the critical part is that each person is responsible for their contribution.

I think the "co-authored" is a little funny. I thought AI had no copyright claims on the code it generated. Also, it is common for me to use multiple harnesses (codex, claudecode, opencode, cursor) and multiple models with them (opus, sonnet, gpt, composer (and I expect some GLM in the future)).

Should we list all of them?

@willpugh willpugh Jul 24, 2026

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.

O.k. I looked at the generative-tooling link. If you think the harness and/or model helps later analysis. We can add it. However, let's cover the "multi" case and whether we want models as well as harness.

@sfc-gh-swalia sfc-gh-swalia Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@khush-bhatia @jbonofre @willpugh - thanks for the feedback! Here's what I am thinking

  • We remove the PR template checkbox entirely
  • In contributing.md section - we limit to You remain personally responsible for all code you submit, regardless of how it was produced + ASF Gen tooling guidance.

On Will's question about the multi-tool case - I think we skip prescribing format altogether. People can note tooling if they want, but we don't need to standardize how. The ASF page covers the legal angle and that should be enough.

I can push those changes quickly. Sound good?

@khush-bhatia khush-bhatia Jul 24, 2026

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.

Yes sounds good. Thanks


## Contribution Workflow

The project's canonical repository is hosted at
Expand Down