> NATS could never graduate Regarding the lack of graduation, I would invite people to read the full comment by user raghu999 on the nats-server discussion[1].

> NATS could never graduate Regarding the lack of graduation, I would invite people to read the full comment by user raghu999 on the nats-server discussion[1]. I will quote two paragraphs from it here, but I really encourage people to read the whole thing: During that lengthy graduation process, the CNCF TOC explicitly and repeatedly raised concerns about the lack of core server maintainer diversity and the risks of single-vendor (Synadia) dominance. Your [Synadia] team's responses at the time consistently deflected these concerns, arguing that client diversity was sufficient, the server was stable/uninteresting for external contributors, and that demanding core diversity was misguided. Now, the narrative has flipped entirely. The very fact that Synadia employees contributed the vast majority (~97%) of the server code – the exact scenario the TOC warned about – is being presented as the reason Synadia must now implement a restrictive BUSL license to recoup investment. This is a stunning reversal. It appears Synadia actively resisted diversifying core control when it was a prerequisite for graduation, only to later weaponize the resulting lack of external contribution as justification for this license change. [1] https://github.com/nats-io/nats-server/issues/6832#issuecomment-2835692350 https://github.com/nats-io/nats-server/issues/6832#issuecomm...