Skip to content

Latest commit

 

History

History
21 lines (12 loc) · 1.23 KB

File metadata and controls

21 lines (12 loc) · 1.23 KB

Contributing to OneHill

Thanks for helping keep intelligence in everyone's hands. This file is the default guide for every OneHill repository that does not ship its own.

Before you start

  • Read the Code of Conduct. It applies everywhere in this organisation.
  • For anything security-related, do not open a public issue. Follow SECURITY.md.
  • A repository may override this file with its own CONTRIBUTING.md. When it does, that one wins.

Licensing and provenance

Contributions follow inbound equals outbound: your contribution is licensed under the same licence as the repository you contribute to. Each repository states its licence in its LICENSE file. There is nothing extra to sign.

We ask you to certify provenance with a Signed-off-by line in your commits, following the Developer Certificate of Origin. That line confirms you wrote the contribution, or otherwise have the right to submit it under the repository's licence.

Some repositories add their own contribution terms on top of this. Where a repository ships its own CONTRIBUTING or LICENSE, that governs.

Questions

Open a discussion or issue on the relevant repository, or email dev@onehill.org.