{"id":13452252,"url":"https://github.com/devongovett/rfcs-1","last_synced_at":"2025-03-23T19:33:53.485Z","repository":{"id":50794329,"uuid":"172965347","full_name":"devongovett/rfcs-1","owner":"devongovett","description":"RFCs for changes to React","archived":false,"fork":true,"pushed_at":"2021-05-29T05:37:28.000Z","size":140,"stargazers_count":16,"open_issues_count":0,"forks_count":3,"subscribers_count":6,"default_branch":"master","last_synced_at":"2024-10-28T18:53:48.238Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"reactjs/rfcs","license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/devongovett.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2019-02-27T18:10:11.000Z","updated_at":"2022-08-18T06:39:55.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/devongovett/rfcs-1","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devongovett%2Frfcs-1","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devongovett%2Frfcs-1/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devongovett%2Frfcs-1/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/devongovett%2Frfcs-1/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/devongovett","download_url":"https://codeload.github.com/devongovett/rfcs-1/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245159203,"owners_count":20570343,"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":[],"created_at":"2024-07-31T07:01:18.439Z","updated_at":"2025-03-23T19:33:53.165Z","avatar_url":"https://github.com/devongovett.png","language":null,"funding_links":[],"categories":["Others"],"sub_categories":[],"readme":"# React RFCs\r\n\r\nMany changes, including bug fixes and documentation improvements can be\r\nimplemented and reviewed via the normal GitHub pull request workflow.\r\n\r\nSome changes though are \"substantial\", and we ask that these be put\r\nthrough a bit of a design process and produce a consensus among the React\r\ncore team.\r\n\r\nThe \"RFC\" (request for comments) process is intended to provide a\r\nconsistent and controlled path for new features to enter the project.\r\n\r\n[Active RFC List](https://github.com/reactjs/rfcs/pulls)\r\n\r\nReact is still **actively developing** this process, and it will still change as\r\nmore features are implemented and the community settles on specific approaches\r\nto feature development.\r\n\r\n## Contributor License Agreement (CLA)\r\n\r\nIn order to accept your pull request, we need you to submit a CLA. You only need\r\nto do this once, so if you've done this for another Facebook open source\r\nproject, you're good to go. If you are submitting a pull request for the first\r\ntime, just let us know that you have completed the CLA and we can cross-check\r\nwith your GitHub username.\r\n\r\n**[Complete your CLA here.](https://code.facebook.com/cla)**\r\n\r\n## When to follow this process\r\n\r\nYou should consider using this process if you intend to make \"substantial\"\r\nchanges to React or its documentation. Some examples that would benefit\r\nfrom an RFC are:\r\n\r\n   - A new feature that creates new API surface area, and would\r\n     require a feature flag if introduced.\r\n   - The removal of features that already shipped as part of the release\r\n     channel.\r\n   - The introduction of new idiomatic usage or conventions, even if they\r\n     do not include code changes to React itself.\r\n\r\nThe RFC process is a great opportunity to get more eyeballs on your proposal\r\nbefore it becomes a part of a released version of React. Quite often, even\r\nproposals that seem \"obvious\" can be significantly improved once a wider\r\ngroup of interested people have a chance to weigh in.\r\n\r\nThe RFC process can also be helpful to encourage discussions about a proposed\r\nfeature as it is being designed, and incorporate important constraints into\r\nthe design while it's easier to change, before the design has been fully\r\nimplemented.\r\n\r\nSome changes do not require an RFC:\r\n\r\n  - Rephrasing, reorganizing or refactoring\r\n  - Addition or removal of warnings\r\n  - Additions that strictly improve objective, numerical quality\r\n  criteria (speedup, better browser support)\r\n  - Additions only likely to be _noticed by_ other implementors-of-React,\r\n  invisible to users-of-React.\r\n\r\n## What the process is\r\n\r\nIn short, to get a major feature added to React, one usually first gets\r\nthe RFC merged into the RFC repo as a markdown file. At that point the RFC\r\nis 'active' and may be implemented with the goal of eventual inclusion\r\ninto React.\r\n\r\n* Fork the RFC repo http://github.com/reactjs/rfcs\r\n* Copy `0000-template.md` to `text/0000-my-feature.md` (where\r\n'my-feature' is descriptive. Don't assign an RFC number yet).\r\n* Fill in the RFC. Put care into the details: **RFCs that do not\r\npresent convincing motivation, demonstrate understanding of the\r\nimpact of the design, or are disingenuous about the drawbacks or\r\nalternatives tend to be poorly-received**.\r\n* Submit a pull request. As a pull request the RFC will receive design\r\nfeedback from the larger community, and the author should be prepared\r\nto revise it in response.\r\n* Build consensus and integrate feedback. RFCs that have broad support\r\nare much more likely to make progress than those that don't receive any\r\ncomments.\r\n* Eventually, the team will decide whether the RFC is a candidate\r\nfor inclusion in React.\r\n* RFCs that are candidates for inclusion in React will enter a \"final comment\r\nperiod\" lasting 3 calendar days. The beginning of this period will be signaled with a\r\ncomment and tag on the RFCs pull request.\r\n* An RFC can be modified based upon feedback from the team and community.\r\nSignificant modifications may trigger a new final comment period.\r\n* An RFC may be rejected by the team after public discussion has settled\r\nand comments have been made summarizing the rationale for rejection. A member of\r\nthe team should then close the RFCs associated pull request.\r\n* An RFC may be accepted at the close of its final comment period. A team\r\nmember will merge the RFCs associated pull request, at which point the RFC will\r\nbecome 'active'.\r\n\r\n## The RFC life-cycle\r\n\r\nOnce an RFC becomes active, then authors may implement it and submit the\r\nfeature as a pull request to the React repo. Becoming 'active' is not a rubber\r\nstamp, and in particular still does not mean the feature will ultimately\r\nbe merged; it does mean that the core team has agreed to it in principle\r\nand are amenable to merging it.\r\n\r\nFurthermore, the fact that a given RFC has been accepted and is\r\n'active' implies nothing about what priority is assigned to its\r\nimplementation, nor whether anybody is currently working on it.\r\n\r\nModifications to active RFCs can be done in followup PRs. We strive\r\nto write each RFC in a manner that it will reflect the final design of\r\nthe feature; but the nature of the process means that we cannot expect\r\nevery merged RFC to actually reflect what the end result will be at\r\nthe time of the next major release; therefore we try to keep each RFC\r\ndocument somewhat in sync with the language feature as planned,\r\ntracking such changes via followup pull requests to the document.\r\n\r\n## Implementing an RFC\r\n\r\nThe author of an RFC is not obligated to implement it. Of course, the\r\nRFC author (like any other developer) is welcome to post an\r\nimplementation for review after the RFC has been accepted.\r\n\r\nIf you are interested in working on the implementation for an 'active'\r\nRFC, but cannot determine if someone else is already working on it,\r\nfeel free to ask (e.g. by leaving a comment on the associated issue).\r\n\r\n## Reviewing RFCs\r\n\r\nEach week the team will attempt to review some set of open RFC\r\npull requests.\r\n\r\nWe try to make sure that any RFC that we accept is accepted at the\r\nweekly team meeting. Every accepted feature should have a core team champion,\r\nwho will represent the feature and its progress.\r\n\r\n**React's RFC process owes its inspiration to the [Yarn RFC process], [Rust RFC process], and [Ember RFC process]**\r\n\r\n[Yarn RFC process]: https://github.com/yarnpkg/rfcs\r\n[Rust RFC process]: https://github.com/rust-lang/rfcs\r\n[Ember RFC process]: https://github.com/emberjs/rfcs\r\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdevongovett%2Frfcs-1","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdevongovett%2Frfcs-1","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdevongovett%2Frfcs-1/lists"}