The Rust Foundation is interested in creating an online store where we could sell Rust-related merchandise to help fund the growing collection of initiatives at the Rust Foundation, such as the…

The Rust Foundation is thrilled to announce that Carol Nichols has been elected as the newest Rust Foundation Project Director. In this position, she will join incumbent Project Directors Ryan Levick, Scott McMurray, Jakob Degan, and Santiago Pastorino to serve on the Rust Foundation Board of Directors. Project Directors are elected by the entity they represent, which in the case of the Rust Project means they are elected by the Rust Leadership Council. Carol is replacing Mark Rousskov who is stepping down after three years of committed work as a Project Director and Company Secretary. Mark has been a valued colleague on the board, and we are grateful to him for helping us advance the Foundation to where it is today. Carol has been an active contributor to and leader of the Rust Project for many years. She currently serves on the Rust Project crates.io Team and has previously served on the Project’s Leadership Council, the Dev Tools Team, and the former Rust Core Team. Carol is also a co-founder of Integer 32, LLC, the world’s first Rust-focused software consultancy, has organized various Rust community events and conferences in the past, and is the co-author of the Rust Book. “The Rust Foundation is essential to ensuring the sustainability and independence of the Rust Project, and I’m excited to help with that mission,” said Carol Nichols. “I’m hoping to further increase communication and cooperation between the Project and the Foundation.” Rust Foundation Executive Director & CEO Rebecca Rumbul said the following about Carol joining the Rust Foundation Board of Directors as our newest Project Director: “Carol is entering into the Project Director role as a respected leader within the Rust community and will no doubt lend an important, community-focused perspective to the decisions we make as a board. The Foundation is grateful to the Rust Project and the Leadership Council for selecting such a qualified and collaborative representative.” * * * For a detailed overview of how Project Directors are selected, please read this blog published by the Rust Project in 2023 before the previous election.

Today, Amazon Web Services (AWS) announced a collaborative initiative aimed at verifying the safety of the Rust standard libraries. The Rust Foundation has reviewed the plans behind this effort and is excited to serve as host! Although the Rust Programming language is designed to be both safe and efficient, these assurances do not apply to unsafe constructs. Currently, the Rust standard library contains approximately 35,000 functions, including 7,500 marked as unsafe, necessitating a focused effort to ensure their reliability and security. This initiative will include a series of challenges that focus on verifying memory safety and a subset of undefined behaviors in the Rust standard library. Participants can contribute by specifying contracts, verifying library components, or developing new verification tools. AWS’ goal is to contribute to an ecosystem where verification becomes an integral part of the Rust language's continuous integration process. There is a financial award tied to each challenge, awarded upon its successful completion. Other key notes: * Participants can contribute by specifying contracts, verifying library components, or developing new verification tools. * The challenge specifies success criteria that must be met for the solution to be reviewed and merged into the forked repository CI pipeline. * The effort is tool agnostic * The repository provides templates for introducing new challenges, new tools, and instructions on how to submit solutions to challenges. * AWS is supporting this effort and has already seen engagement from 30+ students, academics, and researchers. ### The Rust Foundation’s Role # Although AWS is a Platinum Member of the Rust Foundation, we have opted to host the challenge purely out of our shared belief in the safety and reliability of Rust libraries and our desire to have as much insight as possible into important efforts like this. The challenge rewards committee is responsible for reviewing activity and dispensing rewards. ### Get Involved! # AWS invites you to participate by solving challenges, introducing _new_ challenges or tools, and/or helping review and refine the current processes. Challenge announcement from AWS: https://aws.amazon.com/blogs/opensource/verify-the-safety-of-the-rust-standard-library/ Associated GitHub Repository: https://github.com/model-checking/verify-rust-std

