team VS TSC

It's just as true today, though. When the Rust mod team resigned en masse in 2021, it was announced by a programmer (the author of ripgrep) [0], and the conflict was with the core team (also programmers). A supermajority of their contributors to open source projects are programmers, so most famous meltdowns are going to be conflicts between programmers, not between programmers and the tiny minority of non-technical contributors.

I'm still waiting for anyone to give an example of an open source project meltdown that was triggered by non-technical contributors.

[0] https://github.com/rust-lang/team/pull/671

the mods publicly outlined the governance issue, while keeping the moderation issue private (https://github.com/rust-lang/team/pull/671)

Here's another list: https://github.com/rust-lang/team//blob/d4c071b86c33683845919cf27eabf33e15fb6784/teams/interim-leadership-chat.toml

they linked their (user)names:

https://github.com/rust-lang/team/blob/2cea9916903fffafbfae6...

You can also check rust-lang/team repo, where shows more than 400+ people have worked on the Rust Project as official members. And on thanks.rust-lang.org, it shows that 300+ people have been involved in each recent release. I believe the number of active contributors may be more than 100+.

Right, but this type of drama isn't new in the community. A while back the whole mod team resigned because they were not able to hold the core team accountable. In fact I remember it being said that the Core Team placing themselves unaccountable to anyone but themselves. So I don't think I'm being dramatic at all here.

If that's too onerous, you can also look at the list of directors and observe that there are people titled "Project Director" who you can look up on https://github.com/rust-lang/team and observe that they have in fact been selected from the project teams.

You're more than welcome to set the narrative straight. The infighting among Rust maintainers is based partially on your resignation note where you said the Core Team was "unaccountable" https://github.com/rust-lang/team/pull/671 and implied that they were untrustworthy. The same people that once went around starting language wars, like calling Zig a "massive step backward" for the industry https://news.ycombinator.com/item?id=32783244.

I'm just an outsider observer, who's been watching the sparks fly. It's been interesting as well to watch how quickly memories changes when positions are dangled. If there's ever an investigative report on the tribulations of Rust, they can also dig into the allegations of nepotism around one maintainer and his girlfriend on the project, vis-a-vis Amazon. https://news.ycombinator.com/item?id=28633113.

The dates were known in advance - however, the Node team expected OpenSSL 3 to be out before the release of Node 16, but it didn't happen - so they had to release with OpenSSL 1.1.1. Between the lines, I think that there was some minor hope of maybe upgrading, but obviously it was to difficult.

https://github.com/nodejs/TSC/issues/1222

>After the Node incident, it's highly likely Ashley Williams is involved again due to her propensity for racism and sexism.

I didn't know what this was referring to so I looked it up.

Here's a Reddit thread which seems to be the genesis of the complaint (an archive link because the actual post was removed):

https://archive.md/VEtHu

Link to original Reddit thread:

https://old.reddit.com/r/node/comments/6whs2e/multiple_coc_v...

NodeJS GitHub issue thread

https://github.com/nodejs/TSC/issues/324

HN threads:

https://news.ycombinator.com/item?id=16085545

https://news.ycombinator.com/item?id=15115989

https://news.ycombinator.com/item?id=16073017

If Node.js 12.x and 14.x releases have full support for ES modules, what gives? I was wondering the same, so I asked Matteo Collina on Twitter (he's a member of the Node.js TSC). Myles Borins (also a member of the TSC) chimed in on the thread to explain the rationale behind ES modules being marked as 'Experimental' in the 12.x and 14.x release lines: