* Make sure package is published under @elastic org namespace
* Preparing packages/ for Kibana-related packages
* Folder structure mirrors package name
* Add note on naming consistency
* s/packages/node modules/ for removing potention confusion with Kibana system packages
* Prefixing the eslint rule with package scope (i.e. org namespace)
* Adding README
* Bumping up version for release
* Adding repository information to package.json
* Bumping up version for release
* URL-encoding repository link + bumping up version for release
* Using published version