The Rust Foundation's _Community Grants Program_ supports Rust programming language maintainers, community members, and organizers via financial awards, travel stipends, and training support. Through the Community Grants Program, we aim to reward and support innovative ideas that will benefit the Rust ecosystem for an increasingly global and diverse set of users. Our _Fellowship award_ is a grant given annually to active members of the Rust programming language who have made meaningful contributions to the Rust Project. During their time in the program, Fellows receive a monthly stipend, support for additional training, and funding for travel to relevant events. This year, three categories of Fellowship were awarded: * Community Fellowships: 12-month awards for people working to build Rust communities outside of Western Europe and North America to support work such as organizing communities and events and creating content and training materials for their communities. * Project Goal Fellowships 6-month awards (with the potential to extend) for people working on the Rust Project's agreed-upon goals (and sub-goals). * Project Fellowships: 12-month awards for members of the Rust Project Teams and Working Groups to support contributions that serve the goals of the Rust Project Teams and Working Groups Today, the Rust Foundation is thrilled to introduce our 2024 Fellowship cohort! Please join us in welcoming… ## Community Fellowships # ### Promise Reckon (@PromiseReckon) # Promise Reckon is an Embedded system Engineer and a Robotics Instructor at Profix in Canada. He has been a passionate Rustacean since 2022. His focus during the Fellowship year will be promoting Rust adoption in Nigeria through building a vibrant and sustainable Rust Developers Community. This will include arranging meetups and workshops; organising and running Rust training sessions; and collaborating with local technology businesses. ### Kostiantyn Mysnyk (_@Wandalen_) # Kostiantyn is a Rust developer who loves to hammer out solutions with precision and efficiency. Whether tackling code, educational systems, or organizing events, he focuses on creating value, sharing knowledge, and fostering collaboration to support the growth of the community. Passionate about both technical solutions and bringing people together, he aims to make a meaningful impact through his work and leadership in the Rust ecosystem. As part of his Fellowship with the Rust Foundation, he will focus on organizing Rust boot camps and events in Ukraine to promote community engagement and education. Additionally, he will explore opportunities to integrate Rust into higher education curricula, aiming to broaden its adoption and usage among students and educators. ### Mordecai Etukudo (@martcpp) # Mordecai, also known as Mart, is a software developer from Nigeria who has contributed to several open-source projects, including AI (MetaGPT) and others. He is a student at the University of Benin, studying Marine Engineering, focusing on autopilot systems and zero-knowledge proofs (ZKP) in the maritime sector. Mordecai aims to grow Rust within Africa and help drive the adoption of Rust into university systems. ## Project Goal Fellowships # ### Alejandra González (@blyxyas) # I'm a programmer, cat lover, and environmentalist. I'm obsessed with performance because I don't think a user should spend hundreds just to enjoy your apps, and the planet shouldn't suffer, either. I joined the open source collective about four years ago, two and a half of those being part of the Rust project and the Clippy team. I will optimize the linting side of things, the diagnostics that the Rust compiler is famous for, and Clippy, our linter. This includes making algorithms to preview the lints that will emit and execute just those to checking that our L1 cache and type sizes are not monstrously slow. ### **Nick Cameron (**@nrc**)** # Nick is a freelance engineer and consultant. He's been involved with the Rust project since 2014 and is a former core team member. He has worked in many different areas, most recently as part of the async working group. Nick will improve the documentation of async Rust for developers of all experience levels and backgrounds. That should include revitalizing the async book, improving library and reference docs, and perhaps providing other learning material. ### **Predrag Gruevski** (obi1kenobi) # Predrag is an independent software researcher working at the intersection of dev tools, compilers, and databases. He is the author of the cargo-semver-checks linter for semantic versioning in Rust and its underlying Trustfall query engine. Accidental breaking changes in new crate releases are a lose-lose situation: they sap the time and energy of both maintainers and downstream users. The cargo-semver-checks linter can catch many kinds of such breakage and is planned to become part of "cargo publish" itself. Let's resolve the remaining merge blockers so running "cargo update" can become fearless! ### **Manuel Drehwald (**@ZuseZ4**)** # Manuel Drehwald cares about High-Performance Computing, Scientific Computing, and Machine Learning. He works on compiler optimizations and features to support those fields. He is currently a Master's student at the University of Toronto. During the first half of his Fellowship, Manuel will focus on enabling rustc to automatically differentiate Rust code (in the calculus sense). In the second half of his Fellowship, he will work on running Rust functions on GPUs. New LLVM features enable both projects and should support almost arbitrary Rust code, including std and no-std code, basic Rust types, user-defined types, and most dependencies from crates.io. ### **Benno Lossin** (@y86-dev**)** # I learned Rust in a university project in 2021; the expressive type system instantly hooked me. At the start of 2022, I noticed the Rust for Linux effort. After viewing the code, I was shocked to see that Mutexes and other kinds of locks needed to be initialized via _unsafe._ I then solved The Safe Pinned Initialization Problem by creating the _pinned-init_ crate we still use today. Afterward, I continued reviewing code and contributing to various other areas. In 2023, I joined the core team of Rust for Linux, working on making Rust a first citizen language in the Linux kernel. I am primarily working on making Rust more ergonomic in the Linux kernel. I see great potential in adding Field Projections to the Rust language; they come up very often in Rust for Linux. In addition, they allow us to turn currently _unsafe_ APIs into safe ones. I will be working on creating and implementing the RFC. ### **binarycat (**@lolbinarycat**)** # I'm a self-taught programmer with experience in many high- and low-level languages. Most of my previous open source contributions have been to _nixpkgs_. I am working on improving the accessibility, discoverability, and ergonomics of rustdoc search. ## Project Fellowships # ### **Onur Özkan (**@onur-ozkan**)** # I am a self-taught computer scientist specializing in distributed systems, operating systems, and compiler engineering. I am one of the lead maintainers of the Rust Language project, and my responsibilities are mostly related to compiler bootstrapping. I will be working on fixing the download-rustc/ci-rustc issues so we can enable it by default, which will speed up the CI pipelines and shorten compile times for developers. Over the last 5-6 months, I have fixed tens of problems related to it (for ref, you can check all the mentioned PRs from this PR ). After that, I will focus on removing python from bootstrap entrypoint (see https://github.com/rust-lang/rust/issues/94829), improving the LSP/rust-analyzer experience for the library and compiler teams (see https://github.com/rust-lang/rust/pull/120611) and improve the bootstrap experience by any means (e.g., fixing bugs, working with other teams, cutting down the external dependencies, etc.).” ### **Jiayan (**@roife**)** # I'm a graduate student at Nanjing University in China, with an interest in programming languages, compilers, and program analysis. I started learning Rust in 2021, and it has been my primary language for research projects since last year. I've also been contributing to Rust for a year and am a member of the rust-analyzer contributors team. The focus of my Fellowship year will be contributing to rust-analyzer, improving its stability, and refactoring some modules. I also plan to get involved in rustc development and work on driving some interesting proposals forward. ### **Jason Newcomb (**@Jarcho**)** # I've been a maintainer of Clippy since 2022 and have contributed for quite a while longer than that. Most of that time has been spent lowering the false-positive rate and internal refactorings. The fellowship will focus on reducing Clippy's false-positive rate. Notably, this includes interfacing Clippy with the borrow checker and preventing it from making suggestions that violate lifetime rules. ### **Noah Lev Bartell-Mangel (**@camelid**)** # Noah Lev Bartell-Mangel has been involved with Rust since 2020 and is a member of the Rustdoc and Compiler Contributors teams. He also enjoys the research side of programming languages and systems. He is an undergraduate student at UMass Amherst and part of the PLASMA (Programming Languages and Systems at Massachusetts) lab. During his Fellowship, Noah Lev is excited to continue his contributions to Rustdoc, const generics, and the project as a whole. With Rustdoc, he will be working to improve its user interface, performance, and reliability. His focus for const generics will be on making const parameters and arguments more powerful as part of the expanded const generics project goal. He is also developing a research idea related to Rust generics. ### **Boxy (**@BoxyUwU**)** # Boxy is a compiler engineer who has been working on the Rust compiler since early 2021. Their work has largely focused on the type system, particularly const generics. As part of Boxy's fellowship, they will primarily work on stabilizing the _adt_const_params_ feature and reworking the _generic_const_exprs_ feature so that it can be stabilized at some point in the future. They will also help release new versions of Rust as part of the release team and introduce better documentation for how the type system is implemented in the compiler. ### @eth3lbert # @eth3lbert is the newest member of the crates.io team. His work primarily focuses on improving both performance and user experience for crates.io. This includes optimizing database queries and improving rendering times, which makes the website faster for all users. The focus of @eth3lbert’s fellowship year will be implementing pagination for the crate versions page to address the long loading issue for crates with numerous versions; optimizing the search functionality and exploring possibilities to enhance the overall search experience on crates.io; continuing to assist with other Rust-lang projects while contributing to other Rust-related projects whenever possible. ### **Rémy Rakic (**@lqd**)** # Rémy Rakic has been interested in Rust since 2013 and started contributing to the project and ecosystem in 2016. He's a member of the compiler contributors team, the compiler performance and polonius working groups, and was involved in the NLL working group. The focus of Rémy's Fellowship year will be to work on the Polonius 2024H2 project goal, continue working on compiler performance and triage as well as the rustc-perf tool itself, but also PR reviews and regular compiler maintainership activities, like issue triage, bisections and minimizations. ### **Chris Denton (**@ChrisDenton**)** # I first became interested in Rust around the time 1.0 was released, but I didn't start using it in earnest until a couple of years later. In 2019, I began contributing to Rust itself, which led to becoming a member of the Library Contributors, Crate Maintainers, and Rustup teams. During my Fellowship, I'll continue to contribute to and help maintain Rust's standard library, rust-lang crates, and Rustup, with a focus on Windows support. ### **Deadbeef (**@fee1-dead**)** # I've been contributing to the Rust compiler for about three and a half years now, working on implementing language features and pushing them toward stabilization. I've picked up work on const traits since 3 years ago and am continuing my work on it. As part of my fellowship, I will continue to push const traits toward feature completion, aiming for a future where we can use const trait methods on stable. ### **Eric Huss (**@ehuss) # Eric Huss has been involved with the Rust project since 2017. He was drawn to Rust due to its welcoming community and the attraction of a safe systems language that exposed him to new language concepts and can be very productive to use. Eric is currently the lead of the Cargo team (representing the Devtools team on the Leadership Council) and the lead of the lang-docs team. He maintains and works on a variety of projects and infrastructure around the Rust project. The focus of Eric's Fellowship year will be leading the Cargo team and continue to assist with maintenance and new development; continuing participation in other teams, such as the Devtools team and as lead of the Language Documentation team; continuing maintenance of other Rust-lang projects, such as Rust-enhanced, mdBook, cargo-bisect-rustc, rustfix, the RFC repo, and triagebot, continuing assisting other Rust-related projects when possible. _Congratulations to these well-deserving grant recipients!_ ### **Hardship Grants and Event Support Grants Are Available Year-Round** # Hardship Grants are financial awards ranging from $500 to $1,500 made to active Rust Project maintainers facing financial hardship. Event Support Grants are financial awards ranging from $100 to $500 made to support events (both physical and virtual). Both categories of grants are open for applications year-round. You can learn more here. ## **Community Grants Program Support** # If your organization is interested in supporting the Rust language community, donating to the Community Grants Program is a wonderful way to do so. You can inquire about supporting the program by emailing us at grants@rustfoundation.org. We accept donations from organizations for the Community Grants Program in any amount. Additionally, individuals can support the Community Grants Program through our _GitHub Sponsors_ page. _You can learn more about the Community Grants Program_ _here_ _and find the list of 2023 Fellows_ _here_ _._ Congratulations again to our 2024 Fellows!

It turns out misery is a shitty proxy metric.