+1 While Slack isn't my favourite, I think the benefits outweigh the costs. One of the biggest costs is the archive search. You can either use something like what IRC does, with a bot that archives, or a solution like is used here: https://levels.io/slack-export-to-html/ . (The latter approach requires an admin account, though.)
And yeah, I don't like that it requires an invite, but we point new users primarily at the list and that's still the best way for folks to get in touch. People who show up in IRC with random questions mostly walk away with no answers. (Not pointing fingers, it's not like anyone here is a 24/7 support team for ATS.) The list is a much better place to have new folks asking questions anyway. It also sets a better expectation for when answers might arrive. We can couple this with inviting new folks to the Slack channel for more conversation and people may actually wind up feeling _more_ welcomed to the community. But Slack has a much, much better interface for me to follow conversations, and I suspect others feel similarly. I'm often out and about on my phone and don't have immediate access to a computer. I have yet to find an IRC client that coherently works for an intermittent connection. I currently use a Matrix interface instead and it's ok, but not awesome. Slack significantly improves the spamming situation and gives us pretty easy integration for a variety of plugins. It's got good notification settings so I can follow conversations more easily across a variety of devices. It's got a threading system that makes it easier to follow up on slightly older questions and conversations. And perhaps most importantly, it has cute little emoticons you can slap on other people's comments. :D Alternately, we could all contribute to the OSS Matrix and Riot and add features until they're more awesome than Slack and use that. :D But that's kinda hard, so I like the Slack plan in the mean time. On Sun, May 12, 2019 at 8:51 AM Leif Hedstrom <zw...@apache.org> wrote: > > > > > On May 12, 2019, at 08:40, Jason Giedymin <jason.giedy...@gmail.com> wrote: > > > > I like slack, but don’t like that I’d not be able to see past history > > unless: > > - it’s a continuous asf paid account > > - login to slack > > - write a bot to archive (guess that isn’t so bad) > > - in the event asf moved away from slack in the future or goes defunct or > > gets bought out, what to do with past data > > > > So to sum: Id like the data open and free to search (via google even) - but > > I do use slack for many foss groups > > > > We could offer slack as an avenue but make note that any real questions > > that require a more thorough response be initiated via mail list or by > > issue tracker. I.e non supported com channel but it’s there > > This is implicit and doesn’t change whether we use slack, IRC or pidgins. All > decision making is done exclusively on the mailing list. > > — Leif > > > > -Jason > > > >> On May 12, 2019, at 10:18 AM, Leif Hedstrom <zw...@apache.org> wrote: > >> > >> > >> > >>> On May 11, 2019, at 23:35, James Peach <jamespe...@me.com.invalid> wrote: > >>> > >>> > >>> > >>>> On May 12, 2019, at 3:32 PM, Leif Hedstrom <zw...@apache.org> wrote: > >>>> > >>>> Note that this is the ASF workspace, not just ATS. Automating account > >>>> creations here seems like a bad idea, but I guess you can run it by the > >>>> ASF infra ops. My guess would be that they say no :-). > >>> > >>> So users won’t be able to join and participate unless they have some out > >>> of band way to ask for an invite? If that’s the case, I don’t think this > >>> is a good idea. > >> > >> You think it’s a serious burden to send an email to e.g. users@ or dev@ > >> and ask for an invite? Doesn’t seems a whole lot more burdensome than > >> going to a website that you must find. > >> > >> — Leif > >>> > >>>> > >>>> Cheers, > >>>> > >>>> — Leif > >>>> > >>>> > >>>>> On May 11, 2019, at 23:26, James Peach <jpe...@apache.org> wrote: > >>>>> > >>>>> > >>>>> > >>>>>> On May 12, 2019, at 4:57 AM, Evan Zelkowitz <e...@apache.org> wrote: > >>>>>> > >>>>>> +1 > >>>>>> > >>>>>> Though it would be nice if there was an easier way to get new people > >>>>>> in rather than having to manually invite them. My only worry is people > >>>>>> who just want to ask a question dont have an easy way to be able to > >>>>>> get in. So maybe there should be some change on the site to notify > >>>>>> that they should request access on the mailing list or something like > >>>>>> that > >>>>> > >>>>> Most project use https://github.com/rauchg/slackin to automatically > >>>>> issue invites. We should do that here as well. > >>>>> > >>>>>> > >>>>>>> On Fri, May 10, 2019 at 5:45 PM Bryan Call <bc...@apache.org> wrote: > >>>>>>> > >>>>>>> I would like to propose that we move from the IRC to Slack for IM > >>>>>>> communication by June 1st. This is in response to ASF moving to > >>>>>>> Slack for Infra and other channels and spamming that has happened on > >>>>>>> the IRC over the last year. > >>>>>>> > >>>>>>> This would require that people without an apache.org email address to > >>>>>>> be invited. We would keep the IRC channel open after the migration > >>>>>>> to notify people of the Slack channel. > >>>>>>> > >>>>>>> Link to the ASF Workspace: > >>>>>>> https://the-asf.slack.com <https://the-asf.slack.com/> > >>>>>>> > >>>>>>> Channel on Slack: > >>>>>>> #traffic-server > >>>>>>> > >>>>>>> -Bryan > >>>>>>> > >>>>>>> > >>>>>>> > >>>>> > >>>> > >>> > >> >
