Got it. Makes sense. On Fri, Jan 25, 2019 at 9:31 PM Luciano Resende <[email protected]> wrote:
> On Fri, Jan 25, 2019 at 6:02 PM Thomas Weise <[email protected]> wrote: > > > > My personal opinion is that Slack can be useful for a quick ping or > > pointer, but on the other hand threads can quickly become unwieldy. > > Larger/deeper discussions flow better as email and mailing list archives > > make for better discoverability. Slack can also be quite a distraction. > > While it looks attractive to those asking the "quick question", what does > > that mean for those that are supposed to respond? Latency expectation > tends > > to be more aggressive with Slack, compared to email. > > > > Having said that, I think that Slack can be a good complementary > > communication channel, when used with measure. When you look at Beam, > there > > is good activity on dev@ and user@, my impression is that some user@ > > traffic gets diverted to Slack but that is not necessarily at bad thing > > (see subscriber count). Some folks use the Slack channel just to "ping" > > others, but sometimes you find large blobs of text that would better live > > in mailing list archive, for future searches. > > > > In any case it is important that project decisions and deeper discussions > > remain on the dev@ list. > > > > Thomas > > > > > +1 to what Thomas has said... > > In Apache we usually say, "If it didn't happen on the mailing list, it > didn't happen". Having this in mind, I would recommend that any > important discussions that start on slack should be moved to the > appropriate project list, and/or a summary should be sent so others > have the opportunity to join the discussion. > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
