# Contributing to jackin'

Thanks for your interest in contributing. A few ground rules.

## License

jackin' is licensed under the Apache License, Version 2.0. By submitting
a contribution, you agree that it will be licensed under the same terms
in accordance with Section 5 of the Apache License 2.0.

## Developer Certificate of Origin (DCO)

All contributions must be signed off under the Developer Certificate
of Origin v1.1 (https://developercertificate.org/). Sign off every
commit with:

    git commit -s

This adds a `Signed-off-by: Your Name <email>` trailer asserting that
you have the right to submit the contribution under the project's
license.

The full DCO text:

> Developer Certificate of Origin
> Version 1.1
>
> By making a contribution to this project, I certify that:
>
> (a) The contribution was created in whole or in part by me and I
>     have the right to submit it under the open source license
>     indicated in the file; or
>
> (b) The contribution is based upon previous work that, to the best
>     of my knowledge, is covered under an appropriate open source
>     license and I have the right under that license to submit that
>     work with modifications, whether created in whole or in part
>     by me, under the same open source license (unless I am
>     permitted to submit under a different license), as indicated
>     in the file; or
>
> (c) The contribution was provided directly to me by some other
>     person who certified (a), (b) or (c) and I have not modified
>     it.
>
> (d) I understand and agree that this project and the contribution
>     are public and that a record of the contribution (including all
>     personal information I submit with it, including my sign-off) is
>     maintained indefinitely and may be redistributed consistent with
>     this project or the open source license(s) involved.

## Contributions made on behalf of an employer

If your contribution is made in the course of your employment, or if
your employer has rights to inventions you make, you are responsible
for ensuring that you have authorization to contribute the work under
the Apache License 2.0 and to sign the DCO. If in doubt, please do not
submit the contribution until you have confirmed this with your
employer in writing.

Please use a personal email address (not an employer email) in your
commit author identity and DCO sign-off.

## How to submit

1. Fork the repository.
2. Create a feature branch.
3. Make your changes. Commit with `git commit -s` on every commit.
4. Open a pull request describing what problem it solves.
5. Ensure CI passes.

## Non-trivial contributions

For contributions beyond small bug fixes or typos, maintainers may ask
you to confirm in the PR thread that the work was done outside the
scope of any employer's employment agreement and that you are
authorized to submit it. This is standard due diligence, not an
accusation.
