NCoC
team
Our great sponsors
NCoC | team | |
---|---|---|
6 | 51 | |
1,622 | 292 | |
- | 1.7% | |
0.0 | 9.7 | |
almost 3 years ago | 6 days ago | |
Rust | ||
The Unlicense | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
NCoC
-
An newbie programmer makes an annoying "bump" comment on his bad PR...and tags the 350,000 people who follow the repo. If you have access to the Unreal 4 source code, you may want to unsubscribe from this PR asap.
It's the same with the NCoC. We are not all adults unless we're forced to be.
- Rust Moderation Team Resigns
-
Basecamp mandates social politics free workspace, following Coinbase lead.
These policies really stink of the NCoC. They make the incorrect assumption that "we are all adults" as the basis of their policies with the expectation that people will magically just get along. In actuality, we are all individuals that by default project our childhood insecurities and traumas towards each other. These insecurities and traumas combined with our intrinsic identities influence the framework of values we adopt. Proper codes of conduct ensure the effect our latent traumas have towards each other are mitigated. Anyone who thinks an NCoC style of policy would work doesn't think much about anyone else but themselves or those in their particular group.
- No Code (of conduct) for old men
-
What's with all these 'Code of Conduct' documents?
The only Code of Conduct that I support.
team
-
Non-code contributions are the secret to open source success
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.
- Remove my name from the [Rust] project
- Batten Down Fix Later
-
Graydon Hoare: Batten Down Fix Later
the mods publicly outlined the governance issue, while keeping the moderation issue private (https://github.com/rust-lang/team/pull/671)
-
On the RustConf keynote | Rust Blog
Here's another list: https://github.com/rust-lang/team//blob/d4c071b86c33683845919cf27eabf33e15fb6784/teams/interim-leadership-chat.toml
-
On the RustConf Keynote
they linked their (user)names:
https://github.com/rust-lang/team/blob/2cea9916903fffafbfae6...
-
Let's thank who have helped us in the Rust Community together!
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+.
-
JT: Why I left Rust
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.
-
Can someone explain to me what's happening with the Rust foundation?
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.
-
Safety and Soundness in Rust
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.
What are some alternatives?
wingo - A fully-featured window manager written in Go.
go - The Go programming language
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.
Elm - Compiler for Elm, a functional language for reliable webapps.
r-source - Read-only mirror of R source code from https://svn.r-project.org/R/, updated hourly. See the build instructions on the wiki page.
byteorder - Rust library for reading/writing numbers in big-endian and little-endian.
governance - The home for Rust's governance documentation, such as team charters.
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.