+1 to switching over. One less comms client + history + searchability is enough to get my vote easy.
On Tue, May 28, 2019 at 5:52 PM Jonathan Ellis <jbel...@gmail.com> wrote: > I agree. This lowers the barrier to entry for new participants. Slack is > probably two orders of magnitude more commonly used now than irc for sw > devs and three for everyone else. And then you have the quality-of-life > features that you get out of the box with Slack and only with difficulty in > irc (history, search, file uploads...) > > On Tue, May 28, 2019 at 4:29 PM Nate McCall <zznat...@gmail.com> wrote: > > > Hi Folks, > > While working on ApacheCon last week, I had to get setup on ASF's slack > > workspace. After poking around a bit, on a whim I created #cassandra and > > #cassandra-dev. I then invited a couple of people to come signup and test > > it out - primarily to make sure that the process was seamless for non-ASF > > account holders as well as committers, etc (it was). > > > > If you want to jump in, you can signup here: > > https://s.apache.org/slack-invite > > > > That said, I think it's time we transition from IRC to Slack. Now, I like > > CLI friendly, straight forward tools like IRC as much as anyone, but it's > > been more than once recently where a user I've talked to has said one of > > two things regarding our IRC channels: "What's IRC?" or "Yeah, I don't > > really do that anymore." > > > > In short, I think it's time to migrate. I think this will really just > > consist of some communications to our lists and updating the site > (anything > > I'm missing?). The archives of IRC should just kind of persist for > > posterity sake without any additional effort or maintenance. The > > ASF-requirements are all configured already on the Slack workspace, so I > > think we are good there. > > > > Thanks, > > -Nate > > > > > -- > Jonathan Ellis > co-founder, http://www.datastax.com > @spyced >
