Addonify ember-cli

[bcardarella]

• [ ] build pipeline
• [ ] blueprint
• [ ] commands
• [ ] test suite

[bcardarella]

FWIW if this is a desirable direction I was going to propose this be done in many phases. I can spend time in February breaking out the build pipeline.

[jakecraige]

:+1: on this. Should we begin a list on here of specific pieces that should be broken out? A big one that's already on the table is blueprints #2803

[bcardarella]

@jakecraige added some above, feel free to add/propose more

[ef4]

I agree with this goal. If we do this it would make sense to create a separate project with a new name to hold the common core infrastructure, and keep ember-cli as the ember-specific consumer of the common infrastructure.

[bcardarella]

@ef4 confirm, I would imagine that ember-cli itself would just be a collection of addons that depends upon this more abstract higher-level project

[stefanpenner]

I am not apposed to this, but my primary goal will continue to be building the best possible toolchain for ember app developers.

I am fine and happy to enable other efforts, as long as they don't impede on the primary goal of this project.

Ultimately a planned decomposition of the project was a reason behind the org, so lets doit!

[bcardarella]

@stefanpenner I can tackle the extraction of the build pipeline in February

[stefanpenner]

@stefanpenner I can tackle the extraction of the build pipeline in February

Awesome, as you begin we should sync up. :)

[trabus]

@jgwhite and I started work on blueprint extraction today. The gameplan (as I understand it) is to identify and extract everything that is not ember-cli specific into the blueprint library, then we'll provide the necessary hooks to extend it with what is needed in ember-cli (such as project awareness, ui output, and methods like lookupBlueprint) in an ember-cli-addon.

[stefanpenner]

this has gone stale, will gladly re-open if it gets attention.