Move to a composer based workflow and seperate base from profiles

[NormySan]

I propose that we move the 7.x version of odddrupal to a composer based workfow similar to the 8.x branch.

I also propose that we separate out each profile into it's own repository since a profile is really like a module.

If there is a consensus on this change i propose this is released as a 3.x version of the 7.x branch.

Packages handled by: https://packagist.drupal-composer.org/
Existing implementation like the one i propose: https://github.com/drupal-composer/drupal-project/tree/7.x

Possible pros:

• Modules are no longer versioned in git === smaller repositories and possibly faster deployments.
• Patches could most likely be applied automatically by composer (works with Drupal 8 at least).
• Moving the profiles out to custom repositories lets us separate concerns. The base installation should IOM not contain profiles but should instead load them through composer.
• Each profile can have it's own dependencies through composer and the site would automatically install the profiles packages also.
• Get access to packages from the PHP packages at https://packagist.org/.

Possible cons:

• Drupal packagist is down and modules can not be installed/updated.

This changes would require more investigation to see if it's a real possibility and what other pros/cons we can find.

[olofbokedal]

I think this would be a great improvement since it allows for a much more flexible approach to the site structure.

But I think that we should focus on this for Drupal 8, and then backport the solution to Drupal 7 if we can provide a reasonable upgrade path for existing sites.

Thoughts?

[NormySan]

Sounds like a sound plan, just like we previously discussed.