The Collective Code Construction Contract (C4) is a governance model for FOSS (Free and Open source Software) projects that aims to create a solution-focused, iterative, inclusive and positive way of progress.

xchangeee

@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.

Jan Wildeboer 😷:krulorange:

@xchange I wanted to convert the blog to support multiple authors anyway. I'll play around with it a bit to see if I can post Chapter 4 as a guest post by Pieter @kdedude @schlauch

xchangeee

@jwildeboer @kdedude @schlauch

might be relevant, too?

http://hintjens.com/blog:93 (C4.1 - an Exothermic Process)

http://hintjens.com/blog:26 (The End of Stable Releases?)

http://hintjens.com/blog:85 (The End of Software Versions)

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.

Jan Wildeboer 😷:krulorange:

@xchange His big dream of an open world running on stable and reliable APIs that make releases and versions an archaic artefact of a chaotic past have not come to fruition, unfortunately. @kdedude @schlauch

Jan Wildeboer 😷:krulorange:

@xchange But when you follow the #C4process, a release is just a tag in your repo and the platform will build the release files automagically. Good enough for me @kdedude @schlauch

Jan Wildeboer 😷:krulorange:

@xchange Chapter 4 reformatted as markdown and posted as second blog entry at https://c4process.wildeboer.net/blog/2024-12-21-C4-Annotated/ @kdedude @schlauch