Mbed Crypto to drop requirement for a CLA #371
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto#371
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Mbed TLS and Mbed Crypto projects are shortly about to drop their requirement for all contributions to have a CLA. The changes are implemented in these Pull Requests:
https://github.com/ARMmbed/mbed-crypto/pull/369
https://github.com/ARMmbed/mbedtls/pull/3051
After they merged, new contributions must be made under both Apache-2.0 AND GPL-2.0-or-later licenses, to enable LTS (Long Term Support) branches of the software to continue to be provided under either Apache-2.0 OR GPL-2.0-or-later. Contributors must accept the terms
of the Developer Certificate of Origin (DCO) by adding a Signed-off-by: line to
each commit message.
The software on the development branch continues to be provided under
Apache-2.0.
For existing PRs, contributors who have not yet signed the CLA will be asked to resubmit their PR(s) under the new licensing model above. Contributors who have already signed the CLA do not need to resubmit their PR(s).
The intention is that once the current LTS branches expire, the licensing model will change again so that contributions are made under Apache-2.0 only, resulting in a simple inbound=outbound licensing model.
Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-1047