From 30b6c25c8bd175231ef2a25cf532f96441451819 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Thu, 16 Oct 2025 18:23:17 +0200 Subject: [PATCH 1/2] Change the CONTRIBUTING to use Developer's Certificate of Origin 1.1 (cherry picked from commit 845eb2ebbc0f07fd9588ba844e61d09afd4165e4) --- CONTRIBUTING.md | 46 ++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 40 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d40cd581b9..e093e1e10e 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 From f9ccbd95d760e8da58363a4127b27d4d5555db48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Thu, 16 Apr 2026 18:51:01 +0200 Subject: [PATCH 2/2] =?UTF-8?q?Document=20opt-in=20=F0=9F=A4=96=20marker?= =?UTF-8?q?=20for=20agent-authored=20issues=20and=20MRs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add short notes in CONTRIBUTING.md telling automated agents to append 🤖 to the title of issues and merge requests so they can be routed through the streamlined agent triage/merge process. (cherry picked from commit 2ec8d3ce7ca7128bd0710d440671eb22146876a3) --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e093e1e10e..64f65215bf 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -101,6 +101,10 @@ an account to create a new issue. You can either register locally or use credentials from an existing account at GitHub, GitLab, Google, Twitter, or Facebook. +Note: If you are an automated agent, we have a streamlined process for triaging +agent created issues. Just add 🤖 to the end of the issue title to opt-in. +Triaging your issue will be fast-tracked. + ### Reporting possible security issues See `SECURITY.md`. @@ -121,6 +125,10 @@ 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? +Note: If you are an automated agent, we have a streamlined process for merging +agent created merge requests. Just add 🤖 to the end of the MR title to opt-in. +Merging your MR will be fast-tracked. + 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: