diff options
| author | Tomek Mrugalski <tomek@isc.org> | 2021-06-18 12:28:58 +0200 |
|---|---|---|
| committer | Tomek Mrugalski <tomek@isc.org> | 2021-06-23 13:55:39 +0200 |
| commit | ccdc58d724e98109e7bc134c34b8d77c277510e5 (patch) | |
| tree | 46bf25e87be09df95abde6111f907a53f6844fe7 | |
| parent | [#1895] Added section for beginners. (diff) | |
| download | kea-ccdc58d724e98109e7bc134c34b8d77c277510e5.tar.xz kea-ccdc58d724e98109e7bc134c34b8d77c277510e5.zip | |
[#1895] Added Developer Certificate of Origin
| -rw-r--r-- | CONTRIBUTING.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c724e61d42..218f682b34 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,18 @@ Don't be discouraged if a ticket that looks interesting to you is not marked for a bit of DHCP protocol or C++ programming knowledge, but they're definitely all doable. If in doubt, ask on kea-dev list for suggestions or guidance. +## A bit of a legal warning + +With the modern open source movement, it is very easy to contribute patches and people often don't think +about the legal mechanism behind those. Is the code you're about to contribute really yours? If you're working +for a company and you developed it during your work hours, it's likely to be owned by the company you work +for. Are they OK with you contributing this? Are they OK with the fact that this will be open source and other +users and companies, even possibly a competitor, may use it? + +Kea adopted Developer Certificate of Origin, which is a nice half a page document by Linux foundation. You can +read it [here](https://developercertificate.org/). By contributing your patch, you confirm that you follow +and agree with DCO. + ## Writing a patch Before you start working on a patch or a new feature, it is a good idea to discuss it first with Kea |