Last year, as an occasional contributor to the Rust project, I did not think much about the organisational structure of the team behind the project. I saw a hierarchy of teams and groups, team leaders, etc. Just like any other organisation. This year, after getting more involved, becoming a library team member and eventually team lead, I spent some more time thinking about why we have this structure, what these teams are for.
Rust's Most Unrecognized Contributor
I think the Rust language is a big success. When I think back on it I am in awe: so much had to go right to get where we are, and there were so many opportunities to go wrong. It took many tiny miracles for the Rust language to become what it has. Those miracles didn’t happen by accident though: each one was created by a real person, and real people orchestrated them to become something great.
Growing the Rust Community
The Rust community and its commitment to advancing the Rust language are the topics of the fifth video in our series about the Rust…
One year of Rust | Rust Blog
Empowering everyone to build reliable and efficient software.
The state of the Rust dependency ecosystem
Over the past few days, I analyzed over 200,000 crates from crates.io to uncover patterns in maintenance, developer engagement, security, and overall ec...
Traits of Founding Teams That Win — An IT VC’s perspective
By Christopher J. Rust, Founding Partner, Clear Ventures
Review: Team Topologies
Many organizations are struggling with their business agility transformation. One of the reasons is the way they have organized their teams. The focus was probably on efficiency and if these teams …
Rust 2019: Ownership without fear – Dirkjan Ochtman
Like last year, the Rust community team asked community members to write blog posts "proposing goals and directions for 2019"; this is mine. Like withoutboats' post and Niko Matsakis' take, this post will focus on organizational issues. As such, the "ownership" from the title refers to a leadership principle, not the technical type system concept we all know and love.
Shar: One year with Rust.
137 votes, 28 comments. Hi, Reddit! I posted here for a few times, and now our team has reached the important stage of development - we are launching…
Rust Governance: Scaling Empathy
There’s been a lot of talk about improving Rust’s governance model lately. As we decompress from last year’s hectic edition work, we’re slowly starting to look at all the bits of debt we accumulated …
Shepherding v3.1
For open source projects, it can be difficult to find balance between a number of factors: the free time of contributors, the desires of the communities using the project, the ability to on-ramp and mentor new contributors, and to provide necessary guidance and feedback. The Rust Project, and multiple sub-teams and working groups have found success in use of the RFC Process for making informed, high level decisions. However, the RFC process does not address the work necessary for exploratory projects before a decision is made, the work necessary to implement made decisions, or the work necessary to maintain and overhaul parts of the projects in the long run. To address these needs, I'd like to propose a general concept and approach called Shepherding, which aims to assist maintainers of these projects with this aspect of managing the project. By enumerating core goals and putting a name to concepts, but specifically NOT mandating every aspect of implementation, I hope that this technique can be applied across many teams inside and outside of the Rust Project. The "Shepherding v3.1" name comes from a blog post written by Niko Matsakis titled Shepherds 3.0, which also does an excellent job describing the motivations regarding these efforts. This post instead makes a few clarifications and additions to the 3.0 post, and aims to be a "reference manual" for the concept, defining terms and important goals, rather than discussing motivations. Discuss on Reddit Discuss on Twitter
The Evolution of a Rust Programmer
364 votes, 71 comments. 426K subscribers in the rust community. A place for all things related to the Rust programming language—an open-source…
Case Studies — Team Topologies - Organizing for fast flow of value
Examples of Team Topologies used in industry
TeamTopologies/Team-Topologies-Community-Materials
A list of materials relating to Team Topologies (articles, tools, canvases, etc.) generated by the community.
Rust in 2021
This is my response for this year's call for blog posts. I am writing this as a language implementor, not as a language user. I also don't try to prioritize the problems. The two things I'll mention are the things that worry me most without reflecting on the overall state of the project. They are not necessary the most important things.
How to build a multiplayer game - RustFest Global 2020 Pre-Event
As announced on the rust zürisee meetup: I gave a talk about How to build a …
