O3DE is a very large project. Special Interest Groups (SIGs) are the way we divide up the planning and communication for the different areas and responsibilities around developing and maintaining O3DE.
Currently, O3DE has the following active SIGs:
| SIG-Build | SIG-Content | SIG-Core |
| SIG-Docs-Community | SIG-Network | SIG-Operations |
| SIG-Platform | SIG-Graphics-Audio | SIG-Release |
| SIG-Security | SIG-Simulation | SIG-Testing |
| SIG-UI-UX |
To identify what a SIG owns or is working on, you can:
- Use the Contributing guide for a quick overview of areas a SIG owns.
- Use the Feature Grid to see areas of ownership and where a SIG may need help.
- Use the GitHub Code Owners file, which shows the reviewer or maintainer groups that owns a particular area of O3DE.
- Or use the links above to look at the SIGs own documentation.
- All SIGs have a charter document that covers what they own directly, what they own in conjunction with other SIGs etc. All SIGs maintain a charter document in their repository, typically under the
governancefolder or use the quick links in the Contributing guide.
- All SIGs have a charter document that covers what they own directly, what they own in conjunction with other SIGs etc. All SIGs maintain a charter document in their repository, typically under the
SIGs are open to all. You can join the discussion on Discord or attend any of the public meetings. Use the O3DE Calendar to find upcoming SIG meetings.
Many SIGs have further information in the README files at the root of their repository.
Everyone can be a contributor or developer of O3DE. They can write code and documentation that change the project. However, SIGs rely on reviewers and maintainers to ensure contributions to the project have value and align with the needs of the project. Its expected that there will be more contributors than reviewers, and more reviewers than maintainers
Reviewers are expected to have expertize in some parts of the project owned by a SIG, and to guide contributions to that SIG. They have the power to review code on behalf of a SIG. Its expected that reviewers also help contributors find any related work, understand O3DE's development practices and any SIG specific requirements for contributions.
Maintainers have all the power of a reviewer but are also responsible for merging changes in O3DE including ensuring automated reviews are run on a code contributions. Maintainers have final responsibility for changes that are merged. Maintainers can, under special circumstances, bypass Automated Review checks for code submissions.
To become a reviewer or a maintainer for a SIG, see the process in community-membership.md. You may also want to reach out to the Chair(s) of the relevant SIG to understand their processes and expectations around reviewers and maintainers.
- General GitHub issue triage guide for SIG maintainers.
- How to become a reviewer or maintainer for a SIG.
- SIG governance details including roles of Chair(s)
- SIG chair elections process.