mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-01-19 14:25:27 +00:00
Code Issues Projects Releases Packages Wiki Activity

Add more explicit contributing explanation

Browse source 
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>
This commit is contained in:
Scott Chacon 2011-09-06 12:32:51 -07:00
parent c0a429457a
commit dfa6a6e1d1
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
README
View file

@ -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 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 action is at the surface, so some of the "dives" are 4ft deep and 2min
long. 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