Skip to content

Commit

Permalink
Merge pull request #266 from joshmoore/rfc1_adopt
Browse files Browse the repository at this point in the history
Adopt RFC-1 🎉
  • Loading branch information
joshmoore authored Oct 24, 2024
2 parents afc5605 + 335df5b commit a09fc70
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 5 deletions.
13 changes: 10 additions & 3 deletions rfc/1/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ versions/index

## Status

This RFC is currently being responded to (R4).
This RFC has been adopted (S4).

```{list-table} Record
:widths: 8, 20, 20, 20, 15, 10
Expand Down Expand Up @@ -118,6 +118,12 @@ This RFC is currently being responded to (R4).
- EMBL-EBI
- 2024-10-08
- Accept (email)
* - Reviewer
- John Bogovic, Michael Innerberger, Virginia Scarlett
- bogovicj, minnerbe, virginiascarlett
- Janelia
- 2024-10-11
- [Accept](./reviews/2b/index)
```

## Overview
Expand Down Expand Up @@ -439,7 +445,7 @@ Where possible, **Reviewers** SHOULD be chosen to represent a cross-section of
the community. Which cross-sections are chosen MAY depend on a given RFC but
might include geographic distributions, the variety of imaging modalities,
and/or programming languages of the expected implementations. An attempt MUST
also be made to select both positive and negative voices from the community.
also be made to select both supporting and dissenting voices from the community.
*Editors* and *Reviewers* should proactively disclose any potential conflicts
of interest to ensure a transparent review process.

Expand Down Expand Up @@ -603,7 +609,8 @@ This RFC does not try to define all aspects of the NGFF community process and
instead focuses on the most immediate block which covers what is typically
thought of as the voting process. By establishing this as a foundation, future
RFCs can extend the community process either adding or simplifying structure as
feedback determines. In fact, sections like [“Policies”](#policies) are explicitly intended to be updated to reference future RFCs as they are defined.
feedback determines. In fact, sections like [“Policies”](#policies) are explicitly
intended to be updated to reference future RFCs as they are defined.
The following items are therefore considered out of scope for the purposes of
this RFC but future work is intended to evolve the community process.

Expand Down
2 changes: 1 addition & 1 deletion rfc/1/reviews/2b/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Most of the present reviewers feel that the proposed review process remains over
Nevertheless, even though the reviewers feel that the proposal still requires major changes, they change their recommendation to 'accept', acknowledging the importance of forward progress.
As the OME-Zarr community moves forward using this proposed process, the reviewers hope that their concerns will be kept in mind and revisited if / when these concerns become practical issues.

Below are some minor changes the author may consider. If the author chooses not implement them, the reviewers will not contest that decision.
Below are some minor changes the author may consider. If the author chooses not to implement them, the reviewers will not contest that decision.

## Suggested Minor Changes

Expand Down
2 changes: 1 addition & 1 deletion rfc/listing.csv
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
RFC,Description,Date,Status
[0](0/index.md),Original consensus model for decision making,2021,N/A
[1](1/index.md),RFC Process,2024,Under review
[1](1/index.md),RFC Process,2024,Adopted
[2](2/index.md),Zarr V3 Support,2024,Accepted
3,Remove axis restrictions,2024, Clarifications
[4](4/index.md),Axis Anatomical Orientation,2024,Under review
Expand Down

0 comments on commit a09fc70

Please sign in to comment.