Welcome to the Open 3D Engine! To learn more about contributing to the O3DE code repo, check out the Contributor's Guide.
The O3DE community repo contains information about how to get started, how the community organizes, and more.
To contribute, please review our Code of Conduct first.
Requirements to become a reviewer for a given Special Interest Group
- 6+ contributions successfully submitted to O3DE
- 100+ lines of code changed across all contributions submitted to O3DE
- 2+ O3DE Reviewers or Maintainers that support promotion from Contributor to Reviewer
You must be nominated (self-nomination is allowed) for promotion from Contributor to Reviewer. To do this, an issue should be created on the SIG's repo for the supportive Reviewers and Maintainers to comment and add their support. For example, to nominate a reviewer on behalf of sig-content, an Issue should be created in the sig-content repository.
Once you have the requisite support, the nomination Issue needs to be reviewed and approved during a SIG meeting. The nominee should plan to attend and add it to the agenda for the SIG to review and, if appropriate, approve. Nomination Issues that do not have the necessary support will be closed after 4 weeks of inactivity.
Requirements to continue to be a Reviewer
- 4+ Pull Requests reviewed per month
If a Reviewer fails to meet the requirements, they will be given a 1 month grace period to get back to the required number of Pull Requests per month. After the 2nd month, if they haven't returned to the required number of reviews, they will be returned to Contributor status.
Requirements to become a maintainer for a given Special Interest Group
- Has been a Reviewer for 2+ months
- 8+ reviewed Pull Requests in the previous 2 months
- 200+ lines of code changed across all reviewed Pull Requests
- 2+ O3DE Maintainers that support the promotion from Reviewer to Maintainer
You must be nominated (self-nomination is allowed) for promotion from Reviewer to Maintainer. To do this, an issue should be created on the community repo for the supportive Maintainers to comment and add their support. For example, to nominate a maintainer on behalf of sig-content, an Issue should be created in the sig-content repository.
Once you have the requisite support, the nomination Issue needs to be reviewed and approved during a SIG meeting. The nominee should plan to attend and add it to the agenda for the SIG to review and, if appropriate, approve. Nomination Issues that do not have the necessary support will be closed after 4 weeks of inactivity.
Requirements to continue to be a Maintainer
- 8+ Pull Requests reviewed per month
If a Maintainer fails to meet the requirements, they will be given a 1 month grace period to get back to the required number of Pull Requests per month. After the 2nd month, if they haven't returned to the required number of reviews, they will be returned to Reviewer status.