It's way too easy to get flamboyantly excited about all the shiny new tools and accompanying buzz-words that are emerging from the devops realm -- Configuration management tools like Puppy & Chet are all the rage, and you've probably heard the hullabaloo about managing virtual machines using Hobos. These tools are important, but I contend that this is only insofar as they allow us to share culture and processes more openly than ever before. And as a community, we have not been harnessing this opportunity presented to us.

The wonderful thing about configuration management tools like Chef and Puppet is that they allow us to share processes and culture just like we share code. I'd like to speak about how we can build tools that allow our community to pool resources & vision for our toolchains, just as we pool resources & vision for the CMS we build together.

As a community, we spend a lot of time talking to one another about how we roll, but less time working together to build tools that help us roll that way together.

We'll touch on:

• empowering teams through tools designed to put them in control and remove obstacles
• sharing culture and philosophy within the Drupal community through shared toolchains
• taking a run-down of current tool offerings with an eye for how efforts can be merged
• tackle the elephant in the room that is our beloved collection of NIH-themed tools
• high-level showcasing of some in-house open source tools, with emphasis on the philosophy behind each (reproducibility, DRY principles between local development and remote servers, decomposability)
• specific focus on Jenkins-based Inception tool to promote continuous delivery build pipeline processes
• specific focus on potential of Vagrant-based tools (like our Ariadne tool) for managing both local VM dev environments and deployed servers
• discuss ways to reverse the dividing tendencies of the Chef vs Puppet camps