Florian Weber

Hi, i think this project has its purpose. Here are a few differences to the official template: - Ships with drush and Drupal console - Ships with dev dependencies (testing...

I think inline package definitions are not a best practice. We should at least mention the limitations. See the blue box on https://getcomposer.org/doc/05-repositories.md#package-2

@joelpittet You could try to creata a subclass \Drupal\Core\Composer\Composer and override \Drupal\Core\Composer\Composer::$packageToCleanup. Add add the subclass to your composer.json as additional script.

I get the concern about the permissions but Drupal will adjust it automatically during installation and bootstrap. see `drupal_verify_install_file()` in `system_requirements()`.

It looks like we are trying to support multiple use-cases with ``ScriptHandler::createRequiredFiles``. I never had those issues, because the script does not run on my production server it runs in...

D8 is not supported anymore.

Not relying on dev dependencies is a good thing, and i thought about a tagging releases in the fast. But i had trouble finding the a proper version scheme, that...

I would go with `web`. Many people use the template already for D7 and D8. `web` is default in https://github.com/symfony/symfony-standard as well.

@weitzman Maybe we can revisit this issue and provide a template without the scaffolding files after #77 went in.

We could follow symfonys model and add some extra config to our composer.json and use in our ScriptHandler. see https://github.com/symfony/symfony-standard/blob/master/composer.json#L53