{"id":14966899,"url":"https://github.com/reactiveui/rfcs","last_synced_at":"2025-10-19T09:31:22.790Z","repository":{"id":66316508,"uuid":"133005022","full_name":"reactiveui/rfcs","owner":"reactiveui","description":"RFCs for changes to ReactiveUI","archived":false,"fork":false,"pushed_at":"2019-07-23T21:36:14.000Z","size":23,"stargazers_count":5,"open_issues_count":17,"forks_count":5,"subscribers_count":25,"default_branch":"master","last_synced_at":"2024-04-14T13:08:30.826Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://reactiveui.net/rfcs","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/reactiveui.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},"funding":{"github":["reactivemarbles"]}},"created_at":"2018-05-11T07:26:07.000Z","updated_at":"2023-10-11T00:00:01.000Z","dependencies_parsed_at":"2023-07-10T21:31:40.848Z","dependency_job_id":null,"html_url":"https://github.com/reactiveui/rfcs","commit_stats":{"total_commits":13,"total_committers":6,"mean_commits":"2.1666666666666665","dds":0.3846153846153846,"last_synced_commit":"5b51ad1b6b86430c98e7014aec2599df9f25e6cf"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactiveui%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactiveui%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactiveui%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactiveui%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/reactiveui","download_url":"https://codeload.github.com/reactiveui/rfcs/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":219869513,"owners_count":16555291,"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-09-24T13:37:07.128Z","updated_at":"2025-10-19T09:31:22.471Z","avatar_url":"https://github.com/reactiveui.png","language":"Shell","funding_links":["https://github.com/sponsors/reactivemarbles"],"categories":[],"sub_categories":[],"readme":"# ReactiveUI RFCs\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 ReactiveUI\ncore team.\n\nThe \"RFC\" (request for comments) process is intended to provide a\nconsistent and controlled path for new features to enter the framework.\n\n[Active RFC List](https://github.com/reactiveui/rfcs/pulls)\n\n## When you need to follow this process\n\nYou need to follow this process if you intend to make \"substantial\"\nchanges to ReactiveUI, its subprojects or its documentation. What constitutes a\n\"substantial\" change is evolving based on community norms, but may\ninclude 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 ReactiveUI 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-ReactiveUI,\ninvisible to users-of-ReactiveUI.\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\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\ndesign.\n\n## What the process is\n\nIn short, to get a major feature added to ReactiveUI, one must first get the\nRFC merged into the RFC repo as a markdown file. At that point the RFC\nis 'active' and may be implemented with the goal of eventual inclusion\ninto ReactiveUI.\n\n* Fork the RFC repo http://github.com/reactiveui/rfcs\n* Copy `0000-template.md` 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* 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.\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* Eventually, the [core team] will decide whether the RFC is a candidate\nfor inclusion in ReactiveUI.\n* RFCs that are candidates for inclusion in ReactiveUI will enter a \"final comment\nperiod\" lasting 7 days. The beginning of this period will be signaled with a\ncomment and tag on the RFC's pull request and on the [Reactive Inc. Slack instance](http://reactiveui.net/slack). Furthermore,\n[ReactiveUI's official Twitter account](https://twitter.com/reactivexui) will post a\ntweet about the RFC to attract the community's attention. \n* An RFC can be modified based upon feedback from the [core team] and community.\nSignificant modifications may trigger a new final comment period.\n* An RFC may be rejected by the [core team] after public discussion has settled\nand comments have been made summarizing the rationale for rejection. A member of\nthe [core team] should then close the RFC's associated pull request.\n* An RFC may be accepted at the close of its final comment period. A [core team]\nmember will merge the RFC's associated pull request, at which point the RFC will\nbecome 'active'.\n\n## The RFC life-cycle\n\nOnce an RFC becomes active then authors may implement it and submit the\nfeature as a pull request to the ReactiveUI repo. Becoming 'active' is not a rubber\nstamp, and in particular still does not mean the feature will ultimately\nbe merged; it does mean that the core team has agreed to it in principle\nand are amenable to merging it.\n\nFurthermore, the fact that a given RFC has been accepted and is\n'active' implies nothing about what priority is assigned to its\nimplementation, nor whether anybody is currently working on it.\n\nModifications to active RFC's can be done in followup PR's. We strive\nto write each RFC in a manner that it will reflect the final design of\nthe feature; but the nature of the process means that we cannot expect\nevery merged RFC to actually reflect what the end result will be at\nthe time of the next major release; therefore we try to keep each RFC\ndocument somewhat in sync with the language feature as planned,\ntracking such changes via followup pull requests to the document.\n\n## Implementing an RFC\n\nThe author of an RFC is not obligated to implement it. Of course, the\nRFC author (like any other developer) is welcome to post an\nimplementation for review after the RFC has been accepted.\n\nIf you are interested in working on the implementation for an 'active'\nRFC, but cannot determine if someone else is already working on it,\nfeel free to ask (e.g. by leaving a comment on the associated issue).\n\n## Reviewing RFC's\n\nEach week the [core team] will attempt to review some set of open RFC\npull requests.\n\nWe try to make sure that any RFC that we accept is accepted at the\nFriday team meeting, and reported in [meeting minutes]. Every\naccepted feature should have a core team champion, who will represent\nthe feature and its progress.\n\n**ReactiveUI's RFC process owes its inspiration to the [Ember RFC process], in turn inspired by the [Rust RFC process]**\n\n[Ember RFC process]: https://github.com/emberjs/rfcs\n[Rust RFC process]: https://github.com/rust-lang/rfcs\n[core team]: https://reactiveui.net/team/\n[feature flag]: http://emberjs.com/guides/contributing/adding-new-features/\n[meeting minutes]: https://github.com/reactiveui/meeting-minutes/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactiveui%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Freactiveui%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactiveui%2Frfcs/lists"}