RFC-10: propose NGFF editorial board - #559
Conversation
As agreed during the OME2026 community meeting. see: https://bit.ly/ome2026-gov-proposal
Automated Review URLs |
| does not participate in routine RFC deliberations unless escalation is | ||
| required. | ||
|
|
||
| The OMG shall: |
There was a problem hiding this comment.
Not sure where you wanted to specify this, but I still think the formal acts of the OMG should be a default-accept of recommendation of the EB within a specified time frame. See https://docs.google.com/document/d/1picvG4yq0K_gIiF83C5rAy3AguqJeWkdAxL-vds5BgI/edit?disco=AAAB3IaXQ3Q
There was a problem hiding this comment.
Ah, thank you. I see what happened. A copy (fork 🙈) went live for the OME2026 meeting and the two drifted. I'll re-sync post vacation.
There was a problem hiding this comment.
I think the main two missing sections were:
- ZSC: re-added
- OMG relationship: rewritten
Let me know what you think.
|
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/our-proposed-roadmap-to-ome-zarr-1-0/121995/10 |
Co-authored-by: Tiago Lubiana <tiago.lubiana@gerbi-gmb.de>
normanrz
left a comment
There was a problem hiding this comment.
Thanks for the edits!
I think a few failure modes need more thoughts:
- If EB members fail on their duties (e.g. prolonged inactivity), how can they be involuntarily removed? Is that a responsibility of the OMG?
- What options does the EB have in case of failure of the OMG to fulfill their duties (e.g. approvals, appointments)?
|
Pushed, @lubianat. Anything else? |
|
not on my end, LGTM |


As agreed during the OME2026 community meeting. For review by the OME Management Group.
see: https://bit.ly/ome2026-gov-proposal
cc: @vuhlmann