-
-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future of Ember Engines? #687
Comments
@villander Thank you for all your efforts to push engines forward. I appreciate your work with the codebase, the guides, and perhaps most all, the ember community. And I agree that many initiatives, such as the engine router service, have taken much too long to land. I just met with @rwjblue to try to make sure that we can all work together more effectively going forward. We'd like to re-start our monthly meetings, which will be open to all interested. We've tentatively planned to meet on the second Friday of every month, 10:30 - 11:30am ET, starting January 8, 2021. However, we will coordinate this more in the #dev-ember-engines channel in discord, and can reschedule if necessary. Rob and I also discussed some specifics of a solution regarding your engine router service work and arrived at a proposal for better handling external routes. We can discuss this with you in our first meeting at the latest, but I'll try to work with you a bit beforehand. Thanks again for all your work and for raising this issue. Rob and I will do our best to help you and others who want this project to succeed 🚀 |
Awesome! Great news to make 2021 the most promissory year for Ember Engines Looking forward to our monthly meetings and all challenges ahead. 🚀 ⚙️ i4chTkhR6pEzR46ur6OEKNWigmZmiHhJjgRw6umHEgI.mp4 |
@villander what's the status here? |
@wagenet unfortunately we're not making tremendous progress here yet. We started to have weekly meetings between me, @runspired and @SergeAstapov. We began to get some Github privileges from @rwjblue, but it's still in progress. Feel free to participate with us every Thursday, join at |
I think the biggest blocker sorta comes down to needing a constant framework team presence. There's lots the project can do on its own, but there's also lots that is tied so integral to core concepts like routing that iteration is difficult. Recent example is the service RFC. Without a core representative it's hard for us to know when/if that'll get considered, and the alternatives to that RFC are all "tie it even deeper into ember proper" I know @wycats was considering some engines reworking for embroider etc. Not sure where that's gone. I've moved to scaffolding engines as stand-alone addons in a monorepo with the warp-drive engage project, that resolves a lot of the ergonomics issues though it would be nice to have a roadmap for engines in the embroider world. |
I believe @wycats has been involved in some discussions around this. We may need to formalize further. |
I couldn't agree more, especially removing |
Hello to everyone!
We have this roadmap announced by a core team in 2018, but still today we didn't achieve 50% of the goals at the end of 2020. Also, we have a lot of pull requests running for more than one year without the proper support.
ROADMAP STATUS: ember-engines/ember-engines#736
I'm trying to do my best to see Ember Engines more friendly and optimized for the entire community, also fully integrated with Embroider (huge thanks to @ef4 here). But is so frustrating don't find a way to do that most of the time. Now we just need some support to review a bunch of work in progress ( blocked for lack of review and guidance from core team ).
I'd love to see more constancy work on Ember Engines from the core team side if it continues been a great asset for them, of course.
Also, I'd like to left here a huge thanks to @dgeb @locks and @jenweber for always try to make Ember Engines more visible by teaching me on Ember Engines Guides
The text was updated successfully, but these errors were encountered: