@@ -26,6 +26,27 @@ require such detailed description.
26
26
To get good practical examples of good commits and their messages, browse
27
27
the ` git log ` of the project.
28
28
29
+ MicroPython doesn't require explicit sign-off for patches ("Signed-off-by"
30
+ lines and similar). Instead, the commit message, and your name and email
31
+ address on it construes your sign-off of the following:
32
+
33
+ * That you wrote the change yourself, or took it from a project with
34
+ a compatible license (in the latter case the commit message, and possibly
35
+ source code should provide reference where the implementation was taken
36
+ from and give credit to the original author, as required by the license).
37
+ * That you are allowed to release these changes to an open-source project
38
+ (for example, changes done during paid work for a third party may require
39
+ explicit approval from that third party).
40
+ * That you (or your employer) agree to release the changes under
41
+ MicroPython's license, which is the MIT license. Note that you retain
42
+ copyright for your changes (for smaller changes, the commit message
43
+ conveys your copyright; if you make significant changes to a particular
44
+ source module, you're welcome to add your name to the file header).
45
+ * Your signature for all of the above, which is the 'Author' line in
46
+ the commit message, and which should include your full real name and
47
+ a valid and active email address by which you can be contacted in the
48
+ foreseeable future.
49
+
29
50
Python code conventions
30
51
=======================
31
52
0 commit comments