[iamed2]

There are two statements here regarding things that have happened:

> the Core Team placing themselves unaccountable to anyone but themselves

> we have been unable to enforce the Rust Code of Conduct to the standards the community expects of us and to the standards we hold ourselves to

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.

Seems to be a wide variety of possibilities and leaving the nature of the situation ambiguous* will likely make it difficult for a new mod team. I hope the now-former mod team are open and direct with new or potential mod team members about the environment they're entering.

* I do think it's right for the mod team to not reveal the specifics in public; that would likely provoke targeted harassment and make the situation much worse

[PragmaticPulp]

> 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.

[whatshisface]

I wish they were saying "trust me." What they're actually saying is, "I won't tell you anything, and don't trust anyone who does."

[setr]

> 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.

I think it makes sense, scoped to their domain. Eg a security team can’t do their jobs effectively if they can’t apply their policies to the CO or if CO can arbitrarily undo it — security needs to have the last say on security policies, but that doesn’t put them on the top of the chain.

The same would be true with whoever does financial auditing and verifies everything is done to process & legally, as well as HR guarding against violations, and so on. The C*O must be held accountable as well, because their violations are also the most potentially damaging

[politician]

This kind of drama is already a defining feature of the Rust community. They can’t go 6 months without some kind of incident like this. It would be a positive if they could have a BDFL or corporate sponsorship to structure the community going forward because it doesn’t seem like the current community approach really works in practice. I realize that’s probably not possible at this point though.. unless maybe Microsoft steps in.

Disclosure: I am an outside observer, and I find Rust to be excessively syntax dense. Take my opinion with a grain of salt.

[golemotron]

> 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.

It is like HR staging a coup d'etat.

[mzs]

The same mod team member is strongly implying elsewhere that such a potential violation did occur:

>burntsushi ripgrep · rust 31 points 2 hours ago

>If we had an answer to your implied question it will necessarily reveal things (via obvious logical inferences) that we carefully avoided revealing in our statement.

https://old.reddit.com/r/rust/comments/qzme1z/moderation_tea...

[monopoledance]

On a side note, I absolutely love the Reddit Rust community. It's somehow devoid of all the anger, loaded harshness of pretty much any other subreddit or HN. So fucking respectful and friendly there. (At least, every time I visited.) I can only assume rustaceans are generally better people! Hanging out there is like a resort within the internet. Please, if you go there leave your edgy internet persona behind, but bring your bathing suit and a tasty cocktail, instead - enjoy life and programming.

[zozbot234]

> they would have initiated a ban but they were not able to ban a core team member

If that was the case, the obvious response would be a formal statement of rebuke and censure wrt. the offending member's behavior, which would clarify that such things aren't welcome in the project. The fact that we aren't getting anything close to that extreme suggests that this is in fact a big fat nothingburger. (Unless you think that CoC violations are so widespread in the Rust Core Team that naming the specific people involved would have made no discernible difference, but so far we've seen nothing to indicate that.)

[babyblueblanket]

It might be that they cannot censure the offending member in any capacity, due to their core team member status. In that case, resignation is the only thing they have to effectively rebuke behavior.

[unethical_ban]

> I do think it's right for the mod team to not reveal the specifics in public; that would likely provoke targeted harassment and make the situation much worse

Instead, we have countless people bantering and taking "sides" about hypotheticals. In a world mostly devoid of secrets on the web, I think they could have, at the least, masked identities and summarized the issue.

[hintymad]

It seems there is an internal communication channel for the Rust team? I thought that the moderation team would moderate discussions in open forums like mailing list or issue trackers, but in this case we don't know what happened behind closed doors.

[stouset]

You might care to notice that the resignation was announced by Andrew Gallant—more commonly known as BurntSushi[1]—who is one of the most well-respected, talented, and prolific contributors in the wider Rust community. Amongst other things, they are the author of ripgrep[2], the regex[3] crate, and the byteorder[4] crate. They have multiple projects which are amongst the most-downloaded crates[5] in the Rust ecosystem.

One would struggle to find more than a handful of people who have done more "actual work" for Rust than Andrew.

[1]: https://blog.burntsushi.net/about

[2]: https://github.com/BurntSushi/ripgrep

[3]: https://github.com/rust-lang/regex

[4]: https://github.com/BurntSushi/byteorder

[5]: https://crates.io/crates?sort=recent-downloads