Live data from Hacker News

Rust Moderation Team Resigns

github.com

721–730 of 912 posts

Re: Rust Moderation Team Resigns

#721
post #457

Earlier quoted context omitted.

Nice example, arxiv papers (and any decent paper in general) contains an abstract to provide context about the contents of the papers as well as references to other papers cited within. Arxiv papers might not be written for me now , but if I got interested in a paper (and had time to spare, of course) I would probably have most of the content I need to at least grasp the general content of the paper. Thanks for the e…

No offense, but you don't seem to have read many specialized scientific articles. The time investment to even grasp the general idea of very specialized papers would be significantly longer than the investment you need to make to become a respected member of the rust community and apply for the next mod-team. Then you could also ask the members of the previous mod-team about the specifics of their complaints. Maybe y…

That sounds like low-key elitism to support your point.

My point is that arxiv papers (like most papers) come with an abstract to set the stage and have references to other papers cited therein.

Re: Rust Moderation Team Resigns

#722
post #84

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…

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

Re: Rust Moderation Team Resigns

#723
Why are the vast majority of Rust devs furries?

Showcasing your sexual kinks wrt a project that has nothing to do with sex is pretty off-putting to begin with but the fact that most furries are also pedophiles makes it insane that any self-respecting company wants to be associated with Rust.

Re: Rust Moderation Team Resigns

#724
post #504
post #364

This is a real shame. From the early days of Rust (pre-2018?) I built up this mental picture of it having a considerably better run and governed community, with people putting time into thinking about how a community should work rather than it being something that's ignored because "we're here to write code and managing a product is a waste of time". I lost touch (the last video I watched which might be the one that…

This person? https://archive.fo/f10KK

Relevantly enough, given this is about moderating the rust technical team, Rod Vagg had this to say about moderating the nodejs technical team:

“My assessment of the claim that I am a hindrance to inclusivity efforts is that it hinges on the singular matter of moderation and control of discourse that occurs amongst the technical team. From the beginning I have strongly maintained that the technical team should retain authority over its own space. That its independence also involves its ability to enforce the rules of social interaction and discussion as it sees fit. This has lead to disagreements with individuals that would rather insert external arbiters into the moderation process; arbiters who have not earned the right to stand in judgement of technical team members, and have not been held to the same standards by which technical team members are judged to earn their place in the project. On this matter I remain staunchly opposed to the dilution of independence of the technical team and will continue to advocate for its ability to make such critical decisions for itself. This is not only a question of moral (earned) authority, but of the risk of subversion of our organisational structures by individuals who are attracted to the project by the possibility of pursuing a personal agenda, regardless of the impact this has on the project itself. I see current moves in this direction, as in this week’s moderation policy proposal at nodejs/TSC#276, as presenting such a risk. I don't expect everyone to agree with me on this, but I have just as much right as everyone else to make my case and not be vilified in my attempts to convince enough of the TSC to prevent such changes.”

Re: Rust Moderation Team Resigns

#726

Earlier quoted context omitted.

...I think many people would disagree with you about Linux. And perhaps GCC as well.

Yeah it's comical because Linux has so obviously driven a lot of people away from kernel development. Tech is male-skewed, and OSS more so, but Linux kernel dev is even then still at the far end of the gender disparity spectrum.

> Yeah it's comical because Linux has so obviously driven a lot of people away from kernel development.

I hear this "a lot" very often, but then it seems to be from people who have no real interest in technical work of kernel/OS core development. Linux is not the only way to scratch your itch for interest in low-level system dev. Like, this is just personal experience, but I have heard this on the order of 50-100 times: someone parroting how toxic Linux kernel dev is because of drama they heard -- but then you kind of dig a little bit and see what kinds of software stuff interests them, what do they work on -- probably only once or twice has it been anything embedded, hardware related, close to the metal. I would need compelling evidence to change my opinion that most of the complainers have no interest in the work being done by the community they are complaining about -- and I am fully aware that a number of people have departed Linux development, but we are talking about a tiny number of the thousands of contributors over the years -- you can't please everyone.

The hobby OS, emulation and demo scene is a pretty good indicator for "natural"* gender breakdown. These tend to be tight, tiny communities or often lone wolves working on projects. It is male dominated. This can't be explained by any systemic or community gatekeeping - because there is no system nor any mandatory community for participation or distribution. Nothing prevents anyone from putting their work out there.

* I am not discounting there may be other systemic reasons that set up this condition - but it has to be societal conditions that are in place in early childhood -- something that happens a bit before one considers contributing to the Linux kernel.

Re: Rust Moderation Team Resigns

#727
post #721

Earlier quoted context omitted.

No offense, but you don't seem to have read many specialized scientific articles. The time investment to even grasp the general idea of very specialized papers would be significantly longer than the investment you need to make to become a respected member of the rust community and apply for the next mod-team. Then you could also ask the members of the previous mod-team about the specifics of their complaints. Maybe y…

That sounds like low-key elitism to support your point. My point is that arxiv papers (like most papers) come with an abstract to set the stage and have references to other papers cited therein.

Apologies, you are correct that was a snarkish response. I stand by my point though, we don't have any right to see "details" of the accusation. In particular the moderator team seems to resign not because of the particular case but because of structural issues. That is what they pointing towards.

Now regarding the structural issues, I actually could find very scarce information about the governance of Rust. I certainly could not find any information on how the core-team gets selected and what the processes are around being added or removed from the team. I also did not find much about their duties. So in that sense there seems to be verifiable information about lack of transparency (if not accountability).

Re: Rust Moderation Team Resigns

#728
post #55
post #16

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

It's the opposite: it's a "we refuse to drag this drama out into the public sphere" statement.

> we refuse to drag this drama out into the public sphere"

I genuinely can’t think of a more dramatic way to drag this into the public sphere than saying “we all quit due to unspecified violations of the vague code of conduct - go make your best guesses what those were”

Re: Rust Moderation Team Resigns

#729
post #622
post #594

Earlier quoted context omitted.

This person being a prominent part of the Rust community definitely does not make me want to engage with it and does make me wary of the stability of the language as well: https://archive.fo/f10KK

She's not?

I don't know what was originally written, but here is from Ashley Williams (@ag_dubs) Twitter bio:

> a mess like this is easily five to ten years ahead of its time. @rustlang core team. slinging open source strategy at @pubstruct . she/they

Re: Rust Moderation Team Resigns

#730

Earlier quoted context omitted.

The vast majority of open source projects do not create their own open source license- most of them choose from a relatively small selection of widely used licenses (GPL, BSD, MIT, Apache, etc.). Why then do so many project choose to roll their own CoC? I'd expect that there would also be a relatively small handful of widely used CoCs to choose from, and a project could pick based on their projects' needs.

I'm on a tiny project without a CoC because I don't know how to enforce it if we had one. Enforce means it needs to apply to me, and also whoever enforces it needs to be active to watch for issues. I wish KDE/Gnome/other big project would just do a CoC as a service for tiny projects. For the most part the CoC should be standard, and a few experts to enforce it would be better than random enforcement. (note I have no…

I don't think it makes sense to have a CoC beyond "Don't be a jerk" until you have multiple teams and more complex governance structures.
Post reply on HN