You should fork it if you're doing development work like Apple, Intel, AMD, Nvidia, etc because that's how open source works, but it's not necessary if you're using the tooling as-is.
It might be helpful to consider how other people will read your comments before getting defensive next time. It wasn't until I looked at your links that I understood what you were trying to say because it's not the meaning most people are going to assume.
For example, while Rust does have an LLVM fork, it just exists for tighter control over backports, not because there are any modifications to LLVM.
and you think the patches they upstream they don't use in the meantime...?
> and one of them is dead.
yes because the currently used fork isn't public obviously
> Intel staging area for llvm.org contribution. Home for Intel LLVM-based projects.
Seems like they use it to contribute to upstream which is business as usual?
Edit: the concept of fork and hard fork are distinct. I specifically used the word fork