dco
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
dco [2017/07/17 22:36] emsearcy reference IP policies |
dco [2017/07/17 22:48] emsearcy re-word |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * A contributor agreement may be signed by a third party, like a company, on behalf of its employees, whereas the DCO is always an attestation by the author of the contribution. | * A contributor agreement may be signed by a third party, like a company, on behalf of its employees, whereas the DCO is always an attestation by the author of the contribution. | ||
| - | ===== Policy ===== | + | ===== IP policy requirements ===== |
| - | In compliance with their IP policies, Linux Foundation projects MUST incorporate a mandatory mechanism to enforce the DCO on all contributions. | + | When a Linux Foundation project's IP policy requires DCO signoffs for contributions, a mechanism shall be set up to enforce them. |
| - | In the contribution guidelines for each project (e.g. a CONTRIBUTING.md file) the project SHOULD make explicit that the DCO is required, and that commit sign-offs of the form ''Signed-off-by:'' are attestations according to [[https://developercertificate.org/]]. | + | In the contribution guidelines for each project (e.g. a CONTRIBUTING.md file) the project should explain the DCO requirement, and that commit sign-offs of the form ''Signed-off-by:'' are attestations according to [[https://developercertificate.org/]]. |
| ===== Enabling DCO enforcement ===== | ===== Enabling DCO enforcement ===== | ||
dco.txt ยท Last modified: 2019/12/26 18:20 by emsearcy
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
