Last week the Acquia Engineering team assembled in the office for a week of brainstorming, coding, and fun.
As Senior Director of Solutions Architecture at Acquia, Christian Yates makes sure that Drupal is able to compete head-to-head with any and all competing technologies. He translates organizations' business needs into a vision of how Drupal can solve the large-scale, complex problems that large organizations face. Since showing and doing is always better than saying, he also builds proofs-of-concept in working code to help get them on board with Drupal.
Kent Gale, Senior Director of the Client Advisory Team is on the front lines of keeping Acquia's clients happy and productive: "Every day is a pretty intensive exercise in making customers successful ... one way or the other ... either helping them develop, or deploy or maintain and manage their site."
Kenny Silanskas, Acquia's Tier 1 Team Manager, has a passion for getting Drupal right that rubs off on his team – Acquia's crew of frontline Client Advisers. They are in the happy position of being able to train client-developers in best practices, choosing and using the right Drupal modules, how to use the open source process, and more. Kenny says, "The Support Department gives Drupal sites the TLC they need." All of this results in happier and more successful Drupal users and a healthier Drupal project.
In 2004, Peter Wolanin, then a full-time scientist, discovered Drupal while volunteering on a political campaign and building its website. As he puts it, the road to becoming a full-time software engineer at Acquia started when he discovered that "pretty soon, I got more interested in fixing the bugs than building the site ... "The satisfaction of fixing things sort of drew me in."
As a result of Randy Fay's blog posts and Drupalcon Denver core conversation on Drupal governance (see show notes for links), Dries Buytaert convened a working group to define the first steps in the refinement of Drupal governance. In this episode, I sit down with the working group members to talk about what they have been working on, what they have accomplished, and what the next steps are in defining what governance in the Drupal community should look like.