"Distributed Git"

How to redefine `git push` for an era of distributed code. No canonical source; no platform lock-in. A re-implementation of `git push` that sends your code anywhere and everywhere. Nice features like branch protection are still possible, but able to defined locally, remotely, or both. Single locations can be defined as "canonical" upstream sources. Or code can have no canonical source, and just spread out and be used and interacted with wherever people like.

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town