lkml.org 
[lkml]   [2012]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH v2 4/6] copyleft-next: embrace the Signed-off-by practice
Date
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

The idea is taken from Linus Torvald's subsurface
project [0] README file. The Signed-off-by is widely
used in public projects and we stand to gain to make
its usage more prevalent. The meaning of the
Signed-off-by is borrowed from the Linux kernel's.

[0] git://github.com/torvalds/subsurface.git

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
CONTRIBUTING | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 8f214b1..966366c 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -5,6 +5,36 @@ All original contributions to copyleft-next are dedicated to the
public domain to the maximum extent permitted by applicable law,
pursuant to CC0. See CC0 for further details.

+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
+
+Also, please write good git commit messages. A good commit message
+looks like this:
+
+ Header line: explaining the commit in one line
+
+ Body of commit message is a few lines of text, explaining things
+ in more detail, possibly giving some background about the issue
+ being fixed, etc etc.
+
+ The body of the commit message can be several paragraphs, and
+ please do proper word-wrap and keep columns shorter than about
+ 74 characters or so. That way "git log" will show things
+ nicely even when it's indented.
+
+ Reported-by: whoever-reported-it
+ Signed-off-by: Your Name <youremail@yourhost.com>
+
+where that header line really should be meaningful, and really should be
+just one line. That header line is what is shown by tools like gitk and
+shortlog, and should summarize the change in one readable line of text,
+independently of the longer explanation.
+
Contributions from individual free/libre/open source software project
participants, regardless of their views on copyleft, and regardless of
their opinions on existing licenses such as the GNU GPLv2 and its
--
1.7.10.rc1.22.gf5241


\
 
 \ /
  Last update: 2012-07-12 20:42    [W:0.417 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site