Skip to content

Add CONTRIBUTING.md with CLA and AI text - #1054

Merged
TApplencourt merged 1 commit into
mainfrom
add-contributing-file
Sep 25, 2026
Merged

TApplencourt merged 1 commit into
mainfrom
add-contributing-file

Conversation

@KhronosWebservices

Copy link
Copy Markdown
Member

Adds CONTRIBUTING.md with legal mandated AI-assisted-contributions disclosure
and the Khronos Mixed Repository CLA pre-disclosure.

… Contributions block of text and adds CLA pre-disclosure with a link to the CLA text

@gmlueck gmlueck 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.

When I follow the link at (https://www.khronos.org/cla/KhronosGroup/SYCL-Docs), it says this under Outbound License Terms:

Specifications. Khronos licenses its entire specifications under the terms of the Khronos Specification Copyright License at: www.khronos.org/legal/Khronos_Specification_Copyright_License_Header.

However, the published SYCL specification also lists its license, and that is not exactly the same as the content of "Khronos_Specification_Copyright_License_Header". You can see the published license at the very beginning of the spec:

https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html

Should we do something to resolve this difference?

@KhronosWebservices

Copy link
Copy Markdown
Member Author

@oddhack can you take a look?

@gmlueck Might be good to open this as a separate issue, as it doesn't have any bearing on this PR specifically. The SYCL Docs repo is under the Mix Repo CLA and this PR only clarifies that fact, and the AI contributor paragraph.

@KhronosWebservices

Copy link
Copy Markdown
Member Author

@gmlueck Okay to merge this PR now?

@gmlueck

gmlueck commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

@TApplencourt this is up to you as chair. I have no concerns.

@KhronosWebservices: We normally approve PRs to merge in the weekly WG call, but the agenda for our last call did not have time for this. Is this something that is urgent, or can it wait for next week's call?

@KhronosWebservices

Copy link
Copy Markdown
Member Author

Thanks @gmlueck Can wait til next week.

@TApplencourt

TApplencourt commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

I was waiting for @oddhack feedback too. Don't want to merge conflicting-lawyers-thingy : )
But because it's a Khronos PR, I have no objection neither

@KhronosWebservices

Copy link
Copy Markdown
Member Author

This PR doesn't touch licensing, just adding pre-disclosures for the existing license and adds the new required AI text. The CLA is already in place and being used.

@TApplencourt

Copy link
Copy Markdown
Contributor

👍🏽 we will follow up on another issue then!
Thanks

@TApplencourt
TApplencourt merged commit a868b51 into main Sep 25, 2026
3 checks passed
@KhronosWebservices

Copy link
Copy Markdown
Member Author

Thank you everyone!

gmlueck pushed a commit that referenced this pull request Sep 25, 2026
Cherry pick #1054 from main
(cherry picked from commit a868b51)
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.

3 participants