Worth considering what the benefits vs problems are for Gitter vs Slack; i.e. what is Slack solving that Gitter fails at, and what will you lose for this exchange.
IMO there is a non-quantifiable benefit of the openness of Gitter rooms, in that Gitter conversation snippets appear in search results, with an '?at=' querystring so you can jump straight to where the conversation occurred. So while Gitter's search is lacking, there is that, *added* benefit of the free, persistent chat. And as mentioned earlier, Gitter works with your existing accounts. On Sat, Sep 1, 2018 at 9:26 PM Sid Anand <san...@apache.org> wrote: > When we first entered the incubator ~2.5 years ago and we were considering > Gitter (Slack was not an option back then), Jakob Homan (our mentor) > mentioned that the the ASF mailing lists were really the place where things > needed to be documented. We killed our google group and GH issues and moved > into the mailing lists and Jira. We tried Gitter to give people a chance to > get instant answers, though as I mentioned at the top of this thread, it > had a lot of issues. > > I'm glad to hear that the community is gaining some benefit from a > collaborative instant messaging solution, though it does appear from this > thread that the community wants to move to Slack. As a 4-year user of > Slack, I agree Slack is a pretty awesome platform, but I've mostly used > paid versions at my employers. Once I get some guidance on how to set it up > within Apache guidelines, if the ASF has any thoughts on the matter, I'll > proceed to transition. Having 2 parallel solutions will be confusing IMHO. > -s > > > > On Sat, Sep 1, 2018 at 2:30 AM Ash Berlin-Taylor <a...@apache.org> wrote: > > > I'm not a fan of slack for open source work - it's a walled garden, > > signing up is a hurdle (where you have to use a work around of a heroku > > app), not to mention that the client is just so memory hungry! > > > > I'm just a curmudgeon who still likes IRC mainly. So long as I can > install > > https://slack.com/apps/A7DL60U5D-irccloud/ < > > https://blog.irccloud.com/slack-integration/> I won't object ;) > > > > (I am not a fan of Gitter either, but I am constantly logged in via their > > IRC gateway. I'm usually the only PPMC responding in there, Bolke pops up > > from time-to-time too) > > > > -ash > > > > > On 1 Sep 2018, at 02:40, Sid Anand <san...@apache.org> wrote: > > > > > > Great feedback. There is an overwhelming interest in moving Gitter to > > > Slack. Just curious: for the folks who set up Slack for other Apache > > > projects, did you go via an Apache Infra ticket? > > > > > > -s > > > > > > On Fri, Aug 31, 2018 at 4:32 PM James Meickle > > > <jmeic...@quantopian.com.invalid> wrote: > > > > > >> I am in the gitter chat most work days and there's always activity. > > >> > > >> I would be fine with switching to permanent retention slack for > > >> searchability but don't see the point of switching without that > feature. > > >> > > >> On Fri, Aug 31, 2018, 12:59 Sid Anand <san...@apache.org> wrote: > > >> > > >>> For a while now, we have had an Airflow Gitter account. Though this > > >> seemed > > >>> like a good idea initially, I'd like to hear from the community if > > anyone > > >>> gets value of out it. I don't believe any of the committers spend any > > >> time > > >>> on Gitter. > > >>> > > >>> Early on, the initial committers tried to be available on it, but > soon > > >>> found it impossible to be available on all the timezones in which we > > had > > >>> users. Furthermore, Gitter notoriously sucks at making previously > > >> answered > > >>> questions discoverable. Also, the single-threaded nature of Gitter > > >>> essentially makes it confusing to debug/discuss more than on topic > at a > > >>> time. > > >>> > > >>> The community seems to be humming along by relying on the Apache > > mailing > > >>> lists, which don't suffer the downside listed above. Hence, as > newbies > > >> join > > >>> Apache Airflow, they likely hop onto Gitter. Are they getting value > > from > > >>> it? If not, perhaps we are doing them a disservice and should > consider > > >> just > > >>> deleting it. > > >>> > > >>> Thoughts welcome. > > >>> -s > > >>> > > >> > > > > >
