The Role of Core Team Members
Each Ember core team plays a vital part in reviewing and guiding RFCs. If your RFC touches on a specific area—like Ember Data, Learning, or Framework, the relevant team is responsible for reviewing your proposal. Make sure you've listed the correct teams in the "Relevant Team(s)" section of your RFC front matter. This helps ensure it reaches the right people.
During the review process, core team members provide feedback, suggest improvements, and help shape the proposal. This is the time for in-depth discussion—teams may challenge, endorse, or refine your ideas to make sure they align with Ember's direction and standards.
When an RFC is ready to move into the Ready for Release stage, the relevant core teams review the proposal one final time before it moves forward.
| Core Team | Project/Topics | Github Team |
|---|---|---|
| Ember.js | Ember.js | @emberjs/Framework |
| Ember Data | Ember Data | @emberjs/ember-data-core |
| Ember CLI | Ember CLI | @emberjs/cli |
| Learning | Documentation, Website, learning experiences | @emberjs/learning-core |
| TypeScript | TypeScript integration and design | @emberjs/typescript-core |
| Steering | Governance | @emberjs/steering |
About Champions
Every RFC needs a champion from one of the core teams. This person represents your RFC in team meetings and helps it progress through the stages. Their role includes:
- Helping the team reach consensus to move the RFC forward.
- Ensuring your RFC follows the proper process.
- Supporting planning and implementation once the RFC is accepted.
A champion can step down before the RFC is accepted and may also find someone else to take over at any time.