Skip to content

Latest commit

 

History

History
52 lines (35 loc) · 2.82 KB

contributing.md

File metadata and controls

52 lines (35 loc) · 2.82 KB

Contributing

We're thrilled that you want to contribute to the Reaction Catalyst Library!

Before submitting your first contribution, please consult the official guide on contributing to the Reaction code base first. The sections below are currently specific to the Reaction Catalyst Library and should be considered in addition to the official guide.

Signing your Commits

Contributing to the Reaction Catalyst Library requires signing your work by way of signed Git commits.

The Reaction Catalyst Library uses the Apache 2.0 license to allow our community and customers to use it in whichever way they please. It also helps foster open contributions.

As a contributor, we want to make sure that you understand your rights as the copyright holder. We also want to make sure that contributions done on behalf of companies (i.e. by their employees) are submitted with the acknowledgement that the contributor (employee) isn't the copyright holder (employer).

The Reaction Catalyst Library is using a Developer Certificate of Origin (DCO), by way of signed commits, to help contributors acknowledge that they're aware of their rights, and that they have the authority to submit their contributions either on their or on their employer's behalf.

To sign off on the DCO for your commits, use the command git commit -s which adds a line to every commit that looks like this:

Signed-Off-By: Jane Doe <[email protected]>

We do ask that you use your full name and a valid email address in this process.

The DCO signoff is attached to every single commit, thereby stating that the committer agrees to the DCO as shown below or on https://developercertificate.org/.

Developer's Certificate of Origin 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.