Doing some exploratory thinking about the possibilities opened by Google Wave, I came up with this very early idea of something that could turn out to be pretty interesting. In explaining it, I’ll assume you’ve watched that huge 1h20min video they have about it (it’s worth every minute, but there’s an abridged — 10min — version).

Motivation

People have been doing code review through email for ages. It’s the easiest, dead-simple way of doing it. Just add a post-receive-hook to your repository and make it email a diff of every new commit to a mailing list. People answer to that email, inlining comments where needed. Great, you say. But… It’s not 2.0. Bummer.

Continued from part 4: collaboration.
Version control is again not the most accessible topic yet it’s inclusion in Google Wave is significant. The version control community has seen quite a lot of upheaval in recent years. We’ve entered the new millennium with one dominant open-source version control tool: CVS.
Then Subversion emerged as a new open-source version control system that tried to address the design issues in CVS. Subversion is an easier to use version control system because it removed many arcane and idiosyncratic CVS headaches.