Re: Consensus, Majority vote, blocks | <– Date –> <– Thread –> |
From: Moz (list![]() |
|
Date: Sun, 25 Sep 2011 19:42:16 -0700 (PDT) |
> It's really important not to let the team crafting a proposal do so in > a vacuum! We used to have people work months on a proposal then be > devastated when the group, or a number in the group, didn't like it. > Led to burn out. We learned to get community input early and often. We've struggled a bit with "I don't like it but I might be able to live with it, why don't you go ahead and develop it" responses that are not delivered with any committment to helping develop the proposal. Those are the ones that have burnt me. I do feel that if someone doesn't care enough about a proposal to be part of fixing/developing it then they really shouldn't block it later. I think they have an obligation to block it early and firmly. But of course, if they're not committed to seeing it stopped, it's easier to step back and let the keen people work on it, then decide late in the piece that it really won't work for them. It's hard, often "meh" doesn't turn into "no" until there's a concrete proposal to respond to. At that point sometimes it becomes obvious to all that nothing like this will ever get consensus. Which is hard, but such is life. Moz
-
Re: Consensus, Majority vote, blocks Lynn Nadeau / Maraiah, September 25 2011
- Re: Consensus, Majority vote, blocks Moz, September 25 2011
- Re: Consensus, Majority vote, blocks R Philip Dowds, September 26 2011
-
Re: Consensus, Majority vote, blocks Lynn Nadeau / Maraiah, September 26 2011
-
Re: Consensus, Majority vote, blocks Sharon Villines, September 26 2011
- Re: Consensus, Majority vote, blocks R Philip Dowds, September 26 2011
-
Re: Consensus, Majority vote, blocks Sharon Villines, September 26 2011
Results generated by Tiger Technologies Web hosting using MHonArc.