Once again: centralized non-e2ee systems like Slack and Discord are a liability, not the least of which is because of downtime. (The DM logs being mined by an acquirer or intruder is another.)
Patch out the phone-home Segment spyware and selfhost a Mattermost, or a Zulip, or a Discourse (for non-real-time) for your team.
Selfhost a Gitea and a Drone.
It's more simple than you think, and you can backup and restore it onto a new hosted VM in minutes.
> Patch out the phone-home Segment spyware and selfhost a Mattermost,
Just to clarify, by patching out, all you need is to disable a config setting: https://docs.mattermost.com/manage/telemetry.html. It's not like you have to modify the code or anything more intrusive.
Another fan of Mattermost here. Four or five years w/o outage. Maintenance is moving to a new VM every 6mo. Cost is roughly $120/yr. And we can have clients click into our chat w/o requiring them to make accounts with third parties.
I really hate the: For support with CompanyA make account to use service provided by CompanyB to contact A.
Every time I have to use a Slack/Discord to reach a company I'm spam/alert bombed all over again - triple annoying.
Bigger, heavier, requires more resources to set up, maintain, and use. On the other hand it's more stable, mature, has more features and integrations, and I'd guess more secure. Having run both I'd recommend defaulting to Forgejo[0] or Gitea unless your requirements steer you towards Gitlab.
[0]: Fork of Gitea, discussed here previously. Recall that Gitea is itself a fork of Gogs!
I'd add that if you require CI/CD, definitely use Gitlab over Forgejo. I remember they added actions as an experimental feature, but CI/CD in GitLab is quite mature and powerful - it will take time to Forgejo to catch up.
Patch out the phone-home Segment spyware and selfhost a Mattermost, or a Zulip, or a Discourse (for non-real-time) for your team.
Selfhost a Gitea and a Drone.
It's more simple than you think, and you can backup and restore it onto a new hosted VM in minutes.