> Our only office is Slack.
You mistyped Mattermost :)
Seriously, no reason to share all your company inner workings with a random 3rd party when it takes literally 5 minutes to set up a completely private (and also free!) clone of the same.
You mistyped Mattermost :)
Seriously, no reason to share all your company inner workings with a random 3rd party when it takes literally 5 minutes to set up a completely private (and also free!) clone of the same.
I have a work phone that I take with me when I am on-call or on a customer site. Slack (or whatever we decide to use) absolutely has to work here.
I might trust Github more simply because their entire product and value proposition is built around the use case of storing code while some company that builds a restaurant app -- their primary business isn't building code storage infrastructure. So why add operational overhead because of unfounded paranoia?
Unless you're running your own metal in your own data center, there's always 'risk.' Even then, if your system is connected to the internet there's still risk.
Proper risk management isn't "paranoia all the time," but an evaluation of the degree of harm posed by a particular hazard along with the likelihood of that hazard occurring. Then mitigating that risk in a way that is commensurate with those variables.
I'm not bashing GitHub, but some people find more value and less risk in using git in its "native" distributed mode.
Risk analysis: using online DVCS/bugtracker/chat service you are one compromised password away from letting an attacker read the whole contents and potentially alter them. Many of those passwords will be stored in browser. Browsers are known for being softer targets compared to servers, generally speaking.
Contrast this with an on-premise services: You still have login credentials but also require people to badge-in to access the building and login on the desktops or start a VPN (often requiring creds and 2fa).
When self-hosting you have to care about your service-level agreements and trouble solving. If you rely on it you quickly need a growing IT/operations team. sometimes it's cheaper to pay somebody how is specialized on this. Of course one has to evaluate the company, with the ones which make money from selling information (to advertisers) I'd be more critical, but that's a matter of evaluation of options.
Now, just like GitLab, it is a very serious thing and we consider using it instead of relying on a 3rd party. Yet, we are a very small team and cannot dedicate too much time in maintaining/upgrading apps :\
Just look up Digitalocean or Bitnami.
Rather than 10 people writing "agree" one can react and others can click the reaction similar to an upvote. That cuts down considerably on the noise so yes, I'd say it enhances professional communication.