Improve the documentation of the RFC process

resources/rfc-status-codes/index.md

@@ -0,0 +1,38 @@
+RFC status codes
+============
+
+
+[RFC 1](../../rfc/1) defined a Request for Comments process for the NGFF community, which is used to drive changes. The text listed a set of codes used to define how a change progresses from an idea to actual adoption.
+
+
+![State diagram of the RFC process](../../rfc/1/diagram.png)
+
+This resource is a (non-normative) table describing the different codes used in that specification that outline the states of the RFCs. It is _not_ a full description of the RFC process. 
+The status codes indicating ends of an RFC process are outlined in **bold**.
+
+Wait times provide a sense on how fast the process is expected to move to the next phase. The actual time may vary in practice, given factors such as the time of the year and current capacity. 
+
+
+
+| Phase | Code   | Description                                                                                         | Wait time       | Action by         |
+| ----- | ------ | --------------------------------------------------------------------------------------------------- | --------------- | ----------------- |
+| draft | D1     | AUTHORS propose idea (e.g. on an issue or community call)                                           | NA              | AUTHOR            |
+| draft | D2     | AUTHORS gather support (e.g. other AUTHORS) and ENDORSEMENTS                                        | NA              | AUTHOR            |
+| draft | D3     | AUTHORS open/update DRAFT PR                                                                        | 4 weeks         | AUTHOR            |
+| draft | D4     | Questions raised during PR review?                                                                  | NA              | AUTHOR            |
+| draft | D5     | EDITORS approve?                                                                                    | NA              | EDITOR            |
+| draft | **D6** | If not, PR closed                                                                                   | NA              | EDITOR            |
+| RFC   | R1     | EDITORs assign RFC number, merge PR, and contact REVIEWERS                                          | 4 weeks         | REVIEWER + EDITOR |
+| RFC   | R2     | REVIEWERS submit REVIEWS with recommendations as new PRs.                                           | NA              | REVIEWER + EDITOR |
+| RFC   | R3     | EDITORS merge REVIEWS and send to AUTHOR for RESPONSE                                               | NA              | AUTHOR + EDITOR   |
+| RFC   | R4     | AUTHORS prepare RESPONSE and changes to RFC                                                         | NA              | AUTHOR            |
+| RFC   | R5     | EDITORS merge RESPONSE and changes to RFC, contacts  REVIEWERS                                      | 2 weeks         | REVIEWER + EDITOR |
+| RFC   | R6     | REVIEWERS approve?                                                                                  | NA              | REVIEWER          |
+| RFC   | R7     | If no, EDITORS approve?                                                                             | NA              | EDITOR            |
+| RFC   | R8     | If changes necessary, AUTHORS prepare changes to RFC and/or RESPONSE. If they are major, back to R1 | NA              | AUTHOR            |
+| RFC   | **R9** | If rejected, RFC is considered withdrawn. It will be readable on the website                        | NA              | EDITOR            |
+| SPEC  | S0     | If REVIEWERS overridden, EDITORS add RESPONSE                                                       | NA              | EDITOR            |
+| SPEC  | S1     | RFC accepted! AUTHORS or EDITORS update the SPEC                                                    | NA              | AUTHOR + EDITOR   |
+| SPEC  | S2     | Clarifications needed?                                                                              | If yes, 4 weeks | EDITOR            |
+| SPEC  | S3     | Update implementations                                                                              | NA              | EDITOR            |
+| SPEC  | **S4** | SPEC adopted                                                                                        | NA              | EDITOR            |

rfc/7/index.md

@@ -0,0 +1,9 @@
+# RFC-7: Channel provenance
+
+```{toctree}
+:hidden:
+:maxdepth: 1
+comments/index
+```
+
+RFC-7 has been reserved a number and a topic (channel provenance), but is yet under preparation. 

rfc/8/index.md

@@ -0,0 +1,9 @@
+# RFC-8: Collections
+
+```{toctree}
+:hidden:
+:maxdepth: 1
+comments/index
+```
+
+RFC-8 has been assigned a number, but it is still in early preparation. A [draft pull request](https://github.com/ome/ngff/pull/343) has been opened by the authors. 

rfc/listing.csv

@@ -6,6 +6,6 @@ RFC,Description,Date,Status,OME-Zarr Version
 [4](4/index.md),Axis Anatomical Orientation,2024,Under review,
 [5](5/index.md),Coordinate systems and transformations,2024,Under review,
 [6](6/index.md),Flattening the multiscales array,2025,Superseded,
-7,Channel provenance,TBD,TBD,
-8,Collections,2026,[PR](https://github.com/ome/ngff/pull/343),
+[7](7/index.md),Channel provenance,TBD,TBD,
+[8](8/index.md),Collections,2026,[PR](https://github.com/ome/ngff/pull/343),
 [9](9/index.md),Zipped OME-Zarr,2025,Under review,