-1 on *steering* users, especially new ones to Slack.

-- it requires signup/permission to a third party application.
-- its searchablilty is clunky at best.
-- messages are only going to reach people who are signed up/logged in
-- even when someone has signed up etc. they'll be cut out of and unaware of, 
any conversations outside of their working hours/timezone.

If a group of people agree to have a syncronous converstion on Slack between 
them, that’s up to them. And there's maybe an argument for making sure that 
they're aware that there is the option to use Slack for this.

And lastly - if it didn't happen on a mailling list; it didn't happen.

Kind regards

Paul Angus

-----Original Message-----
From: GitBox <g...@apache.org> 
Sent: Thursday, April 1, 2021 7:50 PM
To: dev@cloudstack.apache.org
Subject: [GitHub] [cloudstack-documentation] GabrielBrascher commented on pull 
request #204: Remove IRC reference as it is no longer used


GabrielBrascher commented on pull request #204:
URL: 
https://github.com/apache/cloudstack-documentation/pull/204#issuecomment-812102731


   @DaanHoogland I was wondering this as well. But decided to not include Slack 
for now due to the ML discussion 
[[1]](https://lists.apache.org/thread.html/296def97c549e0b75bc14d0382ae412245cef6088e576acbcb007cc8%40%3Cdev.cloudstack.apache.org%3E).
 Removing IRC was a consensus; however, not everyone agreed on having Slack as 
an "official" communication platformCloudStack.
   
   We might need to re-open the discussion aimed at Slack then.
   
   Any thoughts @DaanHoogland @PaulAngus @svenvogel @andrijapanicsb @rhtyd 
@nvazquez @NuxRo (and others)?
   
   [1] 
https://lists.apache.org/thread.html/296def97c549e0b75bc14d0382ae412245cef6088e576acbcb007cc8%40%3Cdev.cloudstack.apache.org%3E


--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the URL above to go 
to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Reply via email to