I'm Australian and have the direct counter experience. Most of the business I've worked for consider Slack as ephermal.
Email is for significant communications.
Outside of work, I'm using daily for things like booking bands, talking to strata, etc.
While email in a lot of large companies might tend to be becoming a one-way distribution system; it is still vibrant and heavily used in smaller enterprises.
I am skeptical that is actually the case though, there are so many use-cases where you have to think through the consequences too carefully:
- what happens when the source repository rewrites all the commits (to remove one); should the forks also be re-written?
- what happens when the source repository disappears?
_All_ of the problems go away when you actually do a "git clone" of the source repository and have your own objects. More storage, yes, but way fewer corner cases to think through.
A common problem when using Gerrit is the Change-Id being copied across from different branches (via, for example, git cherry-pick).
The idea is ... interesting, but the implementation of Change-Id has quite a few problematic corner-cases which make normal git operations (rebase, cherry-pick, merge) more delicate than the need to be.
GitHub repo says it was archived 2 years ago: https://github.com/Netflix/titus