Strategies for streamlining multi-developer development workflows
Imagine this scenario:
A group of 3 developers are working on a Drupal site, deadlines are tight, and you want to work as efficiently as possible. But, wait, Drupal doesn't really make it easy for multiple developers to work on the same site. HALP!!!
The purpose of this session is to begin a dialogue about the problems that arise with multi-developer Drupal development/implementation. It is not intended to provide the end-all-be-all solution to these problems.
This session will discuss ideas and strategies to employ that should help ease some of the pain-points present when building a complex Drupal site. We won't be talking in depth about code or config, but rather discussing several modules and techniques at a high-level 10,000 foot view that can be combined to make this process easier to manage, less stressful, and hopefully more successful.
Topics of discussion will include:
- Explaining the problem(s) with Multi-Developer Drupal development
- Sharing a single database vs. separate databases - pros & cons of each approach
- Tools that ease the pain: Drush, Install Profiles, Features, etc.
The should also be a fair amount of time for Q&A and a semi-open discussion. I don't have all the answers, my hope with this session is to discuss my ideas, and get your feedback in hope of all of us having a better idea of how to address the problem - and what needs to be fixed in future versions of Drupal to eliminate the problem.