Naming conundrum

[SethDavenport]

Hi @wbuchwalter @e-schultz @dagstuan @clbond,

This isn't really an issue per se but it's the best way I currently have to get in touch with all of you. I'm Seth, and I do a lot of work on the ng2-redux side of things in this github org.

As you probably know, the Angular core team recently announced a change to their naming strategy - e.g. the two frameworks are no longer known as AngularJS (1.x) and Angular2 respectively; instead they're both Angular. With the impending release of Angular 4.x, this presents a challenge for us in terms of naming, since:

• npm ng-redux is the AngularJS (1.x) binding, and
• npm ng2-redux is the Angular 2+ binding.

So at minimum on our side we're going to have to remove the '2' from our package's name or we'll look a bit silly when angular 4 drops :)

Since we're going to have to rename I actually thought it would be a good time for us to make the jump to scoped packages while we're at it.

Tentatively what I'm thinking for the Angular 2+ side is something like:

@angular-redux/core (formerly ng2-redux)
@angular-redux/router (formerly ng2-redux-router, currently maintained by @dagstuan)
@angular-redux/form (formerly ng2-redux-form, currently maintained by @clbond)
@angular-redux/epic (formerly ng2-redux-observable-operator, currently mainained by @e-schultz)
// ... whatever other extensions float up

I took the liberty of registering @angular-redux/core already on npm (currently just as a user, but it can be converted to an org). I have not publicized this stuff yet.

I guess my question for you guys is whether you're cool with this, especially @wbuchwalter and whether you want in on this in the ng1 side of the fence or not.

Cheers,

[SethDavenport]

Just to clarify - ng-redux doesn't need to change at all if you don't want. But you can come under the @angular-redux npm namespace if you do want.

[SethDavenport]

Ok, I'm assuming silence === no objections :)

Closing.