rename gem and namespace everything

[grosser]

fixes#19

@geemus

[geemus]

Looks like a great start. Should we add instructions on migrating from the old stuff in the readme?

Also, so we are on the same page about the broader plan of attack. Something like?

• We will do something with the old gem to either warn or something? I feel like this part might be ambiguous. Given the namespace changes and whatnot, I'm not sure there is a "just works" version. Maybe we should just add a post-install message to the existing gem which says (this is deprecated, please now use this/see these instructions)?
• We will merge/release this, establishing the first version of the new gem. (depending on what we do with old gem, this might need to come first).

[grosser]

I think it's pretty obvious what needs to be done to migrate.
post-install messages are annoying ... don't use them for the new gem ... but for the old gem that should be fine.

Always safe to release the new gem.

After that release the old gem with only a dependency to the new gem (maybe with a major version bump) ... and we are done.

[geemus]

@grosser cool, thanks for confirming. We have a couple other related things in flight, but hope to circle back and resolve this relatively soon.

[backus]

Any update here? Would be much nicer to have the top level namespace be Heroku when using this gem

[grosser]

I can rebase if it's ready to be merged ...