"org.mdedetrich" %% "scala-json-ast" % "1.0.0-M4"
@jvican BTW, this is especially important since you're moving most of the discussion over to Discourse. It's a reasonable place for discussion, but a terrible one for announcements. In social media terms, there are two broad categories of media, "push" and "pull". Push technologies are ones that are in your face, where information comes to you; pull ones are media that you need to go seek out. Email is the purest form of push; realtime systems like Gitter and Slack are push-y but also lossy -- people are likely to see stuff, but only if they are around at the time. Forum systems like Discourse are mainly pull technologies (you can make them push-y in the Preferences, but it takes a lot of work for each member to set up), and they're great for in-depth discussions among dedicated people, but lousy for getting the word out more widely. Announcements need to go to where people already are, using push mechanisms instead; otherwise, the larger community will simply never notice them.
So my recommendation is that you should put the in-depth announcements on Discourse, but then link to those announcements from several of the major Gitter channels. In other words, you push the notification somewhat aggressively to everybody, and then the ones who care can pull the details.
(Sorry for wandering into social-media-tech speak, but this has been one of my professional specialties for 30 years.)
I agree with everything you've said, we won't miss the opportunity to spread the word about our Discourse discussion threads in Gitter and Twitter. The least thing I would like to do is to keep people out of the loop. Thanks for the advice, it's very useful.