The problem is, we're moving to slack because of the ASF, not as a project level decision. If we're not going to be consistent with the ASF as a whole, I'd prefer staying on IRC.
On Tue, May 14, 2019 at 8:50 AM Fieck, Brennan <[email protected]> wrote: > I'd just like to throw Rocket.chat out there as a FOSS alternative to Slack > that (probably) supports all of the same things desired of from Slack. > Support for voice chat is a little spotty, but I don't think anyone cares > for > this project since likely no one would even want to use that feature of > Slack > anyway. Plus it supports REAL markdown formatting :P > > Just a suggestion. > ________________________________________ > From: Steven R. Feltner <[email protected]> > Sent: Monday, May 13, 2019 10:28 AM > To: [email protected] > Subject: [EXTERNAL] Re: [PROPOSAL] Move from the IRC to Slack > > On 5/12/19, 11:49 AM, "Leif Hedstrom" <[email protected]> wrote: > > > On May 12, 2019, at 09:23, Jan Schaumann <[email protected]> > wrote: > > > > > > Leif Hedstrom <[email protected]> wrote: > > > > > >> You think it?s a serious burden to send an email to > > >> e.g. users@ or dev@ and ask for an invite? > > > > > > For people who are part of the community already, this > > > isn't an issue, but I do believe that this raises the > > > barrier to entry for newcomers. As a data point, _I_ > > > wouldn't bother requesting an invite. Not that I am > > > anything but a very, very sleepy lurker here, but I > > > suppose that's my point - I won't get more engaged if > > > I have to sign up for anything. > > > > > > For many open source projects, if I can't quickly get > > > in touch with developers without having to sign up for > > > anything, I'll simply not reach out, won't report > > > issues nor participate in the community. > > > > Well, you still have to register to be on the mailing lists or on > Github to file issues. Again, this has not changed. Maybe people got an > >impression that IRC is/was the official channel for community and > developer interaction, or filing issues? If so, I’m sorry if we mislead > >everyone, but that was never the case, and will never be the case with > Slack either. Moving to the official ASF slack workspace, as >proposed by > Bryan, seemed like the obvious thing to do, being supported by the ASF and > the infra team. > > > > We have the option to not use IRC or Slack if that’s preferable, and > make it clear that Github Issues/PRs and mailing list are the >official > communication channels. I’m ok with that as well. > > > > Cheers, > > > > — Leif > > On another OS project I keep tabs on, they use a bot that allows you to be > in either Slack or irc. Messages are rebroadcast between both social > channels. > > Would it be possible to implement something like this during a transition > phase until most everyone is used to using slack, and even then leave the > irc channel open so any newcomers could still post a question? Change the > irc channel topic to something along the lines of "You can now find us in > slack...". > > Thanks, > Steven > > >
