# sig-docs-community RFCs

This is the tracking list for proposed, open, and accepted RFCs for sig-docs-community.

## Proposed / In discussion

| Discussion | Summary |
|------------|---------|

## Open

| RFC | Summary |
|-----|---------|
| https://github.com/o3de/sig-docs-community/issues/64 | Feature grid requested by the Linux Foundation, supplemental docs edition. |
| https://github.com/o3de/sig-docs-community/issues/61 | Access control and ownership of o3de/o3de.org. |
| https://github.com/o3de/sig-docs-community/issues/43 | Assignment of O3DE issues to `sig/docs-community`; Without a global triage there needs to be a formal process for SIGs to follow. **NOTE:** Gavin may have taken over the global sync, which means this RFC may no longer be needed. |

## Accepted 

This section is a running list of RFCs that have been accepted by the SIG.

| RFC | Summary |
|-----|---------|
| https://github.com/o3de/sig-docs-community/issues/54 | Website versioning for different releases of O3DE, including better visibility and maintenance policies around the `development` branch. |
| https://github.com/o3de/sig-docs-community/issues/32 | Separate `main` and `development` branches of o3de.org to reflect different product states and to prepare for website versioning. |
| https://github.com/o3de/sig-docs-community/issues/8 | Accepting SIG charter. |
| https://github.com/o3de/sig-docs-community/issues/64 | Documentation health in each important feature area needs to be reported in some way for the O3DE feature grid. This RFC covers the column extensions and terminology used by sig-docs-community for reporting on the state of documentation in a way that aligns with how SIGs report on the state of their features to the TSC, TAC, and Governing Board. |
| https://github.com/o3de/sig-docs-community/issues/61 | This RFC is to establish a system where we can separate out different maintainers and owners of the o3de.org website. |
