{"id":524428,"url":"https://emberjs.github.io/rfcs","last_synced_at":"2025-08-13T19:32:05.738Z","repository":{"id":19422073,"uuid":"22664562","full_name":"emberjs/rfcs","owner":"emberjs","description":"RFCs for changes to Ember","archived":false,"fork":false,"pushed_at":"2024-10-28T14:25:53.000Z","size":23464,"stargazers_count":790,"open_issues_count":103,"forks_count":408,"subscribers_count":139,"default_branch":"master","last_synced_at":"2024-10-29T15:44:46.404Z","etag":null,"topics":["ember","ember-cli","emberjs","rfc","rfc-process","rfcs"],"latest_commit_sha":null,"homepage":"https://rfcs.emberjs.com/","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"Shopify/scripts-public","license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/emberjs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null},"funding":{"github":"emberjs","open_collective":"emberjs"}},"created_at":"2014-08-06T00:49:22.000Z","updated_at":"2024-10-28T14:24:29.000Z","dependencies_parsed_at":"2023-09-24T12:28:48.390Z","dependency_job_id":"3456a19f-a5bc-4fba-a848-2c5e6a29c80e","html_url":"https://github.com/emberjs/rfcs","commit_stats":{"total_commits":1930,"total_committers":154,"mean_commits":"12.532467532467532","dds":0.9129533678756476,"last_synced_commit":"519e97a4cc190d55118c8f1fd6aa06890520ccde"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/emberjs%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/emberjs%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/emberjs%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/emberjs%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/emberjs","download_url":"https://codeload.github.com/emberjs/rfcs/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":229008241,"owners_count":18005476,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ember","ember-cli","emberjs","rfc","rfc-process","rfcs"],"created_at":"2024-01-09T09:07:24.537Z","updated_at":"2025-08-13T19:32:05.713Z","avatar_url":"https://github.com/emberjs.png","language":null,"readme":"# Ember RFCs\n\nThe RFC (\"request for comments\") process is how Ember designs and\nachieves consensus on \"substantial\" proposed changes.\n\nMany changes, including bug fixes and documentation improvements can be\nimplemented and reviewed via the normal GitHub pull request workflow.\n\nSome changes though are \"substantial\", and we ask that these be put\nthrough a bit of a design process and produce a consensus among the Ember\ncore teams.\n\nThe process is intended to provide a consistent and controlled path for new\nfeatures and changes to enter the framework. RFCs can be created by any member\nof the community.\n\n---\n## Quick links for Pull Requests for proposed and advancing RFCs\n[Quick links for Pull Requests for proposed and advancing RFCs]: #quick-links-for-pull-requests-for-proposed-and-advancing-rfcs\n\n- [Proposed RFCs](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3AS-Proposed)\n- [Exploring RFCs](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3AS-Exploring)\n\n- [PRs to advance an RFC to Ready for Release Stage](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%22S-Ready+for+Release%22)\n- [PRs to advance an RFC to Released Stage](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3AS-Released)\n- [PRs to advance an RFC to Recommended Stage](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3AS-Recommended)\n\n- [RFCs in Final Comment Period for any Stage](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%22Final+Comment+Period%22)\n- [RFCs in FCP to Close](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%22FCP+to+close%22)\n\n\n**[RFC Website](https://rfcs.emberjs.com)**\n\nThis site shows the current state and text of all RFCs in Accepted or later stages.\n\n---\n\n## Table of Contents\n[Table of Contents]: #table-of-contents\n\n- [Introduction](#ember-rfcs)\n- [Quick links](#quick-links-for-pull-requests-for-proposed-and-advancing-rfcs)\n- [Table of Contents]\n- [How it works](#how-it-works)\n- [Stages]\n  - [Proposed]\n  - [Exploring]\n  - [Accepted]\n  - [Ready for Release]\n  - [Released]\n  - [Recommended]\n- [Following RFC Progress](#following-rfc-progress)\n- [Commenting on an RFC](#commenting-on-an-rfc)\n- [Creating an RFC](#creating-an-rfc)\n  - [When you need to follow this process]\n  - [Gathering feedback before submitting an RFC]\n  - [The Process]\n    - [How to create a new RFC]\n    - [Finding a champion]\n- [Implementing an RFC]\n- [Editing merged RFCs]\n- [Reference]\n  - [Relevant Teams]\n  - [Final Comment Periods (FCP)](#final-comment-periods-fcp)\n    - [FCP to close]\n- [For Core Team Members](#for-core-team-members)\n\n\n## How it works\n[How it works]: #how-it-works\n\n### New Proposals\n\nNew proposals for changes are submitted as pull requests to this repo using one\nof the RFC templates, depending on what the RFC is proposing. The newly opened RFC\nis in the [Proposed] stage. The RFC is then reviewed and commented upon by\ncore team members and the community. The core teams may move the RFC to the\n[Exploring] stage via a label if they believe the RFC is worth exploring further.\nFrom there, with refinement, community consensus, and agreement by the relevant\ncore teams, the RFC enters a [Final Comment Period](#final-comment-periods-fcp) (FCP).\nIf that period is successful, with no new unaddressed concerns raised, the RFC\nis merged and is now in the [Accepted] stage.\n\nAn RFC that does not achieve consensus to be accepted may enter a\n[Final Comment Period](#final-comment-periods-fcp) to move the RFC to the\n[Closed] stage.\n\n### Merged Proposals\n\nOnce the RFC is accepted, a draft pull request is automatically opened to advance\nthe RFC to the [Ready for Release] stage. This pull request has a template that outlines\nwhat is necessary to merge the RFC into this stage. This pull request is where the\ncommunity can track the progress of the implementation of the RFC. Once the criteria\nto move to [Ready for Release] are met, including commitment of the team to the\nfeature's stability, the PR to advance may be merged after a [Final Comment Period](#final-comment-periods-fcp).\nEach core team needs to review the PR and approve it before the end of the FCP.\nIf the FCP is successful, the RFC is merged and becomes [Ready for Release].\n\nOnce the RFC is merged as [Ready for Release], a pull request is automatically opened\nto advance the RFC to the [Released] stage. This pull request has a template that outlines\nwhat is necessary to merge the RFC into this stage. The pull request is merged\nwhen those requirements are met and the relevant team has consensus that the RFC\nhas been [Released]. No FCP is required for this stage.\n\nOnce the RFC is merged as [Released], a pull request is automatically opened to\nadvance the RFC to the [Recommended] stage. This pull request has a template that outlines\nwhat is necessary to merge the RFC into this stage and can be used for community\ncoordination. This advancement requires a\n[Final Comment Period](#final-comment-periods-fcp) to merge.\n\nAt this point, the RFC is [Recommended] and complete.\n\nRFCs that have been merged to the repo can also move to the [Discontinued] stage at\nany point via a pull request. This is done when the RFC is no longer relevant or\nthe feature is no longer supported.\n\nRead more about the RFC [Stages].\n\n## Stages\n[Stages]: #stages\n\nHere are all the stages that an RFC can be in:\n\n| Stage| Description| Requires FCP to enter? |\n| -----| -----------|----- |\n| [0 - Proposed](#Proposed) | A proposal for a change to Ember or its processes that is offered for community and team evaluation. | no |\n| [1 - Exploring](#Exploring) | An RFC deemed worth pursuing but in need of refinement. | no |\n| [2 - Accepted](#Accepted) | A fully specified RFC. Waiting for or in the process of implementation. | yes |\n| [3 - Ready for Release](#Ready-for-Release) | The implementation of the RFC is complete, including learning materials. | yes |\n| [4 - Released](#Released) | The work is published. If it is codebase-related work, it is in a stable version of the relevant package(s). | no |\n| [5 - Recommended](#Recommended) | The feature/resource is recommended for general use. | yes |\n\nThere are two additional statuses for RFCs that will not move forward:\n\n- **[Discontinued](#Discontinued)** - a previously [Accepted] RFC that is either in conflict with Ember's evolving programming model or is superseded by another active RFC.\n- **[Closed](#Closed)** - Proposed RFCs that will not be moved into the next stage.\n\n### Proposed\n[Proposed]: #proposed\n\nProposed RFCs are opened as pull requests to the RFC repository. Anybody may\ncreate an RFC. The format should follow the templates in the RFC repository.\n\nAn RFC's number is the number of it's original proposal PR.\n\nFrom \"Proposed\" an RFC may move to [Exploring],\nor [Closed] stages.\nTo move to [Closed] an FCP is required as in the existing process.\nA \"Proposed\" RFC may be moved to \"Exploring\" by consensus of the relevant\nteam(s) without an FCP. See [Exploring].\n\n### Exploring\n[Exploring]: #exploring\n\nAn Exploring RFC is one the Ember team believes should be pursued, but the RFC\nmay still need some more work, discussion, answers to open questions,\nand/or a champion before it can move to the next stage.\n\nAn RFC is moved into Exploring with consensus of the relevant teams. The\nrelevant team expects to spend time helping to refine the proposal. The\nRFC remains a PR and will have an `Exploring` label applied.\n\nAn Exploring RFC that is successfully completed can move to [Accepted]\nwith an FCP is required as in the existing process. It may also be moved to\n[Closed] with an FCP.\n\n### Accepted\n[Accepted]: #accepted\n\nAn RFC that has been \"accepted\" has complete prose and has successfully passed\nthrough an \"FCP to Accept\" period in which the community has weighed in and\nconsensus has been achieved on the direction. The relevant teams believe that\nthe proposal is well-specified and ready for implementation. The RFC has a\nchampion within one of the relevant teams.\n\nIf there are unanswered questions, we have outlined them and expect that they\nwill be answered before [Ready for Release].\n\nWhen an RFC is merged and moved to \"Accepted\", a new PR will be opened to move\nit to [Ready for Release]. This PR should be used to track\nthe implementation progress and gain consensus to move to the next stage.\n\n### Ready for Release\n[Ready for Release]: #ready-for-release\n\nThe implementation is complete according to plan outlined in the RFC, and is in\nharmony with any changes in Ember that have occurred since the RFC was first\nwritten. This includes any necessary learning materials. At this stage, features\nor deprecations may be available for use behind a feature flag, or with an\noptional package, etc. The team reviews the work to determine when it can be\nincluded in a stable release. For codebase changes, there are no open questions\nthat are anticipated to require breaking changes; the Ember team is ready to\ncommit to the stability of any interfaces exposed by the current implementation\nof the feature. Today, this would be the \"go/no-go\" decision by a particular\nteam.\n\nThis stage should include a list of criteria for determining when the proposal\ncan be considered [Recommended] after being [Released].\n\nA PR is opened on the repo (see [Accepted]) to move an accepted RFC\ninto this stage. An FCP is required to move into this stage.\n\nEach Ember core team will be requested as a reviewer on the PR to move into this\nstage. A representative of each team adds a review. If a team does not respond\nto the request, and after the conclusion of the FCP, it is assumed that the\nrelease may proceed.\n\n### Released\n[Released]: #released\n\nThe work is published. If it is codebase-related work, it is in a stable version\nof the relevant package(s). If there are any critical deviations from the\noriginal RFC, they are briefly noted at the top of the RFC.\n\nIf the work for an RFC is spread across multiple releases of Ember or other packages,\nthe RFC is considered to be in the Released stage when all features are available in\nstable releases and those packages and versions are noted in the RFC frontmatter.\n\nEmber's RFC process can be used for process and work plans that are not about code.\nSome examples include Roadmap RFCs, changes to the RFC process itself, and\nchanges to learning resources.\nWhen such an RFC is a candidate for Released, the work should be shipped as described,\nand the result should presented to the team with the intent of gathering feedback\nabout whether anything is missing. If there is agreement that the work is complete,\nthe RFC may be marked \"Released\" and a date is provided instead of a version.\n\nAn RFC is moved into \"Released\" when the above is verified by consensus of the\nrelevant team(s) via a PR to update the stage.\n\n### Recommended\n[Recommended]: #recommended\n\nThe \"Recommended\" stage is the final milestone for an RFC. It provides a signal\nto the wider community to indicate that a feature has been put through its\necosystem paces and is ready to use.\n\nThe \"Recommended\" stage is most important for suites of features that are designed\nas a number of separate RFCs. It allows the Ember maintainers to stabilize individual\nfeatures once they are technically feature complete, an important goal for maintaining\ntechnical velocity.\n\nTo reach the \"Recommended\" stage, the following should be true:\n\n- If appropriate, the feature is integrated into the tutorial and the guides prose.\n  API documentation is polished and updates are carried through to other areas of\n  API docs that may not directly pertain to the feature.\n- If the proposal replaces an existing feature, the addon ecosystem has largely\n  updated to work with both old and new features.\n- If the proposal updates or replaces an existing feature, high-quality codemods are\n  available\n- If needed, Ember debugging tools as well as popular IDE support have been\n  updated to support the feature.\n- If the feature is part of a suite of features that were designed to work together\n  for best ergonomics, the other features are also ready to be \"Recommended\".\n- Any criteria for \"Recommended\" for this proposal that were established in the\n  [Ready For Release] stage have been met.\n\nAn RFC is moved into \"Recommended\" via PR to update the stage. An FCP is required\nto enter this stage. Multiple RFCs may be moved as a batch into \"Recommended\" with\nthe same PR.\n\n### Closed\n[Closed]: #closed\n\nA [Proposed] or [Exploring] RFC may be closed after an FCP period. This is the same\nas the existing process. A closed RFC is discontinued.\n\n### Discontinued\n[Discontinued]: #discontinued\n\nA previously [Accepted] RFC may be discontinued at any point. The RFC\nmay be superseded, out-of-date, or no longer consistent with the direction of\nEmber.\n\n## Following RFC Progress\n[Following RFC Progress]: #following-rfc-progress\n\nFollowing the RFC repository is the best way to keep up with the proposed\nchanges to Ember and with the implementation of accepted changes.\n\nWatching the repository will alert you to any newly created RFCs. Setting up\nnotifications on a particular pull request will help you follow the progress of\nthat RFC.\n\nRFCs in [Final Comment Periods](#final-comment-periods-fcp) are labeled with\n[Final Comment Period](https://github.com/emberjs/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%22Final+Comment+Period%22)\nand are announced in `#news-and-announcements` on [Ember Discord](https://discord.gg/emberjs) and\non the [Ember twitter account](https://twitter.com/emberjs).\n\n[Quick links](#quick-links-for-pull-requests-for-proposed-and-advancing-rfcs)\nare provided at the top of the README to help you review what you are interested in.\n\n\n## Commenting on an RFC\n[Commenting on an RFC]: #commenting-on-an-rfc\n\nComments are the very heart of the RFC process. Comments are the primary way community\nmembers and core team members can provide feedback and collaborate on the design\nof a feature.\n\nComments should also be used to ensure the author has completed the RFC template\nand addressed implications of the feature across the Ember project, including\ndocumentation, addons, and tooling.\n\nComments should be constructive and respectful, following our\n[Community Guidelines](http://emberjs.com/guidelines/).\n\n## Creating an RFC\n[Creating an RFC]: #creating-an-rfc\n\n### When you need to follow this process\n[When you need to follow this process]: #when-you-need-to-follow-this-process\n\nYou need to follow this process if you intend to make \"substantial\"\nchanges to Ember, Ember Data, Ember CLI, their documentation, or any other\nprojects under the purview of the [Ember core teams](https://emberjs.com/team/).\nWhat constitutes a \"substantial\" change is evolving based on community norms,\nbut may include the following:\n\n   - A new feature that creates new API surface area, and would\n     require a [feature flag] if introduced.\n   - The removal of features that already shipped as part of the release\n     channel.\n   - The introduction of new idiomatic usage or conventions, even if they\n     do not include code changes to Ember itself.\n\nSome changes do not require an RFC:\n\n   - Rephrasing, reorganizing or refactoring\n   - Addition or removal of warnings\n   - Additions that strictly improve objective, numerical quality\ncriteria (speedup, better browser support)\n   - Additions only likely to be _noticed by_ other implementors-of-Ember,\ninvisible to users-of-Ember.\n\nIf you submit a pull request to implement a new feature without going\nthrough the RFC process, it may be closed with a polite request to\nsubmit an RFC first.\n\n### Gathering feedback before submitting an RFC\n[Gathering feedback before submitting an RFC]: #gathering-feedback-before-submitting-an-rfc\n\nIt's often helpful to get feedback on your concept before diving into the\nlevel of API design detail required for an RFC. **You may open an\nissue on this repo to start a high-level discussion**, with the goal of\neventually formulating an RFC pull request with the specific implementation\n design. We also **_highly recommend_** sharing drafts of RFCs in `#dev-rfc` on\nthe [Ember Discord](https://discord.gg/emberjs) for early feedback.\n\n### The Process\n[The Process]: #the-process\n\nThe process for a successful RFC involves several [Stages] that take\nthe proposed change all the way from proposal to implemented and widely adopted.\nA newly opened RFC is in the first stage, appropriately named, [Proposed].\n\n#### How to create a new RFC\n[How to create a new RFC]: #how-to-create-a-new-rfc\n\n* Fork the RFC repo http://github.com/emberjs/rfcs\n* Copy the appropriate template. For most RFCs, this is `0000-template.md`,\nfor deprecation RFCs it is `deprecation-template.md`.\nCopy the template file to `text/0000-my-feature.md`, where\n'my-feature' is descriptive. Don't assign an RFC number yet.\n* Fill in the RFC. Put care into the details: **RFCs that do not\npresent convincing motivation, demonstrate understanding of the\nimpact of the design, or are disingenuous about the drawbacks or\nalternatives tend to be poorly-received**.\n* Fill in the relevant core teams. Use the [table below](#relevant-teams) to map from projects to\nteams.\n* Submit a pull request. As a pull request the RFC will receive design\nfeedback from the larger community, and the author should be prepared\nto revise it in response. The RFC is now in the [Proposed] stage.\n* Find a champion on the relevant core team. The champion is responsible for\nshepherding the RFC through the RFC process and representing it in core team\nmeetings.\n* Update the pull request to add the number of the PR to the filename and\nadd a link to the PR in the header of the RFC.\n* Build consensus and integrate feedback. RFCs that have broad support\nare much more likely to make progress than those that don't receive any\ncomments.\n* From here, the RFC moves to the [Exploring] stage or [Closed] in the process\nexplained in [Stages].\n\n### Finding a champion\n[Finding a Champion]: #finding-a-champion\n\nThe RFC Process requires finding a champion from the relevant core teams. The\nchampion is responsible for representing the RFC in team meetings, and for\nshepherding its progress. [Read more about the Champion's job](#champion-responsibilities)\n\n- *Find one via Discord.*\n  The `dev-rfc` channel on the [Ember Discord](https://discord.gg/emberjs) is\n  reserved for the discussion of RFCs. We highly recommend circulating early drafts of\n  your RFC in this channel to both receive early feedback and to find a champion.\n\n- *Ask for a champion via an issue, or in the RFC itself.*\n  We monitor the RFC repository. We will circulate requests for champions, but highly\n  recommend discussing the RFC in Discord.\n\n## Implementing an RFC\n[Implementing an RFC]: #implementing-an-rfc\n\nCoordination and tracking of implementation of an RFC is done primarily on the\npull request to advance the RFC to the [Ready for Release] stage.\n\nThe author of an RFC is not obligated to implement it. Of course, the\nRFC author (like any other developer) is welcome to work on the implementation.\n\nIf you are interested in working on the implementation for an [Accepted]\nRFC, but cannot determine if someone else is already working on it,\nplease ask (e.g. by leaving a comment on the pull request to advance the RFC to\nthe [Ready for Release] stage).\n\n### Editing merged RFCs\n[Editing merged RFCs]: #editing-merged-rfcs\n\nA merged RFC may be edited via a Pull Request process. Edits may include things like:\n\n- Updating the stage\n- An optional note at the top that summarizes minor adjustments to the RFC\ndesign, at the time that the RFC's work became available for general use. This\nnote can be very brief, and link out to other resources like a blog post. For\nexample, an update might simply say \"See `\u003cblog post\u003e` for more information\nabout this feature.\" This note is not intended to be updated across time.\n- Updating any part of the RFC prose, in order to keep a written record of the\nchanges and rationale.\n\nMajor changes should have a new RFC. The old RFC is moved to the [Discontinued]\nstage when the replacement is merged.\n\n## Reference\n[Reference]: #reference\n\n### Relevant Teams\n[Relevant Teams]: #relevant-teams\n\nThe RFC template requires indicating the relevant core teams. The following table\noffers a reference of teams responsible for each project. Please reach out for\nfurther guidance.\n\n|   Core Team   | Project/Topics                               | Github Team                |\n|---------------|----------------------------------------------|----------------------------|\n| Ember.js      | Ember.js                                     | `@emberjs/Framework`       |\n| Ember Data    | Ember Data                                   | `@emberjs/ember-data-core` |\n| Ember CLI     | Ember CLI                                    | `@emberjs/cli`             |\n| Learning      | Documentation, Website, learning experiences | `@emberjs/learning-core`   |\n| TypeScript    | TypeScript integration and design            | `@emberjs/typescript-core` |\n| Steering      | Governance                                   | `@emberjs/steering`        |\n\n## Final comment periods (FCP)\n[FCP]: #final-comment-periods-fcp\n\nFor certain stage advancements, a _final comment period_ (FCP) is required. This\nis a period lasting 7 days. The beginning of this period will be signaled with a\ncomment and tag on the RFC's pull request. Furthermore, a message will be posted in\n`#news-and-announcements` on [Ember Discord](https://discord.gg/emberjs) and on the\n[official Ember Twitter account](https://twitter.com/emberjs) to attract the community's attention.\n\nAn RFC can be modified based upon feedback from the [core teams] and community\nduring the final comment period. Significant modifications may trigger a new\nfinal comment period.\n\nAt the end of a successful FCP, the RFC moves into the stage specified.\n\n### FCP to close\n[FCP to close]: #fcp-to-close\n\nAn RFC may be closed or discontinued by the [core teams] after public discussion\nhas settled and comments have been made summarizing the rationale for closing.\nThe RFC will enter a \"final comment period to close\" lasting 7 days. At the end\nof the \"FCP to close\" period, the PR will be closed.\n\nAn RFC author may withdraw their own RFC by closing it themselves.\n\n## For Core Team Members\n[For Core Team Members]: #for-core-team-members\n\n### Reviewing RFCs\n\nEach core team is responsible for reviewing open RFCs. The team must ensure\nthat if an RFC is relevant to their team's responsibilities the team is\ncorrectly specified in the 'Relevant Team(s)' section of the RFC front-matter.\nThe team must also ensure that each RFC addresses any consequences, changes, or\nwork required in the team's area of responsibility.\n\nAs it is with the wider community, the RFC process is the time for\nteams and team members to push back on, encourage, refine, or otherwise comment\non proposals.\n\n### Reviewing entry into [Ready for Release] Stage\n\nAs described in [Ready for Release], each core team is responsible for\nreviewing RFCs that are ready to move to that stage.\n\n### Referencing RFCs\n\n- When mentioning RFCs that have been merged, link to the merged version,\nnot to the pull-request.\n\n### Champion Responsibilities\n\n* Achieving consensus from the team(s) to move the RFC through the stages of\nthe RFC process.\n* Ensuring the RFC follows the RFC process.\n* Shepherding the planning and implementation of the RFC. Before the RFC is\n[Accepted], the champion may remove themselves. The champion may find a replacement\nchampion at any time.\n\n### Helpful checklists for Champions\n\n#### Becoming champion of an RFC\n- [ ] Assign the RFC to yourself\n\n#### Advancing the RFC to the next stage\n- [ ] Achieve consensus to move to the next stage from relevant core teams\n- [ ] If the stage requires an FCP to enter, comment in the RFC to address any\n  outstanding issues and to proclaim the start of the FCP period, and tweet\n  from `@emberjs` about the FCP\n- [ ] Ensure the RFC has had the filename and header updated with the PR number\n- [ ] After the FCP period (if any), merge the RFC PR\n- [ ] Ensure relevant teams plan out what is necessary to implement in the next\n  stage\n- [ ] Prepare for advancing the RFC to the next stage if applicable (e.g.\n  opening a placeholder PR)\n\nFor RFCs opened before the implementation of\n[Staged RFCs](https://github.com/emberjs/rfcs/blob/master/text/0617-rfc-stages.md)\ndid not get advancement PRs to their next stage. See the\n[automations docs](https://github.com/emberjs/rfcs/blob/master/.github/READTHIS.md#trigger-opening-advancement-pryml) for instructions on how to trigger the advancement workflow.\n\n#### Move to FCP to Close\n- [ ] Achieve consensus to move to \"FCP to Close\" from relevant core teams\n- [ ] Comment in the RFC to explain the decision\n\n#### Closing an RFC\n- [ ] Comment about the end of the FCP period with no new info\n- [ ] Close the PR\n\n**Ember's RFC process owes its inspiration to the [Rust RFC process]**\n\n[Rust RFC process]: https://github.com/rust-lang/rfcs\n[core teams]: http://emberjs.com/team/\n[feature flag]: http://emberjs.com/guides/contributing/adding-new-features/\n[core team notes]: https://github.com/emberjs/core-notes/tree/master/ember.js\n","funding_links":["https://github.com/sponsors/emberjs","https://opencollective.com/emberjs"],"categories":["Packages"],"sub_categories":["Discovery"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/emberjs.github.io%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/emberjs.github.io%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/emberjs.github.io%2Frfcs/lists"}