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