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