During a meeting about training today, one of my colleagues and I were discussing how the same taxonomy could apply to several different “bodies of knowledge” about Acquia and Drupal. We’re envisioning a taxonomy that could organize a “Drupal Body of Knowledge” collection (akin to the PMBOK), training curricula, a certification exam, and a knowledgebase.

WSJ travel columnist Scott McCartney offers his plea for how President-elect Obama can simplify the lives of business travelers by splitting the FAA into two different arms—one for regulation and the other for air traffic control and management.

He recommends that President Obama work to create the latter entity as a quasi-government organization or a non-profit corporation like those in Australia, Canada, and the UK.
read more

I just finished listening to Karl Susman on Sound Policy with Denise Howell. A worrying trend that Karl points out is that homeowner’s claims related to blogging liability were being paid out for some time, and now there aren’t any being paid out. As an insurance agent, his take on this is that blogging, podcasting, and other online participation are no longer covered by homeowner’s policies. Of course, there are now some custom policies available for bloggers.

Earlier in the cast, he mentioned that blogging and related activities are also entering into corporate policy negotiations. Most of the corporate liability policies he’s working on (in CA) explicitly do not cover liability related to online publishing activities—or offering very minimal coverage.

The CMS Watch Trendwatch blog had a post yesterday on when the project honeymoon ends. We’ve all experienced this—when our relationship with clients shifts from “how can we help them succeed” to “how do we keep from bleeding money.” I think a big part of this is our failure to estimate well, and the fact that we prepare a big statement of work up from (BSOWUF? cf. BDUF).

QuickArrow has made a great library of 35 must read PS whitepapers available on their site. The collection includes some papers from TPSA director Thomas Lah, PSVillage advisory board member Jeanne Urich, Charles Green from Trusted Advisor Associates, and more.

I spent the morning today documenting the practice development activities for Acquia services. I started out working in Project X which I decided to try after seeing the icon in Andrew’s dock. It turned out to be a terrible time to try a new tool, since the ideas were coming too fast and I was handicapped by the learning curve. I thought of switching back to OmniPlan, which I’ve been using since it came out.

Joining Acquia not only marks the earliest stage that I’ve joined a company, but also the first time I’ve joined a commercial Open Source company. This was one of the main reasons I chose to join the company. Managing a services business at an Open Source software company creates some interesting challenges compared to my past experience in traditional software and consulting businesses.

• There’s more than one culture to adapt to. When you join an Open Source company, you not only need to adjust to your company’s culture, but you need to become an active member of the Open Source community. At an early stage, the cultures are likely to be quite similar—but its not guaranteed. Even with compatible cultures, you’re still dealing with two sets of personalities and the politics that come any time you get people together.
  

One of my responsibilities at Acquia is overseeing the development of our certification program. We’re creating this program to establish baseline credentials for working with our commercially supported distribution of Drupal (codenamed Carbon) and our Spokes and Caliper network services. Since Carbon is a distribution of Drupal core and a selection of modules, Acquia certification will judge facility to work with Drupal independent of our distribution.

I’ve owned the domain name “chuckdantonio.com” for a couple of years now, but the time for tool selection, installation, and keeping up a quality blog always eluded me. Now that I’ve joined Acquia, I’m able to make the time to launch the site with Drupal. I started to get acquainted with Drupal during the interview process, then gulped from the firehose during two days at Drupalcon Boston and haven’t stopped gulping on my first few days on the job.