Rfcs

Overview

The Svelte RFCs (Request for Comments) is a platform for discussing major changes to the Svelte JavaScript framework. The process is inspired by the RFC processes of frameworks like React and Ember. It allows for the community to propose and discuss significant changes that could involve breaking changes or controversial decisions. The RFC process helps define the problem clearly, gather use cases, and explore different solutions. While the design described in an RFC may not always be accepted, the process itself provides value in terms of community feedback and collaboration.

Features

• RFC Process: Provides a structured process for proposing and discussing major changes to the Svelte framework.
• Clear Problem Definition: Emphasizes the importance of clearly defining the problem and collecting use cases before proposing a solution.
• Design Feedback: Allows for design feedback from the larger community through pull requests, ensuring different perspectives are considered.
• Consensus Building: Aims to build consensus and gather support for RFCs through community comments and discussion.
• Final Comment Period: RFCs that are candidates for inclusion in Svelte enter a final comment period of 3 calendar days, allowing for further feedback and modifications.
• Rejection and Acceptance: RFCs may be rejected or accepted by the Svelte team after public discussion and summarizing the rationale.
• RFC Life-cycle: Once an RFC becomes active, authors can implement it and submit the feature as a pull request to the Svelte repository. However, being active does not guarantee merging or assign implementation priority.

Summary

The Svelte RFCs provide a structured process for proposing and discussing major changes to the Svelte framework. It emphasizes defining problems clearly, collecting use cases, and engaging in design feedback and discussion with the community. While not all proposed designs may be accepted, the RFC process encourages collaboration and consensus-building. Ultimately, RFCs that are accepted and become active can be implemented and submitted as pull requests to the Svelte repository.