No NickServ spells, no ChanServ incantations, no bouncer to rent or to host on a server. It’s time for instant messaging to get out of the way, and to allow the computer to work for us when it comes to talking to each other. Most of our contributing community is already “working for the computer” when producing the great software we all enjoy. The frugality of the protocol that was once its strength has turned into its weakness in the modern world.
There are issues here and there, but given how basic the whole protocol is, it is fairly sturdy. IRC used to be the top notch system for a while, and is still pretty reliable. I’m going to go into the specifics of Matrix & IRC later on, but let me start with this quote from Thibault Martin over at GNOME: That said, “right” has to be for the whole community.įuture Vision - where I’d like to get to in the next 6 months I know this can be a hot topic for some folks, so (a) please keep the discussion civil, and (b) I want to hear those concerns so that we get this right.
#Irc rss bot how to
I’m going to lay out how to use the solid base of IRC to become a Matrix-first (but not only, IRC will remain) community, and how I hope to move things forward from the Red Hat side. I want to help build that, because I fear that if we don’t, we will fade, and Ansible deserves better than that. Today, that means offering a place where new and existing contributors feel welcomed, safe, and valued, with a rich interface and a low barrier to entry. The way in which we communicate has evolved, as it always has, and periodically we must catch up if we want to attract new people to our community. Please note that at this stage, this represents my views - as I will repeat at the end, my goal is to have the community ratify this, but first I have to convince you :) But I’m going to lead with the big picture, and if you want details, you can keep reading. This post is long, because I have a lot to cover. Building bridges - where the Ansible community needs to go next with chat