From: Ondřej Surý Date: Thu, 16 Oct 2025 16:23:17 +0000 (+0200) Subject: Change the CONTRIBUTING to use Developer's Certificate of Origin 1.1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=37bb5026e8ee677510165ddb270892566ebc20f4;p=thirdparty%2Fbind9.git Change the CONTRIBUTING to use Developer's Certificate of Origin 1.1 (cherry picked from commit 845eb2ebbc0f07fd9588ba844e61d09afd4165e4) --- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f78595aa415..e0770dc3407 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -112,12 +112,46 @@ BIND is licensed under the Earlier versions (BIND 9.10 and earlier) were licensed under the [ISC License](https://www.isc.org/licenses/) -ISC does not require an explicit copyright assignment for patch -contributions. However, by submitting a patch to ISC, you implicitly -certify that you are the author of the code, that you intend to relinquish -exclusive copyright, and that you grant permission to publish your work -under the open source license used for the BIND version(s) to which your -patch will be applied. +ISC does not require an explicit copyright assignment for patch contributions. +However, with the modern open source movement, it is very easy to contribute +patches and people often don't think about the legal implications. Is the code +you're about to contribute really yours? If you work 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? + +BIND 9 adopted [Developer Certificate of Origin](https://developercertificate.org/), +which is a nice half a page document by Linux foundation. By contributing your patch, +you confirm that you follow and agree with the following: + +``` +Developer's Certificate of Origin 1.1 + +By making a contribution to this project, I certify that: + +(a) The contribution was created in whole or in part by me and I + have the right to submit it under the open source license + indicated in the file; or + +(b) The contribution is based upon previous work that, to the best + of my knowledge, is covered under an appropriate open source + license and I have the right under that license to submit that + work with modifications, whether created in whole or in part + by me, under the same open source license (unless I am + permitted to submit under a different license), as indicated + in the file; or + +(c) The contribution was provided directly to me by some other + person who certified (a), (b) or (c) and I have not modified + it. + +(d) I understand and agree that this project and the contribution + are public and that a record of the contribution (including all + personal information I submit with it, including my sign-off) is + maintained indefinitely and may be redistributed consistent with + this project or the open source license(s) involved. +``` #### BIND code