SoylentNews is people
SoylentNews
https://github.com/rust-lang/team/pull/671
The entire moderation team resigns, effective immediately. This resignation is done in protest of the Core Team placing themselves unaccountable to anyone but themselves.
As a result of such structural unaccountability, 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. To leave under these circumstances deeply pains us, and we apologize to all of those that we have let down. In recognition that we are out of options from the perspective of Rust Governance, we feel as though we have no course remaining to us but to step down and make this statement.
In so doing, we would offer a few suggestions to the community writ large:
We suggest that Rust Team Members come to a consensus on a process for oversight over the Core Team. Currently, they are answerable only to themselves, which is a property unique to them in contrast to all other Rust teams.
- In the interest of not perpetuating unaccountability, we recommend that the replacement for the Mod Team be made by Rust Team Members not on the Core Team.
- We suggest that the future Mod Team, with advice from Rust Team Members, proactively decide how best to handle and discover unhealthy conflict among Rust Team Members. We suggest that the Mod Team work with the Foundation in obtaining resources for professional mediation.
(Score: 2) by Thexalon on Saturday November 27 2021, @08:44PM (3 children)
That sounds great, until you ask: Who gets to decide what counts as "professional" or "asshole"? Who gets to decide what "just act like adults" means?
And that matters a lot. Some examples:
- For basically the entirety of the 1950's and early 1960's, it was considered perfectly normal behavior for male bosses to make sexually suggestive comments directed at female subordinates. Depending on the industry, that was still quite common as recently as the 1980's or even 1990's. There are people walking around right now who think it's perfectly "professional" for a dude to say "nice rack" to a woman at work.
- This has definitely happened more than a few times: Person A submits a patch. Person B says "Patch rejected, because it causes these bugs: ..." Person A starts saying "Whaaaa! Person B was super-mean and unprofessional asshole to me! Why can't they be nice and just accept my code?"
- Somebody watches porn on shared computers. They don't leave a physical mess, but the admin catches them because there was stuff left on the hard drives. "Hey, we're all adults here, just be mature and delete it!" says the person who just got caught.
When the wrong people are in charge of enforcing seemingly simple rules, you can bet that those seemingly simple rules will be twisted to allow for their own bad behavior.
The only thing that stops a bad guy with a compiler is a good guy with a compiler.
(Score: 2) by edIII on Saturday November 27 2021, @09:29PM (2 children)
All of that is handled under my CoC. I guess professionalism and being an asshole can be vague, but I'm defining professionalism apparently as being near Vulcan-like in behavior.
Does the fact that a contributor to the project has attractive and/or impressively sized genitalia or secondary sex characteristics have anything to do with project itself? No. So those comments and behavior are censured. Leave such things outside of the project. Period. Nobody cares about your cocks, sweater puppies, or camel toes.
Evaluate separately.
Did Person B use anything but constructive criticism, logic, and reason when rejecting the patch? If so, reject contribution. If not, accept contribution.
Did Person A react illogically and emotionally to a rejected patch that was accompanied by constructive criticism, logic, reason, and examples of why it won't work? If so, then eliminate the noise from the project by erasing the comments and censuring Person A. If not, then let Person B be handled by the CoC.
Maturity Irrelevant. Project resources used for personal purposes while also increasing attack surface to outside threat vectors. Heavily censure person who got caught, and possibly remove from project. Remove files left on hard drive to secure air-gapped tablet for rigorous and thorough analysis.
What else do you have? :)
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 2) by Thexalon on Saturday November 27 2021, @10:20PM (1 child)
And that's all well and good when you, a responsible and fair-minded person, are the adjudicator.
It doesn't work at all when the adjudicator actually agrees with any of those stances. Which happens sometimes - as in, I've seen it happen.
The only thing that stops a bad guy with a compiler is a good guy with a compiler.
(Score: 2) by edIII on Saturday November 27 2021, @10:40PM
In other words, like I said, it's an elementary school playground. Just without any adults.
Yeah, that's very sad. Especially when the people in charge that should be moderating the whole thing are part of the problem.
Technically, lunchtime is at any moment. It's just a wave function.