Dan Montgomery

Since Capybara has added support for Headless Chrome and calls it `:selenium_chrome_headless`, here is what you can use in a `/support/*.rb` file, ``` # Add support for Headless Chrome screenshots....

I'm getting the same issues here. ``` rm composer.lock composer clearcache composer install --prefer-source ``` It wants to use `alpha1` for Reservoir and I get the same patch issue. :(

I also tried pinning to `alpha2` for an existing project and got errors. ``` composer require acquia/reservoir:^1.0.0-alpha2@alpha --no-update rm composer.lock rm -rf vendor composer clearcache composer install --prefer-source ``` Error...

The approach we have found to be the best in other situations is to have the profile contain two separate pieces. One is the list of contributed modules and glue...

I want to put together a better response in a few days perhaps. The short of it is that Reservoir can be curated. If there is a large enough user...

See https://github.com/acquia/reservoir/issues/33 I delete the part of Reservoir that installs default content and then I can install from configuration.

This makes sense at some level, but the spec seems to say that you need both `type` and `id` and that's not the case. You don't need to provide `type`...

I guess the idea is that everyone should provide `id` and `type` even if they don't need to since that's the specification. It seems like Drupal doesn't require both right...

I deleted the check temporarily in `prepare-iso.sh`.

Made a new issue #27 for the OSX 10.11 issue.