-
Notifications
You must be signed in to change notification settings - Fork 0
Resolve license ambiguity #4
Copy link
Copy link
Open
Labels
area: docs-contractsDocs, wiki, ABI/API contracts, hardware-readiness wording.Docs, wiki, ABI/API contracts, hardware-readiness wording.needs: designNeeds design decision or scope clarification.Needs design decision or scope clarification.priority: P1-highHigh-priority work for the current roadmap.High-priority work for the current roadmap.type: docsDocumentation, contracts, or roadmap work.Documentation, contracts, or roadmap work.
Description
Metadata
Metadata
Assignees
Labels
area: docs-contractsDocs, wiki, ABI/API contracts, hardware-readiness wording.Docs, wiki, ABI/API contracts, hardware-readiness wording.needs: designNeeds design decision or scope clarification.Needs design decision or scope clarification.priority: P1-highHigh-priority work for the current roadmap.High-priority work for the current roadmap.type: docsDocumentation, contracts, or roadmap work.Documentation, contracts, or roadmap work.
Summary
Resolve the repository license ambiguity before broader release or contribution growth.
Problem / objective
LICENSEcontains MIT license text but also saysLicense to be decided, andREADME.mdsays the license is undecided. This needs a human decision before cleanup.Acceptance criteria
LICENSE,README.md, and contributor-facing docs agree.Validation
docs-onlymanual-reviewRelevant files
LICENSEREADME.mdCONTRIBUTING.md