Sync'd up another project. This time: *

Took a couple hours merging 11 of 26 open PRs on upstream.

Code: github.com/weex/diaspora

Next step is to deploy this to a production pod.

@fla Hi Fla, C4 is the Collective Code Construction Contract. It IS a bit radical but the idea is to prioritize the people and community who are developing a project by making it much easier to get contributions merged and therefore make more constant and satisfying progress. This fork is experimental but my hope is that it demonstrates a viable path forward for really any project.

C4 came out of the work of Pieter Hintjens and the 0MQ project. Links to follow...

@weex so what are you doing right now regarding diaspora?

@fla I've created a fork that will be maintained by the process spelled out in the protocol.

@weex I need to read more to understand how that C4 thing is working, but merging stuff without human review seems a bit dangerous to me.

Follow

@fla I agree it's a bit counterintuitive / counterculture even for software and it could be a bit bumpy at the start but I'm hopeful for its evolutionary approach.

· · Web · 1 · 0 · 0

@weex diaspora* maintainers always have been very conservative with code merging. But maybe that experiment can change their mind. Just, please, be very explicit on your pod about the fact that you are not running the vanilla diaspora* code, but some untested one.

@fla Understand completely. Created this and will probably update the readme github.com/weex/diaspora/issue but will also create one saying the same about the UI.

Sign in to participate in the conversation
Ecko / c4.social

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.