Awesome Rust Mentors - github

New mentees

Welcome to awesome rust mentors! This project is a curated list of Rustaceans who are ready and willing to act as mentors to new Rustaceans looking to get more involved in the language and/or its community. If that sounds interesting to you, check out the rules and our list of mentors, pick one at random or maybe based off of their bio, and make a friend!

Expectations For Mentees

Mentees are expected to…

• Remember that our mentors are all volunteers, be kind and friendly.
• Inform us if you have any problems with your mentor, such as violating the Code of Conduct (CoC) or being non responsive for a long period of time (approximately > 1 week or so).
• Provide feedback, on this repository or on your mentor, let us know if there are any ways in which we are not serving your needs, this project is all about you after all, help us help you.

Missing Mentor Topics

If there are any topics of interest that you’re looking for that aren’t covered by any of the mentors here just open an issue to let us know! We will do our best to find a mentor for that topic / library / whatever and get them to sign up.

Exercism.io

If you’re looking for someone to mentor solutions for exercism.io just look for mentors that have exercism.io as one of their mentor topics, they will be happy to help.

Code of Conduct

All mentors and mentees are expected to abide by the Rust community code of conduct. Violators will be removed from this list.

New Mentors

To apply, simply open an issue. There is a template set up to help you get started quickly.

Expectations For Mentors

Mentors are expected to…

• Be a friend and guide to your mentee, be their constant cheerleader, and enable them to achieve their goals.
• Provide constructive feedback, pass on things you’ve learned in the course of working in open source.
  • For example, if your mentee is working on something cool encourage them to blog about it, give a talk about it at a local meetup, or both!
• Be responsive, approximately < 1 day for a response is a good goal. Not getting feedback for long periods of time can be discouraging, even if all you can do is say that you’re busy, try to respond promptly.
• Introduce your mentee to other Rustaceans. You aren’t expected to know everything that your mentee might be interested in, but knowing people who can help and facilitating introductions is important.

Mentors are not expected to…

• Be a tutor. Mentors and Tutors are not the same, one advises, the other teaches. You are not expected to teach your mentee the language, only to advise them on how to participate in the Rust community.
• Be a manager. You’re not expected to assign work to your mentees and make sure it gets done, thats a job in its own right. Though if you’re maintaining a project that your mentee is getting involved in maybe this doesn’t apply to you, but that’s more of a maintainer role than a mentor role.
• Be paid. This is a volunteer service. Please do not plan on asking mentees to pay you for your time.

Mentors

See https://rustbeginners.github.io/awesome-rust-mentors/

Ana Hobden (@hoverbear)

