41–50 of 912 posts
'Core team' as a concept naturally leads to elitism.
How to promote on merit and not nepotism or corruption is the hard problem.
Earlier quoted context omitted.
Does it? I am not familiar with the Rust language development but I read it as "team that takes care of the core (of the language)".
Well, you either have a explicit hierarchy of people working on something, and then the people who are a part of the "top layer" can sometimes start to look down on the ones who belong to the layer below, seeing them as less knowledgeable or not producing useful output. Sometimes that leads to people starting to close down into their current layer, and forms "us-vs-them" groups. Or, you have a implicit hierarchy and…
So? Are you going to blame them for seeing the reality as it truly is?
Earlier quoted context omitted.
It looks like they've decided to keep the reasons secret and unaccountable.
"Unaccountable"?
> In this message, we have avoided airing specific grievances beyond unaccountability. We've chosen to maintain discretion and confidentiality. 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. Isn't that a kind of scorched earth statement? I read it as "we will be discreet and…
"We're not going to say what, specifically, one or more Core Team members are being held unaccountable for. If the Core Team does say what, specifically, we aren't necessarily going to respond. Don't take our non-response as an endorsement that this is what it's about."
Earlier quoted context omitted.
They explicitly say they are not saying: > In this message, we have avoided airing specific grievances beyond unaccountability. We've chosen to maintain discretion and confidentiality. 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. With the earlier bit about the Core Team not…
Which is a pity. I always saw the Rust organization as one that acted in public and with transparency, I guess that's why I expected something more clear instead of a resignation of a full team without any further clarification about why. But, of course up to them what they feel comfortable sharing with the public, if it's something that has to stay private I guess that's the way it will be.
Obviously there is a story behind this ("the Core Team placing themselves unaccountable to anyone but themselves"), but it's not entirely evident from the PR itself what actions led down to this happening. I guess somewhere a Core Team member broke the Code of Conduct but the deed went unpunished? I was expecting some references or links to where this actually happened, but couldn't find anything. Anyone know what ha…
Maybe is better that no single action is emphasized or a single person and focus on the actual problem, the fact that there might be a group that is above the laws/rules and possible solutions. Edit: I think if some action will be made public then everyone will focus on debating why that action was correct/incorrect , then a lot of mostly politics dirt will be thrown around etc.
But for some reason, the formalization of conduct enforcement stuff around OSS projects still feels weird, off-putting, and very "Corporate HR"-y to me. I still get a kinda awkward feeling every time I see a code of conduct in a freaking code repository as opposed to an MOTD or mailing list welcome email or the like. The contents is normally reasonable and if it were in one of those other formats it'd feel normal, but checked into a code repo just feels wildly out of place and needlessly in-your-face?
Maybe I'm just getting old.
Programming Language authors love to formalize everything , but did Rust really need all of these rules and moderators to begin with?
Almost every open source project is being overtaken by social justice warrior leeches. Even Linus Torvalds was kicked out of Linux. I'm surprised that the Rust community pushed back.