community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 林晉樟 <line0928769...@gmail.com>
Subject Re: slack
Date Mon, 10 Aug 2015 17:38:04 GMT
2015/8/11 上午1:36於 "林晉樟" <line0928769960@gmail.com>寫道:
>
>
> 2015/8/11 上午1:36於 "林晉樟" <line0928769960@gmail.com>寫道:
> >
> >
> > 2015/8/11 上午1:35於 "Benson Margulies" <bimargulies@gmail.com>寫道:
> > >
> > > I think it's important to recognize how the board and the foundation
> > > have handled this issue over time.
> > >
> > > The absolute requirement is open decision-making. Avoiding real-time
> > > communications avoids many possible failures of open decision-making.
> > > (Not, of course, all.) After all, the simplest primrose path here is
> > > two people standing at the intersection of their cubicles. The policy
> > > has always been to sternly warn that the use of real time mechanisms
> > > involves risks of failure, and that failure involves risks of the
> > > board's blunt instruments being deployed. Does all of this slow down
> > > some processes, and cause some people of limited patience / boundless
> > > energy to get frustrated? Yup, things have costs.
> > >
> > > Just writing up the results on the mailing list isn't good enough if
> > > there is no real opportunity for people to question, deliberate, and
> > > change the course of action.
> > >
> > > You want to have a bar camp, a con call, a slack discussion, a set of
> > > messages exchanged by carrier pigeon? Then it's up to you to make sure
> > > that you don't end up excluding people from the decision-making
> > > process.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message