1 # Contributing to Docker open source projects
2 
3 Want to hack on this project? Awesome! Here are instructions to get you started.
4 
5 This project is a part of the [Docker](https://www.docker.com) project, and follows
6 the same rules and principles. If you're already familiar with the way
7 Docker does things, you'll feel right at home.
8 
9 Otherwise, go read Docker's
10 [contributions guidelines](https://github.com/docker/docker/blob/master/CONTRIBUTING.md),
11 [issue triaging](https://github.com/docker/docker/blob/master/project/ISSUE-TRIAGE.md),
12 [review process](https://github.com/docker/docker/blob/master/project/REVIEWING.md) and
13 
14 For an in-depth description of our contribution process, visit the
15 contributors guide: [Understand how to contribute](https://docs.docker.com/opensource/workflow/make-a-contribution/)
16 
17 ### Sign your work
18 
19 The sign-off is a simple line at the end of the explanation for the patch. Your
20 signature certifies that you wrote the patch or otherwise have the right to pass
21 it on as an open-source patch. The rules are pretty simple: if you can certify
22 the below (from [developercertificate.org](http://developercertificate.org/)):
23 
24 ```
25 Developer Certificate of Origin
26 Version 1.1
27 
28 Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
29 660 York Street, Suite 102,
30 San Francisco, CA 94110 USA
31 
32 Everyone is permitted to copy and distribute verbatim copies of this
33 license document, but changing it is not allowed.
34 
35 Developer's Certificate of Origin 1.1
36 
37 By making a contribution to this project, I certify that:
38 
39 (a) The contribution was created in whole or in part by me and I
40     have the right to submit it under the open source license
41     indicated in the file; or
42 
43 (b) The contribution is based upon previous work that, to the best
44     of my knowledge, is covered under an appropriate open source
45     license and I have the right under that license to submit that
46     work with modifications, whether created in whole or in part
47     by me, under the same open source license (unless I am
48     permitted to submit under a different license), as indicated
49     in the file; or
50 
51 (c) The contribution was provided directly to me by some other
52     person who certified (a), (b) or (c) and I have not modified
53     it.
54 
55 (d) I understand and agree that this project and the contribution
56     are public and that a record of the contribution (including all
57     personal information I submit with it, including my sign-off) is
58     maintained indefinitely and may be redistributed consistent with
59     this project or the open source license(s) involved.
60 ```
61 
62 Then you just add a line to every git commit message:
63 
64     Signed-off-by: Joe Smith <joe.smith@email.com>
65 
66 Use your real name (sorry, no pseudonyms or anonymous contributions.)
67 
68 If you set your `user.name` and `user.email` git configs, you can sign your
69 commit automatically with `git commit -s`.