docs(compliance): the klib notice stance (#1166) - #1245
Merged
Merged
Conversation
…hes Kotlin/Native consumers (#1166) Kotlin/Native klibs have no META-INF resource mechanism, so the third-party notices file cannot physically travel inside them. Document the decided stance in the notices files themselves: the jar of the same release carries the authoritative notice for every artifact of that release, the repo is the versioned source of truth, and an app statically linking a SKaiNET klib carries the NeoGPU MIT notice in its own attributions. Closes the last technical checklist item of #1166 short of the upstream courtesies. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YKeDSK4JF295y53Uvez954
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The klib-coverage decision #1166's checklist flagged: Kotlin/Native klibs have no
META-INFresource mechanism, soTHIRD-PARTY-NOTICES.mdcannot physically travel inside them the way it does in the jar and AAR — yet the klibs embed the same compiled NeoGPU code.The stance, now documented in both notices files where an auditor will look:
LICENSES/MIT.txt, the.licensesidecar, the vendor README.With this, every technical checklist item of #1166 is done; what remains there is the upstream courtesies (drafted, awaiting the maintainer's go) and the close-out summary.
🤖 Generated with Claude Code
https://claude.ai/code/session_01YKeDSK4JF295y53Uvez954