32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
# Contributing Guidelines
|
|
|
|
gp2040ce-binary-tools is made available under the MIT (Expat) license. Contributions are welcome via pull requests. This
|
|
document outlines the process to get your contribution accepted.
|
|
|
|
## Sign Offs/Custody of Contributions
|
|
|
|
The Developer Certificate of Origin (DCO) is a way for contributors to certify that they wrote or otherwise have the
|
|
right to license their code contributions to the project. The full text of the DCO can be found
|
|
[here](https://developercertificate.org/) or in `DCO.txt`. Contributors must sign-off that they adhere to these
|
|
requirements by adding a `Signed-off-by` line to their commit message, and/or, for frequent contributors, by signing off
|
|
on their entry in `MAINTAINERS.md`.
|
|
|
|
This process is followed by a number of open source projects, most notably the Linux kernel. Here's the gist of it:
|
|
|
|
```
|
|
[Your normal Git commit message here.]
|
|
|
|
Signed-off-by: Random J Developer <random@developer.example.org>
|
|
```
|
|
|
|
`git help commit` has more info on adding this:
|
|
|
|
```
|
|
-s, --signoff
|
|
Add Signed-off-by line by the committer at the end of the commit log
|
|
message. The meaning of a signoff depends on the project, but it typically
|
|
certifies that committer has the rights to submit this work under the same
|
|
license and agrees to a Developer Certificate of Origin (see
|
|
http://developercertificate.org/ for more information).
|
|
```
|