{"id":28673335,"url":"https://github.com/webstudio-is/webstudio-rfcs","last_synced_at":"2026-02-13T20:06:52.442Z","repository":{"id":104336723,"uuid":"575341534","full_name":"webstudio-is/webstudio-rfcs","owner":"webstudio-is","description":"RFCs for changes to Webstudio","archived":false,"fork":false,"pushed_at":"2024-04-13T11:35:10.000Z","size":50,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":8,"default_branch":"main","last_synced_at":"2025-06-06T05:49:55.245Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/webstudio-is.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","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}},"created_at":"2022-12-07T09:45:44.000Z","updated_at":"2023-01-23T18:24:26.000Z","dependencies_parsed_at":"2024-04-13T12:25:18.578Z","dependency_job_id":"cf41a836-bf77-4e12-bd7d-78b336030e21","html_url":"https://github.com/webstudio-is/webstudio-rfcs","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/webstudio-is/webstudio-rfcs","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webstudio-is%2Fwebstudio-rfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webstudio-is%2Fwebstudio-rfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webstudio-is%2Fwebstudio-rfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webstudio-is%2Fwebstudio-rfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/webstudio-is","download_url":"https://codeload.github.com/webstudio-is/webstudio-rfcs/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webstudio-is%2Fwebstudio-rfcs/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":259712415,"owners_count":22900041,"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":"2025-06-13T20:10:19.094Z","updated_at":"2025-09-21T00:23:07.059Z","avatar_url":"https://github.com/webstudio-is.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Webstudio RFCs\n\nThe \"RFC\" (request for comments) process is intended to provide a\nconsistent and controlled path for new features or changes with global impact to architecture or coding style to enter the project.\n\n[Active RFC List](https://github.com/webstudio-is/rfcs/pulls)\n\n\n## When to follow this process\n\nYou should consider using this process if you intend to make \"substantial\"\nchanges to Webstudio or its documentation. Some examples that would benefit\nfrom an RFC are:\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 Webstudio itself.\n  - Change to how Webstudio applications are architectured\n  - Change to the coding style of choice\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\n  criteria (speedup, better browser support)\n\n## What to expect\n\nIn practice, Webstudio RFCs serve two purposes:\n\n* **Webstudio Team RFCs** are submitted by [Webstudio Team members](https://github.com/orgs/webstudio-is/people) after extensive (sometimes,\nmulti-month or multi-year) design, discussion, and experimentation.\n\n* **Community RFCs** can be submitted by anyone. We apply the same level of rigour both to Webstudio Team RFCs and Community RFCs. \n\n## What the process is\n\n* Fork the RFC repo http://github.com/webstudio-is/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 team will decide whether the RFC is a candidate\nfor inclusion in Webstudio. \n* An RFC can be modified based upon feedback from the team and community.\n* An RFC may be rejected by the team after public discussion has settled\nand comments have been made summarizing the rationale for rejection. A member of\nthe team should then close the RFCs associated pull request.\n* An RFC may be accepted at the close of its final comment period. A team\nmember will merge the RFCs associated pull request, at which point the RFC will\nbecome 'active'.\n\n\n## The RFC lifecycle\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 RFCs can be done in followup PRs. 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","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebstudio-is%2Fwebstudio-rfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fwebstudio-is%2Fwebstudio-rfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebstudio-is%2Fwebstudio-rfcs/lists"}