The Bevy community! If you want to see yourself here, submit
a pull request!
The Bevy Organization#
The Bevy Organization is the group of people responsible for stewarding the Bevy project. It handles things like choosing project direction, merging pull requests, managing bugs / issues / feature requests, running the Bevy website, controlling access to secrets, defining and enforcing best practices, etc.
Anyone with a history of contributing to Bevy can join the Bevy Organization. Reach out to the Project Lead if you would like to join!
Roles#
Project Leads
have the final call on all design and code changes within Bevy. They
are responsible for representing the project publicly and they choose how the project is organized.
Maintainers
have merge rights in Bevy repos. They assess the scope of pull
requests and whether they fit into the Bevy project's vision. They also serve as representatives of the Bevy
project.
SMEs
(Subject Matter Experts) have proven themselves to be experts in a
given development area. They help guide Bevy's direction in their area and they are great people to reach out
to if you have questions about a given area.
Other members, without a special role, are part of the GitHub
organization. They have the power to manage GitHub issues and pull requests.
Members#
Carter Anderson
Project Lead
Maintainer
Full-time lead developer, project manager, and original creator of Bevy. Focused on building out core engine systems, guiding project direction, and managing the community.
Alice Cecile
Maintainer
SME-Docs
SME-ECS
SME-Input
Technical project manager, mad scientist, and documentation lead. Loves tinkering with ECS features.
James Liu
Maintainer
SME-Animation
SME-ECS
Performance by default. A slow engine is an unused engine. Focused on animation, networking, and general engine performance and UX.
François Mockers
Maintainer
SME-Animation
SME-Input
SME-Mobile
Helping everything run smoothly, and having fun with Bevy!
Gino Valente
SME-Reflection
React Native developer during the day, Bevy contributor at night. Focused mainly on Bevy's reflection system.
Kurt Kühnert
German master's student specializing in computer graphics. Author of bevy_terrain. Focused on improving the ergonomics and documentation of Bevy's renderer.
Joona Aalto
Maintainer of the Avian physics engine for Bevy. Working on shiny simulations and math, breathing life into creations.
Jan Hohenheim
Responsible for the Rust GameDev newsletter. Creator of a few Bevy tools like the Foxtrot template and Yarn Spinner for Rust. Writes unpublished games.
Nicola Papale
Making games at devildahu. Author of bevy-ui-navigation, cuicui and many other bevy-related crates. Incidentally contributes to bevy. Touches reflection, rendering, ui and ecs.
Nile
Formerly active member of the community, and still the uncontested owner of the highest message count on the bevy discord. I will one day return to the forefront of mad science! 🧪
Ida "Iyes"
Likes to teach and explain things. Talks a lot (sometimes with her cat). Makes games, sometimes music and other creative things. Community is Love. Ice is Win. 👀
Thierry Berger
Helping one project after the other, fixing papercuts along the way. Tell me about yours!
Aceeri
harudagondi
Nathan Stocks
Indie Game Dev, Rust Instructor, Rusty Engine creator. Senior Software Engineer at GitHub. Family, Food, Rust, Python, Open Source, Maple Trees.
Community Members#
People in the Bevy community who are not part of the organization.
Anyone can add themselves here! Submit a pull request!
Paul Hansen
Slayer of Windows bugs. Currently working on an unannounced 2d space RPG using Bevy in my free time. Happy to help where I can.
Jos Feenstra
Developer of 3D things. Author of `hedron`: procedural modelling for bevy. Feel free to reach out!
Schell Carl Scivally
Kat Marchán
Maintainer for Big Brain, a Utility AI library for Bevy, as well as KDL, an alternative document format.
Phaestus Fox or Phox for short
I am a small youtuber, attempted game dev and avid doc reader. I'm happy to help wherever and whenever I can.
Crispy
