diff options
author | Bryce Harrington <bryce@osg.samsung.com> | 2016-03-04 10:50:23 -0800 |
---|---|---|
committer | Bryce Harrington <bryce@osg.samsung.com> | 2016-03-07 11:57:34 -0800 |
commit | ba2ee84113e7f9fef9af2ec3998ee437adab5382 (patch) | |
tree | 93649eb3075775895b800facb2ee69c073d13cd4 | |
parent | 973a70dbb5a1d2865ec63a268e939585da5a951f (diff) | |
download | wayland-ba2ee84113e7f9fef9af2ec3998ee437adab5382.tar.gz |
doc: Note strong recommendation to use S-o-b in contributions
Signed-off-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-rw-r--r-- | doc/Contributing | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/Contributing b/doc/Contributing index fe90614..65565dc 100644 --- a/doc/Contributing +++ b/doc/Contributing @@ -30,6 +30,15 @@ cope with the way git log presents them. See [2] for a recommend reading on writing commit messages. +Your patches should also include a Signed-off-by line with your name and +email address. If you're not the patch's original author, you should +also gather S-o-b's by them (and/or whomever gave the patch to you.) The +significance of this is that it certifies that you created the patch, +that it was created under an appropriate open source license, or +provided to you under those terms. This lets us indicate a chain of +responsibility for the copyright status of the code. + +We won't reject patches that lack S-o-b, but it is strongly recommended. == Tracking patches and following up == |