Skip to content

Latest commit

 

History

History
40 lines (25 loc) · 1.86 KB

File metadata and controls

40 lines (25 loc) · 1.86 KB

Contributing To OCI-SPEC-ZIG

We'd love your contribution on the project!

Developer Certificate of Origin

oci-spec-zig enforces the Developer Certificate of Origin (DCO) on Pull Requests (PRs). This means that all commit messages must contain a signature line to indicate that the developer accepts the DCO.

Here is the full [text of the DCO][0], reformatted for readability:

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.

Contributors indicate that they adhere to these requirements by adding a Signed-off-by line to their commit messages. For example:

This is my commit message

Signed-off-by: Random J Developer <random@developer.example.org>

The name and email address in this line must match those of the committing author's GitHub account.

[0]: https://developercertificate.org/