Rust Contributor Program
Doc Jones
Rustc Reading Club
TL;DR: Phase I Retrospective
- Need dedicated tracks
- Indefinite commitment considered harmful
- Learn tooling for contributor aspirants
How we got here
- May 18, 2021
- The writing club
- Chaos at the first session
- Phase I Retrospective
The future we want
"I want to learn to code in rustc"
"Apply now!"
Join the spring cohort of RustContributor::new
RustContributor::new
- 🐛 Get assigned a bug of your very own!
- 💬 Dedicated stream for you and your cohort!
- ✋ Office hours where you can get answers!
- 💰 Fix a bug or your money back!
Gonzo meets others in the cohort and they get to work.
Team members hold regular
office hours to answer questions.
Finally, the big day! Their PRs are merged.
Pomp and Circumstance plays.
I know it's grover, not gonzo, sue me.
But Gonzo wants MORE
Cohort is fixing smaller bugs but they want MORE.
RustContributor::grow
Gonzo joins RustContributor::grow, in which team members explain parts of the code.
This month is @BigFish explaining the trait system.
Once a week for the next 8 weeks, Gonza joins @BigFish and learns how a simple program is checked.
After a while, Gonzo has learned enough to become a full team member
What did we just see?
Proposed program with two tracks:
RustContributor::new– twice per yearRustContributor::grow– every 8 weeks
RustContributor::new
- Three team members commit for two months
- First month:
- find bugs that would be suitable and "hold" them, take applications
- Second month:
- create dedicated Zulip stream for cohort
- mentors available at a fixed time window
RustContributor::grow
- One expert commits for 8 sessions or so
- pick some input programs and a part of the compiler
- advertise expected background knowledge and skill level
- walk through the example using pernosco
- or walk through the code
What does it take to do this?
- One program manager/organizer to recruit people
- Twice a year:
- Three mentors to collect bugs, hold office hours
- Every 8 weeks:
- One mentor to pick some examples and walk through code
- Instructors leading RustContributor::grow
- Badges - Certified Rust Instructor
Takeaways
- Let's design an active education program
- Target new contributors with twice yearly cohorts
- Target all contributors with regular walkthroughs
- Commit as a team to bringing new people in
Rust Contributor Program Doc Jones
{"metaMigratedAt":"2023-06-16T23:11:21.871Z","metaMigratedFrom":"YAML","title":"Rust Contributor Program","breaks":true,"contributors":"[{\"id\":\"27d8f2ac-a5dc-4ebe-8c31-cc45bcd8447e\",\"add\":4671,\"del\":1355},{\"id\":\"a796be9e-9a1d-425f-812f-58de05e425f9\",\"add\":337,\"del\":54}]"}