| Table of Contents |
|---|
...
As a potential contributor of code to the project, you are highly encouraged to read the Technical Charter and in particular note section 12 - Intellectual Property Policy. Contributors are advised to understand that submitting code to the project indicates you agree with the the Developer Certificate of Origin. See the Committing Code Code Guidelines for details on how to sign your code contributions to indicate your agreement with the DCO. See http://elinux.org/Developer_Certificate_Of_Origin for a description of how the Linux kernel implements its DCO.
...
- Apache License 2.0 statement
- Copyright of the contributing entity (person or corporation)
Note: when subsequent contributors make substantive changes to a file they may also optionally add a copyright line to the header for themselves (person or corporation), but should preserve existing copyright statements and license.
Existing source from the project can be used to exemplify this header.
...
If you would like, you could also bring up the issue on Slack the main GitHub discussion boards for initial feedback before submitting the issue in GitHub Issues .
...