General GitHub Workflow:

• https://docs.releng.linuxfoundation.org/en/latest/best-practices.html#github-workflow

Guidelines for Contributors:

• Each code submission should include an issue identifier number to reference what is being addressed by this change.
• Each code submission that includes new code branches must include automated test cases to exercise the new code branches added.
• Commits should be signed and DCO approved. More information on how to setup your GPG keys: https://docs.releng.linuxfoundation.org/en/latest/gpg.html
• Commits should be rebased into the latest branch's HEAD.
• Additionally, we recommend the following Best Practices: https://docs.releng.linuxfoundation.org/en/latest/best-practices.html

Guidelines for Committers/PTL:

• When performing code reviews, committers should check the following items:
  • Make sure CI versification was successful.
  • Verify that the submission contains appropriate test cases.
  • Verify that the commit message is explicit and is appropriate for the code being changed/added/removed.
• After code is merged, the committer should make sure any post CI processing was successful.
• Pull Requests require approval from the committers team for the respective repo.
• New committers can be selected by performing a TSC vote.

Branch Guidelines:

• Main development happens in the "main" branch.

Intellectual Property Policy (From Dent Technical Charter)

a. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project.

b. Except as described in Section 7.c., all contributions to the Project are subject to the following:

i. All new inbound code contributions to the Project must be made using the following licenses (as applicable, the “Project License”):

1. For code that runs in the kernel, GNU General Public License, Version 2.0, available at https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html; and
2. For all other code, Eclipse Public License, Version 1.0, available at https://www.eclipse.org/org/documents/epl-v10.html.

ii. All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;

iii. All outbound code will be made available under the Project License.

iv. Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License, available at ttp://creativecommons.org/licenses/by/4.0/.

v. The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project’s main code repository will comply with the contribution process and license terms for the applicable Upstream Project.

c. The TSC may approve the use of an alternative license or licenses for inbound or outbound contributions on an exception basis. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC.

d. Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.