On Fri, May 10, 2013 at 8:47 PM, Jan Lehnardt <[email protected]> wrote: > Maybe what is missing from this is that lazy consensus leads to things > that can never every be changed again. It is just a tool to keep a > distributed team going. If we do a thing and it gets lazy consesus’d > and implemented and even shipped, we can still *at any time* realise > it was a mistake, make a course correction or revert and move on. > It is unfortunately not true for everything. That is why lazy consensus is adapted to code but quite more complex to use in other cases.
- benoit
