Improving the use of Composer in Drupal 8

Now that Drupal 8 has many external dependencies Composer is one of the key elements for managing these. Commands such as 'composer update' are ran by a core maintainer, and the vendor directory created is committed to the Drupal core git repo. There are a number of issues looking at things like, removing the vendor directory from the Drupal core git repo, getting testbot to run composer install, getting the d.o packager to run composer install, where should the vendor directory be, how many vendor directories should there be etc etc, the list goes on.

This session will look at:

• What is Composer?
• How other PHP projects use Composer?
• How Drupal 8 currently uses Composer?
• How can we improve how Drupal 8 uses Composer?

What we need to think about is not just the core development and the external dependencies in core, but also how development shops, companies and corporations will be using and deploying Drupal. I'm sure there will be ways in which Composer will play a key part in building, maintaining and updating Drupal 8 sites. Depending on how you use Drupal 8 you may or may even use Composer at all.

I have blogged a little about this already.