Commit e721e221 authored by Guido Gunther's avatar Guido Gunther

Add developer certificate or origin

This makes sure contributors know what they sign off.
Based on https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst
parent c80241cf
.. _appendix:
Appendix
========
.. toctree::
Appendix/dco
.. _DCO:
Develper Certificate of Origin
==============================
The Developer Certificate of Origin (DCO) ensures that persons contributing
code are allowed to do so and that the project stays under a free license.
This is indicated by a sign-off.
The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch. The rules are pretty simple: if you
can certify the below:
.. literalinclude:: dco.txt
then you just add a line saying::
Signed-off-by: Random J Developer <random@developer.example.org>
using your real name (sorry, no pseudonyms or anonymous contributions.)
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
``
......@@ -49,7 +49,7 @@ Merge requests (MRs) are meant for code which you would like to get merged. Ther
By making a merge request you are letting others know that your change has been tested and you feel it is ready to be live. Since MRs should be reviewed by another person and in order to minimize misspent effort, we have come up with a short set of guidelines around merge requests.
* In the merge request, add a sign off line signifying that you agree that your work is used under the license of the project being contributed to: ``Signed-off-by: Random J Developer <random@developer.example.org>``
* In each commit add a signed-off-by line signifying that you agree to the :ref:`Developer Certificate of Origin <dco>`: ``Signed-off-by: Random J Developer <random@developer.example.org>``. This is meant to make sure that you agree that your change is distributed under the license (or licenses) of the project you're contributing to.
* Anyone that is making a MR should have tested their change.
* Alert someone to review the MR, ideally by using a ``@mention``.
* If there is no single person that knows the affected areas well, alert multiple people.
......
......@@ -25,3 +25,5 @@ Welcome to the Librem 5 documentation! This site contains instruction and exampl
Contributing
Resources
Contact
Appendix
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment