Blame


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