Which copy of the SPEC should changes be proposed against?

[dstansby]

I want to contribute a minor clarification to the spec, but it's not clear what the process is to do that. In particular, which file in this GitHub repo should I propose a change against?

I suggest that a new "Contributing" (or similar) section is added at the top level to https://ngff.openmicroscopy.org/, which explains how to 1) propose minor changes/clarifications 2) how to propose major additions or changes (ie. explain or link to the RFC process).

[joshmoore]

Before @normanrz's 0.5 changes, your changes would have gone into /latest/. #271 captured "well, now we need a new mechanism". If you have suggestions on doing that, feel free. Otherwise, you can keep capturing proposals against /0.5/ as you did in gh-277 etc. while this issue (#276+#271) gets worked out.

[dstansby]

i've put a proposal at #281 - do you have context on why latest was removed (cc @normanrz)? It seems quite logical to me to always have a latest folder that changes are made against, and that is just copied and 'frozen' in a folder named after each version when a release is made.

[normanrz]

We were thinking of migrating to a branch-based scheme of managing versions. Instead of 0.4, 0.5, latest folders, there would be 0.4, 0.5, latest branches. But we didn't have the time to fully build it out because we were focussed on getting 0.5 done. Putting a symlink in for latest -> 0.5 solved the need to keep existing links functioning.

[joshmoore]

See #282 for a first POC