1 To document, where patches come from without to much overhead, I
2 want to use a "sign-off" procedure on patches/commits.
4 The sign-off is a simple line at the end of the explanation for the
5 patch, which certifies that you wrote it or otherwise have the right to
6 pass it on as a open-source patch. The rules are pretty simple: if you
9 Developer's Certificate of Origin 1.1
11 By making a contribution to this project, I certify that:
13 (a) The contribution was created in whole or in part by me and I
14 have the right to submit it under the open source license
15 indicated in the file; or
17 (b) The contribution is based upon previous work that, to the best
18 of my knowledge, is covered under an appropriate open source
19 license and I have the right under that license to submit that
20 work with modifications, whether created in whole or in part
21 by me, under the same open source license (unless I am
22 permitted to submit under a different license), as indicated
25 (c) The contribution was provided directly to me by some other
26 person who certified (a), (b) or (c) and I have not modified
29 (d) I understand and agree that this project and the contribution
30 are public and that a record of the contribution (including all
31 personal information I submit with it, including my sign-off) is
32 maintained indefinitely and may be redistributed consistent with
33 this project or the open source license(s) involved.
35 then you just add a line saying
37 Signed-off-by: Random J Developer <random@developer.example.org>
39 using your real name (sorry, no pseudonyms or anonymous contributions.)
41 [ The signoff procedure is used by other projects, like kernel.org, git.
42 This texts is derived from their versions of the signoff handling. ]