Merge branch 'develop'
README.md: Remove duplicate cssjanus NPM global package
Merge pull request #2 from ntwb/patch-1

README.md: Remove duplicate cssjanus NPM global package install instruction
Update aliases.yaml

Run `composer install` so that only tested versions of dependencies are loaded as opposed to potentially newer, untested versions.  Reference: https://github.com/FlagshipWP/Compass/pull/1#issuecomment-57935072
Merge pull request #3 from wpscholar/patch-1

Update aliases.yaml
Update composer.json

The 'name' and 'description' properties are required in the composer.json file and will allow others to use this project as a dependency. (https://getcomposer.org/doc/04-schema.md#name).
Merge pull request #4 from wpscholar/patch-2

Update composer.json
Update composer.json

Updated "type" to be "wordpress-theme" to make the project compatible with https://github.com/composer/installers
Merge pull request #6 from wpscholar/patch-3

Update composer.json
Reload Grunt task grunt:watch when configuration changes

When a Grunt configuration change is detected whilst running Grunt task `grunt watch` the watch task should be reloaded with the updated configuration.

See: https://www.npmjs.org/package/grunt-contrib-watch#options-reload
Add .gitattributes file to deal with line endings

When running `grunt check` after cloning the repo and installing dependencies the Grunt JSCS tasks `grunt jscs:assets` and `grunt jscs:grunt` fail with 33 errors `Invalid line break at filename.js` (Where filename.js is any of the 33 JavaScript files included in the Compass repo, the exception is `/grunt/log.js` as it is not included in task files list)

In my personal global `.gitconfig` I set `autocrlf = true` which has in the past dealt with the vast majority of newline (LF/CR/CRLF) issues with GitHub repo's and Windows though in this case with Compass it does not.

If I change the change the `"validateLineBreaks": "LF",` rule in `.jscsrc` to `CRLF` then the JSCS Grunt tasks pass without error and without a `.gitattributes` file per this patch, this is why I went with the `.gitattributes` patch to explicitly declare line endings for the COmpass repo.

See also: https://help.github.com/articles/dealing-with-line-endings/
.jscsrc indentation clenup

The `.jscsrc` was using mixed tabs and spaces for indentation, this pull request fixes all indentation to spaces per the spec.

See also: JSON and YAML files should use spaces not tabs for indentation http://yaml.org/spec/1.2/spec.html#id2777534

p.s. Not sure why any of the linters did not pick this up, will dig around that as I continue exploring the Compass repo :wink:
Include JSON file .jscsrc in Grunt task grunt:jsonlint



See also: https://github.com/FlagshipWP/Compass/pull/11
Truly global config change

Composer doc instructions demand that the `-g` flag is used when using
the `config` command. Using `composer global config` opens up
composer.json. The result of this PR is the opening of config.json.
Update JSON files to use two-space indentation, per WP Coding Standards

See https://github.com/FlagshipWP/Compass/pull/11
Merge pull request #14 from joshlevinson/master

Truly global config change
Merge pull request #11 from ntwb/patch-3

.jscsrc indentation clenup
Merge pull request #12 from ntwb/patch-4

Include JSON file .jscsrc in Grunt task grunt:jsonlint
Merge pull request #15 from GaryJones/two-space-indents

Update JSON files to use two-space indentation, per WP Coding Standards
Merge pull request #9 from ntwb/patch-1

Reload Grunt task grunt:watch when configuration changes