Rename to react-router-redux

[jlongster]

@ryanflorence and @mjackson have invited this project to join the rackt set of projects since it aligns well with how they envision react-router and redux integration. I think it will essentially replace redux-router and that will live as its own standalone project.

We're considering renaming it react-router-redux as it will be more official bindings. Unless anyone has any better ideas, I say we go with it.

[ellbee]

Will be great to have this project join rackt!

react-router-redux sounds good to me 👍

[kimjoar]

That's great! 👍 💯

[arkist]

good enough 🌟

[lukebennett]

👍

[omnidan]

Sounds good! Just have to make sure it's not too confusing to have two react/redux routers that sound almost the same too. (redux-router vs react-router-redux) That could be solved with documentation though. (explaining the differences between the two)

[choonkending]

I reckon go for it! Sounds exciting.

[jlongster]

I'm going to set a date for this: Wednesday. I'll think through anything we need to do before then.

[jlongster]

I stalled on this because I was worried about the rename, sync redux-router is also in rackt it seems like calling this react-router-redux is going to be super confusing.

@ryanflorence @mjackson Are you all sure you want to rename this? If so, I feel like we should either rename redux-router or do something so that it's not so confusing which is which.

[MattKunze]

Any reason to switch away from redux-simple-router? I usually cringe when things have "simple" in the name (argh SOAP!), but it actually seems warranted in this case

[jlongster]

I think Ryan and Michael want it to be more "official" bindings. But I suspect with enough community feedback they might be fine keeping the name.

[gaearon]

Maybe we can find a different name for redux-router too?

[ryanflorence]

We're removing the current redux-router from rackt, so there shouldn't be any confusion.