• Contact: Email (ana@hoverbear.org, Twitter (@a_hoverbear)
• Spoken Language: English, some German, some Mandarin
• Topics: Distributed systems, software evolution, infrastructure, architecture, chaos testing, workshops, proc-macros

Andre Bogus (@llogiq)

• Pronouns: he/him
• Contact Twitter (@llogiq), reddit (/u/llogiq)
• Spoken Languages: German, English
• Topics: Procedural macros, writing lints, unsafe code, performance, bit twiddling, public speaking

Andreas Fischer (@Vengarioth)

• Pronouns: he/him
• Contact: Twitter (@vengarioth), Email (vengarioth@gmail.com)
• Spoken Languages: German, English
• Topics: Games programming, graphics & rendering, netcode (games), parsers, starting a company in germany

Ben (@gnunicorn)

• Pronouns: he/him
• Contact: Matrix (@ben:matrix.parity.io), Gitter (@gnunicorn), Twitter (@gnunicornBen)
• Spoken Languages: English, German
• Topics: Hacktoberfest, libp2p, substrate, blockchain, decentralization, networking, p2p, cryptogovernance, cli, web, webassembly, data structures, architecture
• Additional Resources: personal website

Bernardo Meurer (@lovesegfault)

• Preferred Pronouns: he/him
• Contact: Twitter (@lovesegfault), Email (bernardo@standard.ai)
• Spoken Languages: English, Portuguese
• Topics: Beginners, intermediates, video, cameras, data transports, distributed systems
• Additional Resources: You can see the slides of the talk I gave this year as a reference on the kind of stuff I work with.

Bhargav Voleti (@bIgBV)

• Pronouns: he/him
• Contact: Twitter (@2093bps)
• Spoken Languages: English, Hindi
• Topics: Beginners, async, distributed systems

Brian Anderson (@brson)

• Pronouns: he/him
• Contact: Telegram (MrBrianAnderson)
• Spoken Languages: English
• Topics: Rust tooling, ecosystem, greenfield projects, big ideas, Chinese community, connecting people. I work on TiKV, and have worked on the compiler, std, rustup, crater and others.
• Additional Resources:
  • Practical Networked Applications in Rust
  • Rust Anthology
  • basic-http-server
  • my blog and other writings
  • Rust Cookbook
  • Rust API Guidelines.

Cyryl Płotnicki (@cyplo)

• Pronouns: he/him/they/them
• Contact: Twitter (@cyplo)
• Spoken Languages: English, Polish
• Topics: mentoring others (so meta!), project management, brand-new-to-rust, structuring tests, property-based tests, fuzzers, distributed systems, I/O
• Additional Resources: I sometimes write about Rust on my blog

Dimitri Sabadie (@phaazon)

• Pronouns: he/him
• Contact: Twitter (@phaazon), IRC (phaazon on Freenode), Email (dimitri.sabadie@gmail.com), Discord (phaazon#0545)
• Spoken Languages: French, English
• Topics: Graphics programming, procedural macros, unsafe bindings & FFI, functional programming & type theory, parsing, type-driven architectures, blockchains, low-level optimizations, cargo tools, writing RFCs.
• Additional Resources:
  • My blog

Eliza Weisman (@hawkw)

• Pronouns: she/her
• Contact: Email (eliza@buoyant.io), Discord (mycoliza#5146)
• Spoken Languages: English
• Topics: Async I/O, networking, concurrent data structures. I’m pretty busy and would generally prefer to provide mentoring for contributions to projects I already contribute to (tokio, tracing, tower, etc).

Erich Gubler (@erichdongubler)

• Pronouns: he/him
• Contact: Email (erichdongubler@gmail.com)
• Spoken Languages: English, Portuguese (BR)
• Topics: Forensics/parsing, workflow (setting up projects, architecture)

Esteban Küber (@estebank)

• Pronouns: he/his
• Contact: Twitter (@ekuber)
• Spoken Languages: English, Spanish
• Topics: Beginners, rustc (parser, diagnostics and in general).

Geoff Shannon (@RadicalZephyr)

• Pronouns: he/him
• Contact: Discord (@radicalzephyr#6728)
• Spoken Languages: English
• Topics: Beginners, intermediates, async/await, macros (by-example and procedural), parsing, tokio

Gray Olson (@termhn)

• Pronouns: she/her
• Contact: Twitter (@fu5ha)
• Spoken Languages: English
• Topics: Beginners, graphics, gamedev
• Additional resources:
  • learn-gfx-hal
  • learn-rendy
  • Introduction to PBR

Jane Lusby (@yaahc)

• Pronouns: she/her
• Contact: Twitter (@yaahc_)
• Spoken Languages: English
• Topics: Beginners, community outreach, cargo, clippy, tracing, CLI, exercism.io, code review
• Aditional Resources: My work tracker, I’m especially happy to mentor any of these issues

Jonathan Turner (@jonathandturner)

• Pronouns: any gender pronoun
• Contact: Email, Discord (jturner#3961), Twitter (@jntrnr)
• Spoken Languages: English
• Topics: Developer experiences, growing projects, Emulation, CLI, and Beginner/Intermediate Rust

Joshua Mir (@joshua-mir)

• Pronouns: he/him
• Contact: Twitter (@jam10o), Gitter Parity technical support chat: (@joshua-mir)
• Spoken Languages: English
• Topics: Beginner Rust, cryptocurrency, blockchain, parity-ethereum, Substrate runtime development
• Additional Resources: Substrate Docs, Parity (Ethereum) Wiki, Substrate Community Resources

Luca Barbato (@lu-zero)

• Contact: IRC (lu_zero on freenode.net), Telegram (lu_zero)
• Spoken Languages: English, Italian
• Topics: Multimedia, cargo, proc-macros, CLI

Lucio Franco (@LucioFranco)

• Pronouns: he/him
• Contact: Twitter (@lucio_d_franco)
• Spoken Languages: English, Italian, French
• Topics: Async io, networking, distributed systems, game dev, compilers

Mara Bos (@m-ou-se)

• Pronouns: she/her
• Contact: Email (rust@m-ou.se), Twitter (@m_ou_se), IRC (M-ou-se on Freenode)
• Spoken Languages: English, Dutch
• Topics: Embedded, CLI, math, proc-macro, Linux, undefined behaviour, FFI, lifetimes, shared memory, memory ordering/atomics/caches

Mike Tang (@daogangtang)

• Pronouns: he/him
• Contact: Twitter (@daogangtang)
• Spoken Languages: Mandarin, English
• Topics: Beginners, community meetup, wasm, web framework, orm, substrate…
• Additional Resources:
  • rust.cc
  • rustforce.net

Nikolai Vazquez (@nvzqz)

• Pronouns: he/him
• Contact: Twitter (@NikolaiVazquez), Email (nikvzqz@gmail.com), Discord (nvzqz#4477)
• Spoken Languages: English, Spanish, German
• Topics: Learning Rust from nothing or experienced newcomers
• Additional Resources: I maintain Static Assertions, so I’d be happy to teach people how it works

Oli (@oli-obk)

• Pronouns: he/him
• Contact: Zulip (@oli), Github (@oli-obk), Discord (oli#1337)
• Spoken Languages: German, English
• Topics: Miri, const eval, error messages and other diagnostics, optimizations, MIR

Phil Krones (@flip1995)

• Pronouns: he/him
• Contact: GitHub (@flip1995), E-Mail (hello@philkrones.com), Discord (flip1995#2683; not that active there)
• Spoken Languages: German, English
• Topics: Beginners, Clippy, Lints, Diagnostics

Ravi (@wafflespeanut)

• Pronouns: he/him
• Contact: Twitter (@wafflespeanut)
• Spoken Languages: Tamil, English
• Topics: Beginners, CLI, web, coding practices, clean + maintainable code.
• Additional Resources: I’m actively working on paperclip, a WIP OpenAPI tooling library. I’d love to give a hand if anyone’s interested!

Robert Winslow (@rw)

• Pronouns: he/him
• Contact: Twitter (@robert_winslow)
• Spoken Languages: English
• Topics: Distributed systems, low-latency, testing, formal methods, Bayesian statistics, machine learning, deep learning, serialization. async/await, FlatBuffers, testing, minimizing heap allocations, lifetimes, traits, borrow-checker, API design
• Additional Resources: Video of a talk I presented at Mozilla HQ on FlatBuffers in Rust.

Roman Proskuryakov (@kpp)

• Contact: Github (@kpp), Email (r.proskuryakoff@gmail.com), Telegram (gitkpp),
• Spoken Languages: English, Russian
• Topics: Beginner/Intermediate Rust, async, futures, CI

Shady Khalifa (@shekohex)

• Pronouns: he/him
• Contact: Twitter (@shekohex)
• Spoken Languages: Arabic, English
• Topics: Networking, FFI, CLI, parsers, development tools, web (server-side)

Søren Mortensen (@nerosnm)

• Pronouns: he/him
• Contact: Twitter (@nerosnm), Email (soren@neros.dev)
• Spoken Languages: English
• Topics: Beginners/the basics, developer tools, CLI, Rust–Swift/Objective-C interop

William (@Firstyear)

• Pronouns: he/him/they/them
• Contact: Twitter (@Erstejahre), Email (william@blackhats.net.au)
• Spoken Languages: English
• Topics: Code review, beginners, C-FFI, concurrency, data structures, security, identity management aka authentication
• Additional Resources:
  • Programming lessons and methods
  • LDAP guide
  • Using rust generics to enforce db record state
  • CPU atomics and ordering explained

Zack M. Davis (@zackmdavis)

• Contact: Twitter (@zackmdavis), email (code@zackmdavis.net), Discord (zackmdavis#3944)
• Spoken Languages: English
• Topics: Language basics, rustc development (especially diagnostics)

Additional Resources

• The Rust Book
• Rust by Example
• Rust Language Cheat Sheet
• rust-learning
• awesome-rust