Add RFC index

Add an index for in discussion / proposed / accepted RFCs for tracking. The SIG can review this list regularly at group meetings.

Signed-off-by: Stephen Tramer <[email protected]>

rfcs/README.md

@@ -1 +1,25 @@
-# O3DE RFCs - This is where RFCs that have been accepted are kept
+# sig-docs-community RFCs
+
+This is the tracking list for proposed, open, and accepted RFCs for sig-docs-community.
+
+## Proposed / In discussion
+
+| Discussion | Summary |
+|------------|---------|
+| https://github.com/o3de/sig-docs-community/discussions/46 | Website versioning for different releases of O3DE, including better visibility and maintenance policies around the `development` branch. |
+
+## Open
+
+| RFC | Summary |
+|-----|---------|
+| 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. |
+| https://github.com/o3de/sig-docs-community/issues/40 | Feature grid requested by the Linux Foundation, supplemental docs edition. |
+
+## 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/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. |