On Wed, Mar 22, 2017 at 2:37 PM, Craig Russell <craig.russ...@oracle.com> wrote:
> My takeaway is that Slack not a substitute for email. But it is useful for > ping-pong communication when people are in the heat of development. > > But no decisions are made on Slack, and any discussion there (aside from > “add a semicolon there” and “let’s get lunch") needs to be brought back to > the dev list. > > The underlying principle is that “if it didn’t happen on dev, then it didn’t > happen”. We strive for open, inclusive communications at Apache and that > means attempting to encourage participation by everyone who wants to, > regardless of primary language, time zone, and availability of tools. (We > assume everyone has a device that handles email clients). +1 I would add one more criteria: availability. Real-time communication channels, should they be used for development (as opposed to user support), privilege core devs who follow the project every waking minute and exclude everyone on the periphery. Efficient asynchronous decision making over email is a skill, and mastering it is key to success as an Apache community. It takes practice, because the way you present ideas for asynchronous consumption is not the same as the way you'd do it in real-time. The question I always have when podlings ask about Slack, IRC, videochat, face-to-face convos in meatspace, or any real-time communication channel, is whether they appreciate why they need to master email. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
