Update CONTRIBUTING.md with information about DCO (#7397)
* Update CONTRIBUTING.md with information about DCO References: #7389 More information: https://about.gitlab.com/handbook/marketing/community-relations/code-contributor-program/#developer-certificate-of-origin-dco * Update CONTRIBUTING.md Co-Authored-By: zeripath <art27@cantab.net>release/v1.15
parent
c8aa46d27b
commit
f1ca8ed049
|
@ -11,7 +11,7 @@
|
||||||
- [Translation](#translation)
|
- [Translation](#translation)
|
||||||
- [Code review](#code-review)
|
- [Code review](#code-review)
|
||||||
- [Styleguide](#styleguide)
|
- [Styleguide](#styleguide)
|
||||||
- [Sign-off your work](#sign-off-your-work)
|
- [Developer Certificate of Origin (DCO)](#developer-certificate-of-origin-dco)
|
||||||
- [Release Cycle](#release-cycle)
|
- [Release Cycle](#release-cycle)
|
||||||
- [Maintainers](#maintainers)
|
- [Maintainers](#maintainers)
|
||||||
- [Owners](#owners)
|
- [Owners](#owners)
|
||||||
|
@ -77,7 +77,7 @@ Here's how to run the test suite:
|
||||||
creates (a default AWS or GCE disk size won't work -- see
|
creates (a default AWS or GCE disk size won't work -- see
|
||||||
[#6243](https://github.com/go-gitea/gitea/issues/6243)).
|
[#6243](https://github.com/go-gitea/gitea/issues/6243)).
|
||||||
- Change into the base directory of your copy of the gitea repository,
|
- Change into the base directory of your copy of the gitea repository,
|
||||||
and run `drone exec --local --build-event pull_request`.
|
and run `drone exec --event pull_request`.
|
||||||
|
|
||||||
The drone version, command line, and disk requirements do change over
|
The drone version, command line, and disk requirements do change over
|
||||||
time (see [#4053](https://github.com/go-gitea/gitea/issues/4053) and
|
time (see [#4053](https://github.com/go-gitea/gitea/issues/4053) and
|
||||||
|
@ -157,22 +157,21 @@ import (
|
||||||
)
|
)
|
||||||
```
|
```
|
||||||
|
|
||||||
## Sign-off your work
|
## Developer Certificate of Origin (DCO)
|
||||||
|
|
||||||
The sign-off is a simple line at the end of the explanation for the
|
We consider the act of contributing to the code by submitting a Pull
|
||||||
patch. Your signature certifies that you wrote the patch or otherwise
|
Request as the "Sign off" or agreement to the certifications and terms
|
||||||
have the right to pass it on as an open-source patch. The rules are
|
of the [DCO](DCO) and [MIT license](LICENSE). No further action is required.
|
||||||
pretty simple: If you can certify [DCO](DCO), then you just add a line
|
Additionally you could add a line at the end of your commit message.
|
||||||
to every git commit message:
|
|
||||||
|
|
||||||
```
|
```
|
||||||
Signed-off-by: Joe Smith <joe.smith@email.com>
|
Signed-off-by: Joe Smith <joe.smith@email.com>
|
||||||
```
|
```
|
||||||
|
|
||||||
Please use your real name; we really dislike pseudonyms or anonymous
|
If you set your `user.name` and `user.email` git configs, you can add the
|
||||||
contributions. We are in the open-source world without secrets. If you
|
line to the end of your commit automatically with `git commit -s`.
|
||||||
set your `user.name` and `user.email` git configs, you can sign-off your
|
|
||||||
commit automatically with `git commit -s`.
|
We assume in good faith that the information you provide is legally binding.
|
||||||
|
|
||||||
## Release Cycle
|
## Release Cycle
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue