Suggestion to rename the package

[xcambar]

In my company, we use this plugin as our base set of rules for all our JS projects.

Many of our newcomers don't understand though why, in a non-Ember project, we use a set of rules "for Ember". This is until they read the code and realise that this plugin is a global set of rules with only very little specifics for Ember:

• a configuration for no-direct-property-access
• the rule require-const-for-ember-property

This led me to wondering whether it could a good idea to rename the project so it reflects better what it is and what is, IMO, the best description of the project, as per the README:

a recommended configuration based on DockYard's styleguide.

So, how about eslint-plugin-dockyard?

[brzpegasus]

This has been in the back of my mind, and I've been wanting to gather consensus within the team on moving in that direction as well. The name of ember-suave was carried over from the previous, JSCS-based version of this repo for no other reason than continuity, but eslint-plugin-dockyard makes total sense.

[bcardarella]

If the project is being renamed can a patch release still be done under this project that emits a warning telling people about the new name and that they should switch?