Skip to content

Adding AI disclosures updates#259

Open
sfc-gh-swalia wants to merge 1 commit into
apache:mainfrom
sfc-gh-swalia:swalia-ai-usage
Open

Adding AI disclosures updates#259
sfc-gh-swalia wants to merge 1 commit into
apache:mainfrom
sfc-gh-swalia:swalia-ai-usage

Conversation

@sfc-gh-swalia

Copy link
Copy Markdown
Contributor

Summary

This PR adds section to CONTRIBUTING.md and adds optional disclosure checkbox as part of PR template.

@jbonofre jbonofre left a comment

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.

First glance: I love it 😄

I will do the review/merge tomorrow morning my time.

Comment thread CONTRIBUTING.md
(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.

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.

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.

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.

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?

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.

@LiJie20190102 LiJie20190102 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM,+1

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.

5 participants