Ember in 2018 (and 2019) has been more exciting than ever! We've been working diligently to advance the project based on our 2018 Roadmap, but while we work to finish that, it is time to think about the future.
The Ember team would like you to write a blog post to propose goals and direction for Ember for the next year. The content of these posts will help us to draft our next Roadmap RFC.
What's a Roadmap RFC?
The Roadmap will outline the community's priorities for the next year. It will be presented as an RFC and follow the normal RFC process. The RFC will be written based on community input--the blog posts we've requested and other community discussion--and curation from the core teams.
This is will be our second annual Roadmap RFC. To see the results of the process, see the 2018 Roadmap RFC.
The 2018 Roadmap led to the "Octane Edition" of Ember, currently in preview. Octane includes many features, most of which have already landed in a stable release. As the edition nears completion, we want the community to think beyond Octane to the next steps for Ember. The resulting Roadmap for 2019 will not necessarily include an edition but will outline what we will be working toward.
The Roadmap process is part of our on-going effort to have shared, clear, and published project-wide goals.
To contribute a post: Tweet a link to the post with the hashtag #EmberJS2019 or email a link to firstname.lastname@example.org. These posts will be collected and categorized, and each one will be read by those working to draft the Roadmap RFC.
Your post can be on any online writing platform, but we suggest:
- A post on your personal or company blog
- A GitHub gist
We'd like to hear about any aspect of Ember you have hopes for in 2019--not only about the Ember.js framework. Please include your desires for Ember Data, Ember CLI, learning, tooling, the community, addons, and anything else Ember-related.
Here are some broad ideas that might help you get started:
- Ideas for community programs
- Framework features
- Documentation improvements
- Ecosystem needs
- Tooling enhancements
We strongly encourage posts replying to or building off of others' posts. Please try to keep the discussion in the form of blog posts.
To kickoff the process, we've collected some early posts:
Dates may change, but this is a general overview of the upcoming process:
May 20: call for posts!
Throughout May and early June: read posts, draft Roadmap RFC
June 17: cutoff for posts--you can still write them (please do!), but we cannot guarantee they'll be read before the Roadmap creation
Late June: Post the Roadmap RFC on GitHub
Mid July: assuming we've reached consensus, and following the normal RFC process, accept final Roadmap
This is our second call for blog posts. For inspiration, or to better understand the process, you may want to look at the 2018 blog posts, as collected by community member Lennex Zinyando or directly on twitter, and the 2018 Roadmap RFC.
Many thanks also to the Rust Core team and the Rust community, from whom we are still learning and adapting process.