Skip to content

Commit 421d5f2

Browse files
authored
Switch from Contributor License Agreement (CLA) to Developer Certificate of Origin (DCO) (#18)
1 parent 4b056dd commit 421d5f2

File tree

2 files changed

+3
-23
lines changed

2 files changed

+3
-23
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ There are three important things to know:
2626
This a checklist of things to keep in your mind when opening pull requests for this project.
2727

2828
0. Before pushing anything, validate your pull request with `go test`
29-
1. Make sure you have signed the [Contributor License Agreement](#contributor-license-agreement)
29+
1. Make sure you have accepted the [Developer Certificate of Origin](#developer-certificate-of-origin-dco)
3030
2. Make sure any added dependency is licensed under Apache v2.0 license
3131
3. Strive for very high unit-test coverage and favor testing productive code over mocks
3232
(mock in depth wherever possible)
@@ -35,29 +35,9 @@ This a checklist of things to keep in your mind when opening pull requests for t
3535
Pull requests will be tested and validated by maintainers. In case small changes are needed (e.g., correcting typos), the maintainers may fix those issues themselves.
3636
In case of larger issues, you may be asked to apply modifications to your changes before the Pull Request can be merged.
3737

38-
### Contributor License Agreement
38+
### Developer Certificate of Origin (DCO)
3939

40-
When you contribute (code, documentation, or anything else), you have to be aware that your contribution is covered by the same [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0) that is applied to the Cloud Foundry CLI Java Plugin itself.
41-
Also, you need to agree to the Individual Contributor License Agreement, which can be [found here](https://gist.github.com/CLAassistant/bd1ea8ec8aa0357414e8).
42-
(This applies to all contributors, including those contributing on behalf of a company).
43-
If you agree to its content, you simply have to click on the link posted by the CLA assistant as a comment to the pull request.
44-
Click it to check the CLA, then accept it on the following screen if you agree to it.
45-
CLA assistant will save this decision for upcoming contributions and will notify you if there is any change to the CLA in the meantime.
46-
47-
#### Company Contributors
48-
49-
If employees of a company contribute code, in **addition** to the individual agreement above, there needs to be one company agreement submitted.
50-
This is mainly for the protection of the contributing employees.
51-
52-
A company representative authorized to do so needs to download, fill, and print
53-
the [Corporate Contributor License Agreement](docs/SAP%20Corporate%20Contributor%20License%20Agreement.pdf) form. Then either:
54-
55-
- Scan it and e-mail it to [opensource@sap.com](mailto:opensource@sap.com)
56-
- Fax it to: +49 6227 78-45813
57-
- Send it by traditional letter to: *Industry Standards & Open Source Team, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany*
58-
59-
The form contains a list of employees who are authorized to contribute on behalf of your company.
60-
When this list changes, please let us know.
40+
Due to legal reasons, contributors will be asked to accept a DCO before they submit the first pull request to this projects, this happens in an automated fashion during the submission process. SAP uses [the standard DCO text of the Linux Foundation](https://developercertificate.org/).
6141

6242
## Code of Conduct
6343

-104 KB
Binary file not shown.

0 commit comments

Comments
 (0)