Contributing to seL4

We welcome contributions to all aspects of the seL4 ecosystem:

• Code and documentation contributions via pull requests on GitHub. You should be aware of the seL4 coding conventions and requirements and the developer certificate of origin. See more details below.
• Design and API contributions via the Request for Comments (RFC) process
• Asking questions and helping out others on our community channels

The seL4 code of conduct applies to all contributions.

Code, Proofs, and Documentation

Code, proof, and documentation contributions are via pull requests on repositories in the seL4 GitHub org. To increase the likelihood that your pull request receives interest and reviews, please follow the guidelines on the page for coding conventions and requirements. The developer certificate of origin requirement applies to all pull requests, including documentation and proof contributions.

In general, quality assurance requirements are highest for kernel contributions. They are more standard and faster-paced for user-level frameworks and libraries.

Note that larger changes, such as an architecture port, or adding a new feature to the kernel, requires a RFC first, in which you describe the change and get feedback from the community. Contributions to user-level frameworks and libraries are less formal, but we still recommend that you discuss any larger contributions with the community before starting work on them.

Anyone can help review pull requests, but only people that have been granted the Committer role by the Technical Steering Committee can merge them. Committers are the people responsible for maintaining the quality and correctness of the code.

For the specific case of contributing a platform port, please read the platform contributions guide. The seL4 docsite has additional guidance for kernel contributions, as well as guidance for contributing to the docsite itself.