Our great sponsors
-
governance
Discontinued The home for Rust's governance documentation, such as team charters. (by rust-lang)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
regex
An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
xgb
The X Go Binding is a low-level API to communicate with the X server. It is modeled on XCB and supports many X extensions.
Based on their mods.toml file:
https://github.com/rust-lang/team/blob/master/teams/mods.tom...
The "description" field says "Helping uphold the code of conduct and community standards" which is why they left. My guess is people could of done literally any number of things that violated the Code of Conduct. They want to not start a witch hunt which is respectable. As someone else around this thread said though, it leaves room to interpret it as the absolute worst. I am going to assume it's not as awful as it seems and might just be something to the tune of differing opinions. Maybe another Linus Torvald scenario.
I have used Rust for years, but I never bothered to look into the governance structure.
How are team members selected? Who picks new team members? Who has authority to kick someone off a team?
I can't find anything online, except this very bare-bones WIP stub. [1]
This seems to be a glaring oversight, I really thought that there were proper procedures in place.
Especially now, with Rust becoming more and more popular, the foundation in place for almost a year, and corporate interest flooding into the project, I would have expected procedures to already be in place.
There certainly seem to be other cracks in the system. See for example "I refuse to let Amazon define Rust" by Steve Klabnik, discussed at length on HN. [2]
[1] https://github.com/rust-lang/governance/blob/master/common/m...
[2] https://news.ycombinator.com/item?id=28513130
i think the parent was referring to https://github.com/golang/go/issues/45970
The compiler literally checks what GitHub org originated the package. If you fork a package that uses FFI, it won't work unless you remove the check from the compiler or use a hacky workaround to trick the compiler: https://github.com/elm/compiler/blob/770071accf791e817144070...
You might care to notice that the resignation was announced by BurntSushi, who is one of the most well-respected, talented, and prolific contributors in the wider Rust community. Amongst other things, they are the author of ripgrep[1], the regex[2] crate, and the byteorder[3] crate. They have multiple projects which are amongst the most-downloaded crates[4] in the Rust ecosystem.
[1]: https://github.com/BurntSushi/ripgrep
He's also a prominent contributor to the Go ecosystem.
https://github.com/BurntSushi/toml