Very cool... I think I remember seeing this concept discussed on Slashdot a few years back.
Two of the biggest problems in software development are - the client gives incomplete or wrong requirements, or the programmer doesn't implement them correctly. How are you going to keep everyone happy when the programmer decides the software is deliverable, but the client(s) disagree?
Cheers for the feedback. Good questions ... spec disagreement is one of the things we're mulling over.
Currently it's the pledgers (the "clients") who have the vote on whether the releases are any good, or whether or not they're according to spec. But we've got in mind an agreements system for spec arguments like this. For later -- for now we're going to keep a close eye on things and see how they go.
Two of the biggest problems in software development are - the client gives incomplete or wrong requirements, or the programmer doesn't implement them correctly. How are you going to keep everyone happy when the programmer decides the software is deliverable, but the client(s) disagree?