This is a request for comments on the Caffe development model and contribution protocol. These aren't draconian laws so much as guidelines so we can all happily brew Caffe. Establishing protocols is only a side effect of having such thriving development, so it's a lovely problem we have.

Development workflow proposal:

• master is golden.
• work is done in feature branches. These should be rebased to the tip of dev to avoid drift–and this is required for merge.
• dev is the branching point for features, and the target of pull requests for merge.
• contributions are shepherded from dev to master by the project maintainers after integration and testing via merge.
• the history of dev is not rewritten. accidents are fixed by reverts.
• "releases" are marked with tags

Contributions/Issues/PR proposal: see #101 (comment).

The closer your contribution follows these suggestions, the less friction for merging.