# Should we adopt C4? **URL:** \ **Category:** 🔮 Meta\ **Created:** [June 2, 2016, 12:06pm UTC](https://help.nextcloud.com/t/should-we-adopt-c4/113 "2016-06-02T12:06:37Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![jospoortvliet](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jospoortvliet/32/3_2.png) [@jospoortvliet](https://help.nextcloud.com/u/jospoortvliet)\ **Post date:** [June 2, 2016, 12:06pm UTC](https://help.nextcloud.com/t/should-we-adopt-c4/113/1 "2016-06-02T12:06:37Z")
[The Collective Code Construction Contract](http://rfc.zeromq.org/spec:22/) is an evolution of the [github.com](http://github.com) Fork + Pull Model, aimed at providing an optimal collaboration model for free software projects. It is absolutely interesting to read and we should see if we can use this, adopt it perhaps. From the link above: ## Goals C4 is meant to provide a reusable optimal collaboration model for open source software projects. It has these specific goals: - To maximize the scale and diversity of the community around a project, by reducing the friction for new Contributors and creating a scaled participation model with strong positive feedbacks; - To relieve dependencies on key individuals by separating different skill sets so that there is a larger pool of competence in any required domain; - To allow the project to develop faster and more accurately, by increasing the diversity of the decision making process; - To support the natural life cycle of project versions from experimental through to stable, by allowing safe experimentation, rapid failure, and isolation of stable code; - To reduce the internal complexity of project repositories, thus making it easier for Contributors to participate and reducing the scope for error; - To enforce collective ownership of the project, which increases economic incentive to Contributors and reduces the risk of hijack by hostile entities. --- _[View the full topic](https://help.nextcloud.com/t/should-we-adopt-c4/113)._