|
| 1 | +# Guidelines for submitting bugs: |
| 2 | +All non security bugs should be filed on the Issues tracker: |
| 3 | +https://github.com/tpm2-software/tpm2-tss-engine/issues |
| 4 | + |
| 5 | +Security sensitive bugs should be emailed to a maintainers directly. |
| 6 | + |
| 7 | +# Guideline for submitting changes: |
| 8 | +All changes to the source code must follow the coding standard used in the |
| 9 | +tpm2-tss project [here](https://github.com/tpm2-software/tpm2-tss/blob/master/doc/coding_standard_c.md). |
| 10 | + |
| 11 | +All changes should be introduced via github pull requests. This allows anyone to |
| 12 | +comment and provide feedback in lieu of having a mailing list. For pull requests |
| 13 | +opened by non-maintainers, any maintainer may review and merge that pull |
| 14 | +request. For maintainers, they either must have their pull request reviewed by |
| 15 | +another maintainer if possible, or leave the PR open for at least 24 hours, we |
| 16 | +consider this the window for comments. |
| 17 | + |
| 18 | +## Patch requirements |
| 19 | +* All tests must pass on Travis CI for the merge to occur. |
| 20 | +* All changes must not introduce superfluous changes or whitespace errors. |
| 21 | +* All commits should adhere to the git commit message guidelines described |
| 22 | +here: https://chris.beams.io/posts/git-commit/ with the following exceptions. |
| 23 | + * We allow commit subject lines up to 80 characters. |
| 24 | +* All contributions must adhere to the Developers Certificate of Origin. The |
| 25 | +full text of the DCO is here: https://developercertificate.org/. Contributors |
| 26 | +must add a 'Signed-off-by' line to their commits. This indicates the |
| 27 | +submitters acceptance of the DCO. |
| 28 | + |
| 29 | +## Guideline for merging changes |
| 30 | +Changes must be merged with the "rebase" option on github to avoid merge |
| 31 | +commits. This provides for a clear linear history. |
0 commit comments