# Compiler Team Ambitions for 2022 @pnkfelix, @wesleywiser --- ## Background - In past years, we've often oscillated between planned and very unplanned team goals. <!-- Planned: Rust 2017 impl period --> - Lots of great progress was made in 2021 but it was largely ad-hoc. --- ## Beginnings - In 2022, we wanted to be more organized :) - Goals - Find out what contributors are working on <!-- There are a lot of people in compiler-team + contributors and they are self motivated and it's not always clear to us what they might want to work on. --> - See if there are common themes between sets of contributors <!-- We were hoping that there would be overlap between what people wanted to do and we could set up working groups, project groups or even just let people know others were interested in the same thing --> - Give the community an idea of what we're working on <!-- The release team does a great job showing off what's in each release but it's not always obvious to the community what might be coming in the short-medium term --> - Highlight ways the community can help <!-- Even as a large team, we want to continue growing and enabling new people to contribute to the compiler. We also heard from contributors that were interested in mentoring people for specific roles. --> - Showcase the growth & maturity of the project <!-- As I said above, we have a lot of consistent contributors and showcasing how many people come together to work on Rust is a huge sign of maturity for the project --> --- ## Process - Free-form thread on #t-compiler to "spitball areas for a 2022 roadmap" - Felix & Wesley wrote up separate idea lists based on the feedback from the thread - Consolidated lists into one document <!-- One of the main things that emerged here was a list of things we think we can accomplish (we called these inititives) and a list of things we hope we could achieve (we called these aspirations) --> - Engaged Compiler Team & Contributors <!-- Emails to the compiler team, Friday design meeting, PMs etc --> - Inside Rust blog post goes up tomorrow! --- ## Lessons learned - It always takes longer than you think it does. - Setting deadlines was helpful but also important to realize they did not have to be immovable. - Just having team members talk about what they hoped/planned to work on was **very** valuable. <!-- Debugging in particular was one area we weren't sure we had enough people interested in working in to start a working group and it actually turned out that we had quite a lot of interest in this area. --> --- ## Sneak peak - Three main themes we identified for 2022: - Fulfill Rust's Promise (🦀) <!-- identifying the gaps between expectation and reality for each of our three pillars: [Performance, Reliability, and Productivity][rust-lang], and then addressing those gaps --> - Developer Delight (👩‍💻) <!-- We want answers to the question, "what would delight Rust developers?" This is not about meeting their expectations: It's about *surpassing* them. --> - Contributor Workflow (🛠️) <!-- improving the Compiler Contributor Workflow means technology enhancements that benefit people maintaining and extending the Rust compiler itself. --> ---