On the RustConf Keynote
blog.rust-lang.org
blog.rust-lang.org
It's clear over the last 6-months that the project lacks clear and mature (in multiple senses) governance. I suggest you quickly take the following actions:
1. The individual(s) responsible for this situation publicly apologize, With their name(s) attached, and possibly resign from their leadership position. This muddy, cloak and dagger, he said she said, stuff is completely unnecessary and just breeds distrust. The community/project needs clarity and accountability if it is going to survive.
2. All statements need to have names of individuals attached, either "John Smith, on behalf of Rust Leadership chat" or a big list of all members of the leadership chat. Stop hiding behind amorphous groups.
3. Adopt and implement the Leadership Council RFC. It's obvious this intrum leadership chat is ineffective in providing direction and clarity on the project. Rust needs a clear organizational structure.
The email was not signed, and the executives agreed that they had proofed it but there was no possible way to know who sent it! Never mind the email account or rationale or executive team; must have been a ghost. One hour later we were no closer to the truth. Moral of the story; accountability is difficult, and I doubt we will get an answer here.
We have given Rust governance enough time and it is essentially still infantile and they continue to add fuel to the fire to this pointless drama.
Some people have warned for years [1] about the issues with Rust's governance structure as a 501(c)6 and now the core team have realized its inherent issues and is no more bureaucratic than the Linux Foundation. This is why you have these leadership issues and the opaqueness you have right in front of you.
Rust governance is not a 'community'. And its (past and present) problems of setting it up as a 501(c)6 just shows that to them the 'community' never mattered, only corporate interests.
https://github.com/rust-lang/team/blob/2cea9916903fffafbfae6...
Thankfully as someone who writes a lot of code in Rust but has little involvement in building it I can largely ignore it, but I do worry that it is damaging the long-term health of the community.
The "leadership chat membership" made a mistake, then they apologized and they're discussing how to avoid this mistake in the future. How is that irrelevant for HN?
It sounds like this is governance by a committee. Is that right? As in, there is no single person in charge here? If so, I can certainly see how that might not work out.