Drop requirement for a CLA #369
No reviewers
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!369
Loading…
Reference in a new issue
No description provided.
Delete branch "dh/drop-cla"
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 Crypto project no longer requires a CLA. Contributions from now on
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.
Update README.md and CONTRIBUTING.md to explain the new licensing model.
Add a copy of the DCO to the project.
Expand the full Apache-2.0 license text in the LICENSE file and remove the
redundant apache-2.0.txt.
Fix inconsistent list formatting in CONTRIBUTING.md.
@ -24,7 +19,8 @@ Making a Contribution1. Write a test which shows that the bug was fixed or that the feature works as expected.Additionally to the dco, we could consider mentioning the inbound licences here too. (The dco makes a vague reference to an open source licence, it is not impossible to figure out what it is, but I think we should make the job easier for our contributors.)
@ -2,8 +2,6 @@As discussed earlier, we could try clarifying the inbound licenses a little bit. Maybe writing something like this in addition: "The inbound licences are both Apache-2.0 AND GPL-2.0-or-later simultaneously, that is, contributions are made under both."
@ -24,7 +19,8 @@ Making a Contribution1. Write a test which shows that the bug was fixed or that the feature works as expected.OK, I'll link the license section of the readme here.
@ -2,8 +2,6 @@I think I already clarified that point. Your suggestion just says the same thing twice IMO.
LGTM
Note: the CI is only failing the Mbed OS tests, which are a known issue clearly independent from this PR.
The CI fails on Mbed OS, but not for the known issue we had. This PR deletes the file
apache-2.0.txt, which is targeted explicitly by the importer script in Mbed OS.@Patater The Mbed OS importer script will need updating once this PR is merged.
Thanks for the heads up. We'll fix this when we update the version of Mbed TLS in Mbed OS.