I actually agree with that a lot. On the flip side of that is the ability of these chat systems to quickly exchange ideas and throw some spaghetti against the wall to see if somethings sticks. A lot of the banter, user questions, non-dev discussions and so on would also feel out of place on a dev list I think.
Technically my main issue with Slack is that it's a closed system. To get on the Apache Slack channels you need to jump through hoops which I couldn't even find for the longest of times. Instead of lowering the barrier it increased it for me. Open source Mattermost runs on our own server, has no history limits and anyone can join for free without any limits. I think this low barrier is extremely important since you're not going to spend a lot of time if you just want to report something small. Matt On Wed, Oct 14, 2020 at 12:04 AM Julian Hyde <[email protected]> wrote: > Slack and other forms of chat are fine, especially for really quick > questions, but get into the habit of switching to the dev list for > decisions or longer discussions. > > There are differing opinions within the ASF about Slack. Some folks say > that it is as good as a dev list if it is archived and the archive is > searchable. But in my opinion, Slack conversations are so low latency that > they tend to exclude anyone who is not online when the discussion is > happening. If in doubt, move the conversation to the mailing list. > > Julian > > > > On Oct 9, 2020, at 1:55 AM, Maximilian Michels <[email protected]> wrote: > > > > Sounds good! Eventually we also want to migrate the existing Slack > channel over to the ASF Slack. > > > > ¬Max > > -- Neo4j Chief Solutions Architect *✉ *[email protected] ☎ +32486972937
