Lazy Consensus

[tjfontaine]

Below is from an internal thread from the advisory board, included here to start the discussion.

Lazy Consensus

@shammond2000

• I suggest clarifying what the TC decides and how they make those decisions. For example, there are some critical issues such as roadmap, stable release readiness, adding members to TC, etc. that should have a full consensus and maybe some less critical items such as unstable releases that could get away with a lazy consensus.

@isaacs

I seem to remember a discussion about needing quorum to remove members from the TC, and consensus to add them, but I don't see that in the discussion history. (It could've been in mikeal/node-forward, but it's also possible it was in meatspace or my imagination. I'll try to dig this up.) It's a good point to clarify, thank you for highlighting it.

[mikeal]

I addressed most of this in my comment on the consensus model here #6 (comment)