On 24/03/18 03:22, Tao Peng wrote:
On Fri, Mar 23, 2018 at 10:36 PM, Anne Bertucio <anne@openstack.org> wrote:
Hi all,
With some of the changes to Slack’s terms of service and integrations with IRC, I wanted to raise the idea of moving to an open source alternative to Slack. Hi Anne,
Most of the container ecosystem communities are doing just fine with slack so I want to understand why we want an alternative. What changes to Slack’s terms of service would scare us away?
There is a few reasons: 1. Slack announced the IRC/XMPP gateway is going to be removed a. This means that a lot of peoples prefered clients will no longer work b. People are now forced to use the RAM / CPU hungry, proprietary Slack clients. 2. Slack just announced that workspace admins can now get access to private messages without notifying users that their chats were accessed. 3. Doing open source development in a closed source walled garden is not what all communities (or developers) want - supporting open standards is important. Other communities are having these discussions as well, not just Kata.
The driver behind having an alternative to IRC was 1) some find IRC intimidating 2) some are more likely to get involved in our community if there’s a communication GUI that they’re familiar with.
I see these are cons of IRC but they are not the reasons to drop slack right?
Cheers, Tao
_______________________________________________ kata-dev mailing list kata-dev@lists.katacontainers.io http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev