docs(legal): prepare contributor agreement draft - #37
Merged
Merged
Conversation
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
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.
Summary
Prepares a non-operative Harmony-based Contributor License Agreement planning draft and a separate adoption checklist for HitTheKit's possible future dual-licensing model.
The proposed planning model is a copyright license, not an assignment: contributors retain copyright while the draft evaluates the copyright and patent permissions needed for community and separate commercial/proprietary distribution.
Important status
Human review required
The checklist intentionally leaves adoption blockers unresolved, including the receiving legal party, address/contact, governing law and forum, privacy/data retention, electronic signatures, employer/entity and minor contributors, patent scope, prior contributions, and the exact GPL-to-MPL transition.
Validation
Scope
Documentation only. No merge, no CLA activation, no CLA Assistant configuration, and no relaxation of the current contribution block.