yilooki.blogg.se

• #Apple closing work slack channels debate archive#

But these are all things that you could do without taking swift-evolution off of email.Īfair, the option of keeping a mail interface was mentioned in one of the first posts, so none of the positive aspects of email would be lost (it just wouldn't be possible to use the "bonus-features" that aren't available in the medium) It'd even be nice to have an upvote feature.

#Apple closing work slack channels debate archive#

I would love to have a great web archive for swift-evolution-something with a really solid search function, good threading, and most of the other niceties of forums. Gmane is clunky, the thing we have on wrote: I'm happy to answer more questions about Matrix, Riot, Matrix/IRC integration, etc.The reason I don’t like mailing lists is because nobody has a good web UI for them.

As such, any effort by an organized group who would've otherwise "chosen" Slack could simply put their effort into publicizing the fact that users can use either Matrix or IRC to participate in community chat. This means that it's not even necessary to "choose" Matrix. I've been using Matrix through Riot to chat in the Mozilla IRC channels for some time now. This means that using Matrix as the community chat for Rust would make it completely transparently compatible with our existing IRC channels. The Matrix server provided by bridges into both Freenode and Mozilla IRC, so users of Matrix and users of IRC can talk to each other in the same channels transparently, without even knowing that some other users are connected through the other system. It's also important to note that Matrix bridges into other networks, including IRC. You can either create an account to chat, or log in as a guest without providing any information about yourself, just like IRC. The premiere web-based Matrix client right now is Riot. More info about Matrix can be found at the official website. Even the information in those documents should be enough to make it a compelling alternative to Slack for the Rust community's purposes. If you're not already familiar with Matrix, we prepared a good Introduction to Matrix that explains it at a high level. I'm the author of Ruma, a fledgling Matrix server written in Rust. My obviously biased opinion is that the best system to use for an open source project's community chat is Matrix, because it is an open protocol, anyone can build a client or server for it, it's federated, so no single company owns or controls the data, and it's on par feature-wise with Slack (give or take, since all the Matrix clients are still beta-ish at best.) (For me, a good example of this was Kubernetes moving from IRC to Slack.) Many people are already getting annoyed with having to set up yet another Slack account just to discuss or get support for an otherwise open project. While the features Slack provides a team are great and it's a good thing to want to bring them to communities using less powerful technology like IRC, the closed nature of Slack makes it less than an ideal for us. It's fine for a company to use Slack for their employees to chat (which is its primary use case) but it's a very poor fit for something like this. Despite the hype it currently gets (which is largely deserved) it's still just a business, and there's no guarantee it'll still be around in a year or two.

It's a system owned and controlled by a business that does not value openness, interoperability, or the privacy of its users. That said, I really don't like the trend of open communities using Slack. Those who aren't interested can simply not use it, and the Mozilla IRC channels aren't going away. Since you're talking about this being "unofficial" there's nothing to stop you from creating a Slack team for the Rust community. I could write a novel on this topic, but I'll try to keep it brief. Does this sound like a good idea? Would you be interested in helping? With that, I'll open it up for discussion. This channel would be unofficial, just like the gitter and /r/rust on reddit, but even being unofficial, the hope is that there would still be the same high quality Rust community spirit there. If it looks like no one is using it, we'll take that as an indication that people prefer going to IRC/gitter, and we'll close it down so we don't have to keep maintaining it (which is a burden on the moderation team and the Rust folks who sit in there and answer questions). Let's set up a Slack channel for, say, 30 days. For example, our rust-lang/rust gitter has 1000 people in it(!!) While IRC is great, some people prefer to use other means. The idea of the channel would be, just like #rust-beginners, a safe place for people new to Rust to get started. Recently, I've been chatting with some of the other Rust Community team members about starting up a Rust Slack channel.