Vue RFCs
A formal process for proposing and discussing substantial changes to the Vue.js core framework.
What is Vue RFCs?
Vue RFCs is the official repository and process for managing substantial changes to the Vue.js core framework. It provides a structured workflow where contributors can propose new features, API changes, or significant modifications, which are then reviewed and discussed by the Vue core team and community before implementation. This process ensures that Vue evolves in a stable, consensus-driven manner.
Vue.js core team members, framework contributors, and advanced developers who are proposing or reviewing significant changes to Vue's architecture, APIs, or behavior.
It offers a transparent, community-inclusive governance model that prevents haphazard changes, reduces breaking changes, and maintains Vue's stability and simplicity as it grows. Developers choose it to contribute meaningfully to Vue's future with a process that ensures their proposals receive proper design scrutiny and broad feedback.
Overview
RFCs for substantial changes / feature additions to Vue core
Use Cases
Best For
- Proposing a new Vue.js core feature that adds API surface area
- Suggesting a breaking change to an existing Vue.js API
- Managing the design phase for substantial framework evolution
- Understanding the decision-making process behind Vue.js changes
- Contributing to Vue.js with a structured, review-driven approach
- Tracking the status of upcoming features or modifications to Vue core
Not Ideal For
- Making minor bug fixes or performance optimizations in Vue core that don't alter API semantics
- Proposing changes to Vue ecosystem libraries like Vue Router or Pinia
- Teams needing rapid implementation of features without community feedback cycles
- New contributors looking to start with simple documentation improvements or small PRs
Pros & Cons
Pros
Guides contributors through a defined workflow from initial discussion to implementation, ensuring proposals are thoroughly vetted to prevent hasty changes, as outlined in the RFC lifecycle stages.
Facilitates open discussions with both the Vue core team and community, leading to decisions with broad support and reducing the risk of unpopular or breaking changes.
Tracks RFCs through clear stages like Pending, Active, Landed, or Rejected, providing visibility on proposal progress and outcomes, as specified in the README.
Adopts and adapts RFC processes from major projects like React and Rust, lending credibility and tested methodologies to Vue's evolution, ensuring reliability.
Cons
Requires detailed markdown files with convincing motivation and design, which can be daunting for contributors with simpler suggestions, as emphasized in the submission guidelines.
Only covers Vue core changes, leaving ecosystem projects without a formal RFC process, potentially leading to inconsistent governance across the Vue landscape.
Active RFCs have no guaranteed priority or resources for implementation, meaning accepted features might linger without being shipped, as noted in the 'Details on Active RFCs' section.
Progress hinges on core team reviews, which could slow down the process if they are overwhelmed, delaying decisions and feedback cycles.
Frequently Asked Questions
Related Projects
React RFCsRFCs for changes to React
OTEPsSpecifications for OpenTelemetry
Compose SpecificationThe Compose specification
React Native RFCsDiscussions and proposals related to the main React Native project
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.