diff options
| author |  Scott Chacon <schacon@gmail.com> | 2011-09-06 12:32:51 -0700 |
|---|---|---|
| committer | Scott Chacon <schacon@gmail.com> | 2011-09-06 12:33:52 -0700 |
| commit | dfa6a6e1d15314e9f259f1df9368659a998dfbe2 (patch) | |
| tree | 38ae889a283f8201d47c456961c9ceb67fb494c2 /README | |
| parent | c0a429457ab9fae5e6995777b869b111ef32be74 (diff) | |
| download | subsurface-dfa6a6e1d15314e9f259f1df9368659a998dfbe2.tar.gz | |
Add more explicit contributing explanation
Most developers on GitHub are not used to projects that use the Signed-off-by convention.
They do, however, tend to read the READMEs to see which conventions the author prefers
to follow. If you are explicit about what you prefer in the README with easy to follow
instructions, it is more likely people will follow those conventions.
Signed-off-by: Scott Chacon <schacon@gmail.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -38,3 +38,14 @@ my divemaster course, so they are from following open water students along (many of them the confined*water dives). There a lot of the action is at the surface, so some of the "dives" are 4ft deep and 2min long. + +Contributing: + +Please either send me signed-off patches or a pull request with +signed-off commits. If you don't sign off on them, I will not accept +them. This means adding a line that says "Signed-off-by: Name <email>" +at the end of each commit, indicating that you wrote the code and have +the right to pass it on as an open source patch. + +See: http://gerrit.googlecode.com/svn/documentation/2.0/user-signedoffby.html + |