status |
---|
draft |
We don't want project on-boarding to be a burden.
The files in this folder are our recommendations for what CF projects should define.
-
If you use a DCO, your project should have a DCO.txt (case-insensitive) file containing content from http://developercertificate.org/
-
CONTRIBUTING.md to explain how to make successful contributions (be real).
-
If your project uses a DCO, include that in your contribution guide. For example:
All contributions are subject to the [Developer Certificate of Origin (DCO)](http://developercertificate.org/). The DCO text is also included verbatim in the [dco.txt](./dco.txt) file in the root directory of this repository.
-
If your project uses a CLA, include that requirement in the contribution guide. For example:
Contributor License Agreement Contributions to JReleaser are protected by a CLA. Please read the document before making a contribution. You’ll be asked to digitally sign the document on your first contribution. Feel free to open a discussion topic if you have questions.
-
Explanation of the difference between DCO and CLA: https://www.consortiuminfo.org/open-source/all-about-clas-and-dcos/
-
-
CODEOWNERS to define individuals or teams that are responsible for code in a repository