Skip to content

Commit 27f628c

Browse files
authored
Merge pull request #7 from wking/contributing
CONTRIBUTING.md: Pull in from docker/opensource's project-template
2 parents 5bb1f32 + 79405cf commit 27f628c

File tree

1 file changed

+72
-0
lines changed

1 file changed

+72
-0
lines changed

CONTRIBUTING.md

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

0 commit comments

Comments
 (0)