{"id":21571120,"url":"https://github.com/ti-community-infra/rfcs","last_synced_at":"2026-03-19T20:53:42.732Z","repository":{"id":48533685,"uuid":"333003657","full_name":"ti-community-infra/rfcs","owner":"ti-community-infra","description":"RFCs for changes to TiDB community infra","archived":false,"fork":false,"pushed_at":"2023-04-03T07:35:33.000Z","size":18,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-03-18T06:15:20.749Z","etag":null,"topics":["rfcs","ti-community-infra"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ti-community-infra.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"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}},"created_at":"2021-01-26T07:20:29.000Z","updated_at":"2023-04-03T07:35:38.000Z","dependencies_parsed_at":"2025-01-24T12:43:24.656Z","dependency_job_id":"8578fbb4-7887-4f63-882d-f7f55c8aadea","html_url":"https://github.com/ti-community-infra/rfcs","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/ti-community-infra/rfcs","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ti-community-infra%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ti-community-infra%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ti-community-infra%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ti-community-infra%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ti-community-infra","download_url":"https://codeload.github.com/ti-community-infra/rfcs/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ti-community-infra%2Frfcs/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":273842300,"owners_count":25177917,"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","status":"online","status_checked_at":"2025-09-05T02:00:09.113Z","response_time":402,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"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":["rfcs","ti-community-infra"],"created_at":"2024-11-24T11:14:56.464Z","updated_at":"2026-02-13T05:02:37.724Z","avatar_url":"https://github.com/ti-community-infra.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# TiDB community infra RFCs\n\nRFCs for changes to TiDB community infra\n\n## What is an RFC?\n\nThe \"RFC\" (request for comments) process is intended to provide a\nconsistent and controlled path for new features to enter the community infra.\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 TiDB community.\n\n## The RFC life-cycle\n\nAn RFC goes through the following stages:\n\n- **Pending:** when the RFC is submitted as a PR.\n- **Active:** when an RFC PR is merged and undergoing implementation.\n- **Landed:** when an RFC's proposed changes are shipped in an actual release.\n- **Rejected:** when an RFC PR is closed without being merged.\n\n[Pending RFC List](https://github.com/ti-community-infra/rfcs/pulls)\n\n## When to follow this process\n\nYou need to follow this process if you intend to make \"substantial\"\nchanges to one of the projects listed below:\n\n- [tichi](https://github.com/ti-community-infra/tichi)\n- [ti-challenge-bot](https://github.com/ti-community-infra/ti-challenge-bot)\n- [ti-sync-bot](https://github.com/ti-community-infra/ti-sync-bot)\n\nWhat constitutes a \"substantial\" change is evolving based on community norms, but may include the following:\n\n- A new feature that creates new plugins or components\n- Changing the semantics or behavior of an existing plugins or API\n- The removal of features that are already shipped as part of the release channel\n\nSome changes do not require an RFC:\n\n- Additions that strictly improve objective, numerical quality criteria (speedup)\n- Fixing objectively incorrect behavior\n- Rephrasing, reorganizing or refactoring\n- Addition or removal of logs\n- Additions only likely to be _noticed by_ other implementors, invisible to users\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## Why do you need to do this\n\nIt is great that you are considering suggesting new features or changes to TiDB community infra - we appreciate your willingness to contribute! However, as these tools becomes more widely used, we need to take stability more seriously, and thus have to carefully consider the impact of every change we make that may affect end users.\n\nThese constraints and tradeoffs may not be immediately obvious to users who are proposing a change just to solve a specific problem they just ran into. The RFC process serves as a way to guide you through our thought process when making changes to TiDB community infra, so that we can be on the same page when discussing why or why not these changes should be made.\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 TiDB community infra, 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 TiDB community infra.\n\n- Fork the RFC repo https://github.com/ti-community-infra/rfcs\n\n- Copy `0000-template.md` to `src/0000-my-feature.md` (where\n  'my-feature' is descriptive. don't assign an RFC number yet).\n\n- Fill in the RFC. Put care into the details: **RFCs that do not\n  present convincing motivation, demonstrate understanding of the\n  impact of the design, or are disingenuous about the drawbacks or\n  alternatives tend to be poorly-received**.\n\n- Submit a pull request. Make sure to follow the pull request template and open a corresponding discussion thread.\n\n- Build consensus and integrate feedback in the discussion thread. RFCs that have broad support are much more likely to make progress than those that don't receive any comments.\n\n- Eventually, the [core team] will decide whether the RFC is a candidate\n  for inclusion in TiDB community infra.\n\n- An RFC can be modified based upon feedback from the [core team] and community. Significant modifications may trigger a new final comment period.\n\n- An RFC may be rejected after public discussion has settled\n  and comments have been made summarizing the rationale for rejection. A member of the [core team] should then close the RFC's associated pull request.\n\n- An RFC may be accepted at the close of its final comment period. A [core team] member will merge the RFC's associated pull request, at which point the RFC will become 'active'.\n\n## Details on Active RFCs\n\nOnce an RFC becomes active then authors may implement it and submit the\nfeature as a pull request to the 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\nAn active RFC should have the link to the implementation PR listed if there is one. Feedback to the actual implementation should be conducted in the implementation PR instead of the original RFC PR.\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\nMembers of the [core team] will attempt to review some set of open RFC\npull requests on a regular basis. If a core team member believes an RFC PR is ready to be accepted into active status, they can approve the PR using GitHub's review feature to signal their approval of the RFC.\n\n**TiDB Community Infra's RFC process owes its inspiration to the [React RFC process], [Rust RFC process], [Vue RFC process] and [Ember RFC process]**\n\n[react rfc process]: https://github.com/reactjs/rfcs\n[rust rfc process]: https://github.com/rust-lang/rfcs\n[ember rfc process]: https://github.com/emberjs/rfcs\n[vue rfc process]: https://github.com/vuejs/rfcs\n[core team]: https://github.com/orgs/ti-community-infra/people\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fti-community-infra%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fti-community-infra%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fti-community-infra%2Frfcs/lists"}