A Little Encouragement Goes a Long Way in 2018
In May 2018, Ember Core team member Katie Gengler published Ember’s 2018 Roadmap: A Call for Blog Posts. With this call-to-action she invites the community to give feedback on their hopes and wishes for Ember moving forward. In this context, I also want to share some of my own thoughts on Ember and what I’d be excited to see in its nearest future.
The Ember team would like you to write a blog post to propose goals and direction for Ember in the remainder of 2018. The content of these posts will help us to draft our first Roadmap RFC.
First off, I’m confident that Ember already has done a lot to allow me and many others to create great and maintainable applications. And it has done so very early on. For a while naming conventions and a CLI-driven approach to scaffold, build & serve apps have been hallmarks of Ember as a framework for the ambitious developer. Other framework ecosystems are also adopting similar approaches to increase developer productivity (1, 2) and are having immense success with them.
Other productivity improvements that emerged with Ember include its well-planned release cycle (3) that has been put into practice during the v1.x era as early as 5 years ago, and the ongoing support through LTS releases (4) for more than 2 years. This mature and dependable release process has not only been extremely progressive back then, but in fact it still is.
@ember/test-helpers (6) improves the readability of tests massively and also makes async testing more than straightforward.
This makes me think that making features understandable to a diverse set of people does not only include explaining how technologies work, but also why they are so useful.
I already believe that Ember.js is a great choice for any web developer who wants to create scalable applications today. There’s really not much I could wish for on a technical level. Instead when I think about what I wish for Ember, visibility comes to my mind. I’d love both Ember’s core characteristics and its cutting-edge features to be understood by even more people; even by those who haven’t had much experience in using it to see its worthwhile benefits in the long-run of a project. I believe Ember’s bottleneck for adoption and community growth isn’t about technical aspects, it’s about visibility and outreach.
A Gap in Visibility
But who’s putting in the time and effort to maintain such an independent project? For a huge part, Ember’s community does, and it does so in their free time. Countless contributors work on improvements, bug fixes and features in the early hours preceding their day jobs, on their weekends, their time-off - to bring forward a software project which can compete with other major frameworks. And this in itself is remarkable.
This is why Ember truly is a framework of the community, by the community, for the community.
And this community effort is also what keeps Ember visible in the current front-end ecosystem. In the end, who’s stepping up to blog about latest features, to screencast debugging sessions, to demo Ember at their local meetup, to distribute Zoey stickers among their friends, to give talks on how to build an Ember app or to improve, fix and update any of the official online resources of Ember?
It’s not only the Ember Core or the Ember Learning Team who does all of this - it’s also you and me and us.
Taking the opportunity to change the way Ember is represented in the world to further its adoption is an open issue everyone can work on. Ember is still a somewhat hidden gem (8) and it keeps on “quietly shipping new cutting-edge features to its users” (9). But I don’t believe it has to be this way with a little help from the community.
Of course, there are those who already have a clear vision in mind right now and who are making consistent efforts to create online tutorials, write blog posts, give talks, send pull requests to the Ember.js website repository (10) and much more without any prompting. What I’d wish for Ember’s 2018 Roadmap though is to find ways to lower the entry barriers for newcomers to get started in their attempt to advocate Ember and to be creative on how to encourage a sense of empowerment in the wider community regarding outreach efforts.
Closing the Visibility Gap
I believe one of the biggest actions that could be taken to make contribution to anything that is outreach-related easier is by increasing the discoverability of discussion channels and already ongoing Github projects and related issues. On the Ember Community Slack chat, most notably the #st-website, #wb-marketing and #topic-talks channels are great first points of contact for anyone who was interested in helping out with marketing efforts to find something to help out with. I believe making these channels more discoverable for new developers, e.g. from having a noticeable call-to-action on the Ember.js website (11) or a dedicated, search-engine optimized landing page already goes a long way.
The Learning Team and the community have already leveraged many amazing initiatives recently, including a massive technical upgrade of the official Guides which makes it even easier for developers to contribute (12), the release of a status board to keep potential contributors informed which initiatives are still ongoing and require help (13), making blog content discoverable (14), creating a printable mini book about the framework (15), publishing project-related updates through a newsletter every single week (16) and many others. Speaking about these initiatives more openly and often might also draw interest of developers who don’t know yet what to work on or what to start off with. In my opinion the increased leverage of the RFC (Request for Comments) process adopted by the Rust Community (17), Quest issues for breaking down major work packages on these official resources, and the creation of Strike Teams for agile collaboration will also deepen community interest, increase a sense of ownership of how decisions are made and allow people to succeed on their possibly first OSS issue easily.
Wishing Upon a Vocal Community
These are some of the ideas that came to my mind when thinking about what I’d wish for Ember in 2018. I’d like to see Ember’s community grow even further and I believe one major way to achieve this goal is by improving its visibility - the degree by which it is seen by those who are already becoming part of the community and also by those outside of it.
In my opinion more explicit call-to-actions can have a big impact on the sense of community empowerment to make Ember visible: Being vocal about current outreach efforts that require community help, making those initiatives more discoverable and prompting the community to take action - just as has been done in this very call for blog posts (22) - are some of the options that I believe should be leveraged even further.
Ember is still a hidden gem but I’m confident that this can and will change. And with a little encouragement I believe there’s no one who could do a better job at this than us - the community.