Most decentralized development process, ever.

At Shitfork, we merge all pull requests directly to Master. Any pull request that is a valid patch (see the contribution protocol) will be merged straight into Master, no questions asked. What a crazy world.

At the same time, if your patch is not valid under the contribution protocol, it will not be merged.

The contribution protocol is simple and easy to follow, but the reasoning behind it can be hard to understand until you see the results in action. It's a hill-climbing algorithm. The best way to understand it is to read the annotated version before the raw protocol itself.

The contribution protocol applies to everyone. A cardinal sin that many open source developers make is to place themselves above others. "I founded this project thus my intellect is superior to that of others". It's not just immodest and rude, and usually inaccurate, it's also poor business. The rules apply equally to everyone, without distinction.

Upfront consensus is not compatible with the contribution protocol, that means roadmaps are not possible. Shitfork is an experiment in evolution, not intelligent design.

Existing work was released under the terms of the MIT license, for details see LEGACY_LICENSE. All additional work is released under the MPL v2 (LICENSE) and remains copyright (c) whoever sent the pull request (AUTHORS). There's a good reason for doing things this way, but you'll have to understand the rationale behind the contribution protocol to understand why.