Welcome to the Open 3D Engine Community contributing guide. We are excited about the prospect of you joining our community!
There are many opportunities to contribute to the O3DE project at any level. Every contribution is highly valued and no contribution is too small.
You do not need to write code to contribute to this project. Tests, documentation, demos, and feature design advancements are a key part of this project's growth. One of the best ways to begin contributing in a meaningful way is by helping find bugs and filing issues for them.
We have full documentation on how to get started contributing here:
- O3DE Contributor Guide - Main contributor documentation
This project has many different disciplines represented by special interest groups (SIGs). If you have a speciality, or just want to contribute to a certain area, please look through the SIGs and their respective charters here:
| SIG Repo | Charter | Mailing Group | Purpose |
|---|---|---|---|
| Build SIG | SIG-Build Charter | Build Group | Build systems, infrastructure, automation |
| Content SIG | SIG-Content Charter | Content Group | Editor framework, content workflows, animation, visual and scripting languages, asset processor |
| Core SIG | SIG-Core Charter | Core Group | Core frameworks, behavior context, serialization, code reflection, Physics API, packaging, AZCore and AZFramework |
| Docs-Community SIG | SIG-Docs-Community Charter | Docs-Community Group | Documentation standards, website management, community standards |
| Network SIG | SIG-Network Charter | Network Group | Communication Standards, Cloud networking, Multiplayer Client / Server / Peer networking |
| Platform SIG | SIG-Platform Charter | Platform Group | Platform Abstraction, Win/Mac/Android/Linux/other toolchain, language support, platform specific packaging, shared cross platform code and libs |
| Graphics-Audio SIG | SIG-Graphics-Audio Charter | Graphics-Audio Group | 2D/3D GPU Video Renderer, Audio renderer, AR/VR rendering, data specification mesh, materal, shader, and textures |
| Release SIG | SIG-Release Charter | Release Group | Define branch and release process / schedules, merge stabilization to release, freeze resolution |
| Security SIG | SIG-Security Charter | Security Group | Security review and campaign, tooling and communication, security bulletins, security compliance standards |
| Testing SIG | SIG-Testing Charter | Testing Group | Automated review and testing frameworks, prevalidation scripts, test case guidelines, define KPI and SLA for test metrics |
| UI-UX SIG | SIG-UI-UX Charter | UI-UX Group | User Interface / Experience design standards, Best practices, Compliance validation, cross-sig consistency |
Members of the community have multiple ways to collaborate on the project. We encourage you to join the community Discord server, Mailing list or SIG Discussion area.
Each SIG has scheduled meetings that may be found on the O3DE calendar.
The Open 3D Engine is a large, lively, friendly open-source community. As many open source projects often do, it depends on new people becoming members and regular code contributors. The Community Membership Document covers membership processes and roles. Please consider joining Open 3D Engine, and making your way up the contributor ladder!
Open 3D Engine participates in O3DECon and related Industry events. Information about these and other community events is available on the O3DE Event Calendar page.
All Open 3D Engine meetups follow the general Cloud Native Computing Foundation Guidelines You may also contact O3DE Staff driving the Community Groups program by email (meetups@o3de.org)
Before submitting code to the O3DE project, you will need to acknowledge the Developer Certificate of Origin DCO on Pull Requests. By making a submission, you license your submission under the Apache 2.0 and MIT licenses.
Please make sure to read and observe the Code of Conduct and Community Values
- Mentoring Initiatives - We have a diverse set of mentorship programs available that are always looking for volunteers!