Contributions are welcome!
Contributions can be bug reports, feature requests, testing and documentation in addition to code. Please see the github guide on Collaborating on projects using issues and pull requests for details.
Contributions to this project are accepted on an "inbound=outbound" basis. That means that you agree that your contributions are made under the same license as the license for this project, the Apache License 2.0 LICENSE
To make this understanding explicit -- and for you to assert that you have the right to make the contribution -- commits must be signed off indicating acceptance of the Developer Certificate of Origin 1.1 DCO
This is an overview of the contribution workflow:
- Fork the repository on Github
- Create a topic branch from where you want to base your work (usually the master branch)
- Check the formatting rules from existing code (no trailing whitespace, mostly default indentation)
- Ensure any new code is well-tested, and if possible, any issue fixed is covered by one or more new tests
- Make commits to your branch using the following guidelines:
- Start with a subject line (beginning with a capital, ending without a period, no more than 50 characters)
- Use the imperative mood in the subject line: "Add x", "Fix y", "Support z", "Remove x"
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
- Finish the commit message with the sign off:
Signed-off-by: Your Name <firstname.lastname@example.org>
- Push your code to your fork of the repository
- Make a Pull Request
Verified commits with GPG
Verifying commits is not essential for contributions to this project, but for those motivated to add additional security it is important to know that Github now supports GPG signature verification.
Using GPG is a complex subject. Here are some pointers for further information:
- OpenPGP Best Practices
- Debian Keysigning HOWTO
- If you create a new key please ensure that the RSA key length is at least 4096 bits and configured for SHA-2
- If you use caff (from signing-party) to sign and distrubute signatures please verify that the separate caff configuration is accurate.
You can export your GPG public key to a file for use with Github as follows (assuming your GPG key id is 0xCAFED00D):
gpg --output 0xCAFED00D.asc --armor --export-options export-clean,export-minimal --export 0xCAFED00D
Simply paste the contents of that file in the SSH and GPG keys section of your Github settings.