C4 doesnt contain much details wrt releases/versions. I remember that e.g. zeromq tried to avoid the producer/consumer relationship that often emerges with software projects, and thus didnt put too much weight into versioned releases. It was expected to work on latest main.
@jwildeboer@kdedude@schlauch Ive been re-reading chapter 4 of the book and I feel it would make sense to eventually merge this into the C4 website / repo.
The chapter is the design doc explaining the what and why, while the protocol defined in the RFC is the condensed implementation that explains the how.
IMHO this is not gatekeeping per-se but more like "just enough process", in the same way that you would expect contributors to open github issues and fill out an issue template over sending a free-form email to the maintainers personal mail address.
Sticking to problem/solution statements is as simple as it can get and helps to avoid the XY-Problem. I'm using this model successfully for many years now (adapted to a corporate setting) and it just works.
AFAIR C4 itself is governed by COSS (https://rfc.unprotocols.org/), and if you change C4, technically it will would become deprecated and eventually retired.
But COSS has never left the draft state :D Do you remember what the ideas behind unprotocols were and why there is a split between unprotocols and ZMQ RFCs?