| > It's possible that there were CoC violations that they were not able to moderate, that the actions available to them were limited (e.g., they would have initiated a ban but they were not able to ban a core team member), that a core team member intervened to prevent effective moderation, or that the core team prevented the mod team from being able to access official core team channels in order to moderate. It's not clear to me that they're claiming a violation occurred. The wording is vague, but one interpretation is that they simply wanted more control over the core team but the core team didn't want it structured that way, so the mod team resigned. IMO, it would be strange to make a moderation team the highest authority in an organizational structure. I don't really agree with their demand to be the ultimate authority over everyone. Violation or not, I wish they could have come to an agreement without throwing ambiguous accusations out into public as they quit. Between this and the "I refuse to let Amazon define Rust" post a few months ago we're getting a lot of drama with few, if any, details. There's a lot of "just trust me, but don't listen to what anyone else says about the situation" in this post. Their closing statement asking everyone to not trust anything the core team says makes this feel particularly petty: > We
recommend that the broader Rust community and the future Mod Team exercise
extreme skepticism of any statements by the Core Team (or members thereof)
claiming to illuminate the situation. I really hope that drama like this doesn't become one of the defining features of the Rust community. |