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. I think it is time to promote it again, as its IMHO unique approach deserves to be discussed and implemented in more projects. It will need some updates, as things have changed since the primary author passed away. I started by creating a website at https://c4process.wildeboer.net 1/4
And set up an organisation at #Codeberg with the site sources and a discussion repository at https://codeberg.org/C4process I invite all of you that know or want to learn about the C4 process to join me there. Good governance for FOSS is not magic, Pieter spent years of his life to extract the C4 process from experiences and failures. Let's all learn together! 2/4
(That's one of the things that has changed. We now have decentralised forges with #Forgejo and don't have to rely on Github or Gitlab alone) 3/4
IMHO we never had to rely on GitHub:
> The project SHALL be hosted on github.com or equivalent, herein called the “Platform”.
it was just practical to do so. what else do you think should be changed?
@jwildeboer I love the idea. I'll check it out in detail later.
Sorry to be that guy, but can you link the source code (git repo) to the page in e.g. the footer? GPL and all that…
@jwildeboer
The name C4 seems to be clashing with the other C4 systems architecture modelling language. Can we add or remove a word to end up with C3 or C5?
If this is Pieter Hintjens, we're in for a treat. I was always intrigued by the good writing around the #0mq community process and also the work on calling out psychopaths. https://hintjens.gitbooks.io/psychopathcode/content/