Awesome

Bevy RFCs

Thank you for contributing to Bevy! If you've been asked to make an RFC, it's because your contribution is significant enough that it warrants careful thought from the Bevy community.

What is an RFC?

RFCs (request for comments) provide a way for Bevy contributors to propose designs for specific features in a structured way. Creating a new RFC starts a collaborative process where the Bevy community (and @cart, the Bevy project lead) can review your design and suggest changes. If an RFC is accepted, this indicates that it is in line with our vision for Bevy's future. Bevy contributors can implement accepted RFCs comforted by the knowledge that the design has already been "approved".

RFCs are for large features, breaking into new design areas, major breaking changes, and significant changes to Bevy App development.

• Most changes don't need RFCs: The majority of Bevy changes (bug fixes, small tweaks, and iterative improvements) should not go through the RFC process. Just use the normal contributing process in the main Bevy repo.
• RFCs are not feature requests: RFCs are for developers who already have a specific design in mind (including technical details) and want feedback on it. If you want to request a feature, please create an issue in the main Bevy repo.
• RFCs should be scoped: Try to avoid creating RFCs for huge design spaces that span many features. Try to pick a specific feature slice and describe it in as much detail as possible. Feel free to create multiple RFCs if you need multiple features.
• RFCs should avoid ambiguity: Two developers implementing the same RFC should come up with nearly identical implementations.
• RFCs should be "implementable": Merged RFCs should only depend on features from other merged RFCs and existing Bevy features. It is ok to create multiple dependent RFCs, but they should either be merged at the same time or have a clear merge order that ensures the "implementable" rule is respected.
• Don't create RFCs before you have a design: If you want to explore design spaces with the Bevy community, consider finding or creating a Github Discussion in the main Bevy repo. If at any point during the discussion you discover a design you believe in enough to bring to completion, create an RFC. You don't need to have all of the details sorted out ahead of time, but Draft RFCs (RFCs created as "Draft PRs" on Github) should have more than just a few sentences describing the feature. An initial Draft RFC should at a bare minimum describe the design and goals from a high level, draw out a first draft of the public apis, and prescribe a good portion of the technical details. RFCs are a platform for community members to share detailed technical designs for new Bevy features, not for people to open discussions with the intent to eventually find a design.

If you are uncertain if you should create an RFC for your change, don't hesitate to ask us in the #dev-general channel in the official Bevy Discord.

Why create an RFC?

RFCs are intended to be a tool for collaboration, not a burden for contributors.

RFCs protect Bevy contributors from wasting time implementing features that never had a chance of getting merged. This could be due to things like misalignment with project vision, missing a key requirement, forgetting a technical detail, or failing to consider alternative designs.

RFCs also serve as a form of documentation. They describe how a feature should work and why it should work that way. The accompanying pull request(s) record how the Bevy community came to that conclusion.

They don't need to be perfect, complete, or even very good when you submit them. The goal is to move the discussion into a format where we can give each part of the design the focus it deserves in a collaborative fashion.

The Process

1. Fork this repository and create a new branch for your new RFC.
2. Copy template.md into the rfcs folder and rename it to my_feature.md, where my_feature is a unique identifier for your feature.
3. Fill out the RFC template with your vision for my_feature.
4. Create a pull request in this repo. The first comment should include:
   1. A one-sentence description of what the RFC is about.
   2. A link to the "rendered" form of the my_feature.md file. To do so, link directly to the file on your own branch, so then the link stays up to date as the file's contents changes. See #1 for an example of what this looks like.
5. With your PR created, note the PR number assigned to your RFC. Rename your file to PR_NUMBER-my_feature.md (ex: 7-visual_scripting.md), and make sure to update the link to your rendered file.
6. Help us discuss and refine the RFC. Bevy contributors and @cart (Bevy's project lead) will leave comments and suggestions. Ideally at some point relative consensus will be reached. Your RFC is "accepted" if your pull request is merged. If your RFC is accepted, move on to step 7. A closed RFC indicates that the design cannot be accepted in its current form.
7. Bevy contributors are now free to implement (or resume implementing) the RFC in a PR in the main Bevy repo, and an associated tracking issue is created in that repo. You are not required to provide an implementation for your RFC, nor are you entitled to be the one that implements the RFC.

Collaborating

First, make sure you always abide by the Bevy Code of Conduct when participating in the RFC process.

Additionally, here are some suggestions to help make collaborating on RFCs easier:

• The insert a suggestion feature of GitHub is extremely convenient for making and accepting quick changes.
• If you want to make significant changes to someone else's RFC, consider creating a pull request in their fork/branch. This gives them a chance to review the changes. If they merge them, your commits will show up in the original RFC PR (and they will retain your authorship).
• Try to have design discussions inside the RFC PR. If any significant discussion happens in other repositories or communities, leave a comment with a link to it in the RFC PR (ideally with a summary of the discussion).