Skip to content

Commit f70194e

Browse files
committed
docs: add contribution instructions, require DCO
Signed-off-by: Tommy van der Vorst <tommy@pixelspark.nl>
1 parent e5332d1 commit f70194e

File tree

2 files changed

+54
-0
lines changed

2 files changed

+54
-0
lines changed

.vscode/settings.json

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
{
2+
"git.alwaysSignOff": true
3+
}

CONTRIBUTING.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# Contributing Code
2+
3+
High-quality contributions are welcome. Fork the repository and make your changes in a new branch. Once it's ready
4+
for review, create a pull request.
5+
6+
## Authorship
7+
8+
### The Developer Certificate of Origin (DCO)
9+
10+
Like the Syncthing project, we require the Developer Certificate of Origin (DCO) sign-off on pull requests (PRs). This
11+
means that all commit messages must contain a signature line to indicate that the developer accepts the DCO.
12+
13+
The DCO is a lightweight way for contributors to certify that they wrote (or otherwise have the right to submit) the code
14+
and changes they are contributing to the project. Here is the full [text of the DCO](https://developercertificate.org):
15+
16+
---
17+
18+
By making a contribution to this project, I certify that:
19+
20+
1. The contribution was created in whole or in part by me and I have the right to submit it under the open source license
21+
indicated in the file; or
22+
23+
2. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open
24+
source license and I have the right under that license to submit that work with modifications, whether created in
25+
whole or in part by me, under the same open source license (unless I am permitted to submit under a different license),
26+
as indicated in the file; or
27+
28+
3. The contribution was provided directly to me by some other person who certified (1), (2) or (3) and I have not
29+
modified it.
30+
31+
4. I understand and agree that this project and the contribution are public and that a record of the contribution
32+
(including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be
33+
redistributed consistent with this project or the open source license(s) involved.
34+
35+
---
36+
37+
Contributors indicate that they adhere to these requirements by adding a `Signed-off-by` line to their commit messages.
38+
For example:
39+
40+
This is my commit message
41+
42+
Signed-off-by: Random T Developer <randomt@example.org>
43+
44+
The name and email address in this line must match those of the committing author.
45+
46+
## Licensing
47+
48+
All contributions are made available under the same license as the already existing material being contributed to. For
49+
most of the project and unless otherwise stated this means MPLv2, but there are exceptions (see [README](./README.md)).
50+
51+
Regardless of the license in effect, you retain the copyright to your contribution.

0 commit comments

Comments
 (0)