I was recently asked by the Argus Leader, a local newspaper in Sioux Falls, to give my two cents on the controversial South Dakota #DontJerkandDrive campaign. Since then the article has been syndicated out to USA Today and other publications. It seems that I caught the attention of a reporter when I labeled the campaign as "brilliant" on Twitter.
— Bryan Ruby (@MrBryanRuby) December 9, 2014
The word on the street is that the State of South Dakota is pulling back on this specific campaign. I can't say I'm surprised. I understood the gamble Lee Axdahl, the Director of the Office of Highway Safety, was taking when he signed on to this marketing strategy.
Bryan Ruby, owner of the web consulting business CMS Report, was impressed with the campaign from a marketing standpoint. Online, he called it "brilliant."
When I talk about Drupal, information technology and the weather all in the same breath, I get a little excited. I can't help myself. I'm biased toward Drupal as it is one of my favorite content management systems. I'm also a former meteorologist working in information technology for a very large organization that is heavily involved with the weather. Needless to say, a year or two ago when I heard that The Weather Channel started using Drupal to meet the needs of it's customers and meteorologists, it caught my attention. I think the use of Drupal is a win-win for everyone around and given my background, I wish my own employer had adopted a similar solution. I think organizations miss out on a lot when they don't utilize open source or even proprietary systems in favor of an in-house CMS.
The news keeps getting better if you're a Drupal fan. Last month, both Acquia and Mediacurrent announced that The Weather Channel is standardizing on the Acquia Platform for Weather.com. Weather.com started using Drupal last year to increase the agility of its content creation and publishing. Now, the company has moved the entire website, which serves more than 20 million pages of content, to the Acquia Platform, which brings together Drupal and Acquia’s solutions for digital engagement and experience management. The team at Weather.com worked with Acquia and digital agency partner Mediacurrent for its site development and migration from its legacy web content management system Percussion.
For the first time in 15 years, my family doesn't have a website to call their own. In January 2000, I registered the domain Bryansplace.com. This was the first website I ever built outside of work and it became a sandbox for me to express my interests as well as a way to seek personal growth. From handwritten HTML pages into Frontpage to a number of CMSs, the software and content at Bryansplace evolved as my life evolved.
Bryansplace.com was the website where my girlfriend and I announced our marriage to the world. As a married couple, we eventually publicly announced the birth of our son via the site. This domain was the site where I talked about camping, computers, and my latest beer recipes. It wasn't all about me either. My wife showcased her photography for the first time online via Bryansplace. This was also the website my son learned how to navigate the Drupal content management system and talk about his gaming skills. Bryansplace.com was synonymous with "family news". Despite how much I valued the domain, last week I unceremoniously killed the website.
Over the years, I've made it an unwritten policy not to sensationalize bug fixes and security vulnerabilities in content management systems. While there may be great interest in such stories, I believe such stories have a tendency to cause more harm than good. When sensationalized, such articles tend to cause customers to address security concerns with emotion instead of logic which is never a good thing. So, when the security vulnerability known as "Drupageddon" broke and Drupal developer Bevan Rudge posted "Your Drupal website has a backdoor", I knew this story was going to eventually reach mainstream media. In the meantime, I've been struggling on how best to write this article and what story need to be told.
For those that don't know, Drupageddon is the highly critical SQL injection vulnerability in Drupal 7 core and was fully disclosed by the Drupal Security Team in SA-CORE-2014-005. Since the dawn of time when databases were introduced to websites, SQL injection vulnerabilities have been discovered and in the majority of cases when found are patched by their developers and system administrators. What makes Drupageddon particularly nasty is the vulnerability can be exploited by users not even logged into your site (in Drupal they're called anonymous users). Worse, if you didn't update your site quickly enough, your site may still be compromised even after applying the fix (in Drupal 7.32 or later versions).