The concept

Suppose you've got very unique features/functionality for your site or application... Or you've got an extremely custom integration with a third-party service. Or you're non-trivially forking an existing Drupal extension... Or you're working with non-GPL compatible code.

All code is debt, but eventually, we have to write it. Let's talk about strategies and best practices for maintaining your custom Drupal extensions within your organization.

The details

• Breaking apart a monolithic codebase into discrete, maintainable projects (and maintaining commit history)
• Architectural decisions: prioritizing portability, reducing dependencies.
• Development workflows: advantages and disadvantages of git submodules and git subtree
• Taking full advantage of drush package management and the core Update module
• Automated testing outside of drupal.org