My back hurts. As with the rest of the United States, my neck of the woods has received more snow and cold weather than one could possibly want for the winter season. Due to the constant snowfall, I have spent a number of my days clearing my driveway from snow with the help of my 15 year old snow blower. Several days ago, the snow blower's auger died on me leaving me with a useless rusting piece of machinery.

Auger Belts

1. Remove the plastic belt cover on the front of the engine by removing two self-tapping screws. See figure 23.

2. Drain the gasoline from the snow thrower or place a piece of plastic under the gas cap.

The death of my snow blower couldn't have come at a worse time. Most stores in my area have already sold out their snow blowers for the season. The waiting list is long for seeing a small-machine mechanic to fix this heap of metal. I didn't even bother calling knowing full well I likely wouldn't even hear from the mechanic until March whether this snow blower was fixable or not.

3. Tip the snow thrower up and foward so that it rests on the housing.

4. Remove six self tapping screws from the frame cover underneath the snow thrower.

There was only one option left, I needed to fix the MTD 22 inch 5HP Snow Blower myself. I would need to start with a replacement part, Auger Belt OEM-754-0430.

5. Roll the front and rear auger belts off the engine pulley. See figure 24.

6. Unhook the idler spring from the hex bolt on the auger housing. See figure 25.

7. Unhook the support bracket spring from the frame.

The problem is that I'm not a mechanic but an information technologist. Not a single computer processor can be found on this snow blower. No keyboard, no user interface, and no scripting language came supplied with this equipment. They say manuals for computers can be confusing, but have you ever tried to decipher an owner's manual from Cleveland, Ohio for a 1996 snow blower?

Note: it may be necessary to loosen the six nuts that connect the frame to the auger housing to aid in belt removal.

8. Lift the rear auger belt from the auger pulley and slip belt between the support bracket and auger pulley. See Figure 24. Repeat this step for the front auger.

9. Replace both auger drive belts by following instructions in reverse order.

Before there was YouTube and before there was Web 2.0, I would have resigned myself to spending the rest of this winter shoveling my driveway without the aid of a snow blower. But this isn't 1991, this is 2011. I can't think of a better moment in time to show positive proof the impact the modern Internet has for improving our daily lives. For if you ever find yourself in need to fix your snow blower, you can thank the social web as well as YouTube's Donyboy73 for reminding me once again that there is purpose in Web 2.0, social media, and information systems.

Without a doubt, my snow blower would have landed in the junk yard and my back ruined if it hadn't been for that video. Instead, I spent my Super Bowl Sunday knowing that the next time it snowed, I had a snow blower fixed and ready to be called back to duty. I am tech geek, hear me roar.

I like to keep things simple and prefer to use content management system (CMS) as the term used to describe the information system we use to manage all content. However, I will acknowledge that it is sometimes good to categorize a CMS by purpose. This differentiation of a CMS by purpose has given us subcategories of the CMS which include the enterprise content management system (ECM), the web content management system (WCM), and the social publishing system (social business system). In a press release this week, Alfresco introduced me to social content management, another new marketing term to describe a CMS with the purpose of managing social media.

Alfresco is tying to evolve the social content management system higher than the social publishing system within the information system food chain. If you ask them, a social content management system would do something much more than a social publishing system. I'm not convinced of that, but they do make a good argument.

Alfresco Enterprise 3.4 is purpose-built for managing content in a social world. Enterprises are increasingly deploying social business systems like Jive, Salesforce.com’s Chatter, Lotus Quickr, Drupal and Liferay, among others, in the hopes of making employees more effective. According to Alfresco, these social business systems are creating volumes of unmanaged content if left un-checked. Using open standards like CMIS & JSR-168, Alfresco Enterprise 3.4 is a content platform with a goal to co-exist with social business systems to help manage and retain the content created by social business systems.

The marketing team over at Alfresco are pure geniuses. In this case Alfresco is using the social business systems as another catch phrase to describe what I know to be social publishing systems. Alfresco on the other hand identifies their product as as a social content management system that co-exist to manage the social content created by all these other systems. A CMS that is needed to clean up after the mess created by all these other social publishing systems.  I'm not sure I buy the argument that there is much difference between a social content management system and a social publishing system. But I will bite that social content management has a much better ring to it than social publishing system or any other term we use to describe the management of social content.

From now on when I describe a CMS for the purpose of managing social content, I'll likely use the term social content management instead of social publishing system. It seems to be a more fitting term for describing the direction the CMS is currently evolving toward. So hats off to Alfresco for pushing this term in their marketing. In a CMS world where ECM and WCM can exist, I see no reason why there can't be a SCM. On face value, there is nothing wrong with this logic. Except, of course, I like to keep things simple and prefer to simply call all these information systems a content management system. However, who am I to argue with progress.

Last fall, I once again had the privilege of participating as a member of the judging panel for Packt Publishing's Open Source Awards. For the 2010 event, I participated by voting for the category of Open Source CMS Awards. In that award, the winner was declared by the panel to be CMS Made Simple, with SilverStripe as first runner up followed by MODx as second runner up.

I received a lot of inquiries asking me how and in what order did I rank the content management systems. Each of the judges on the panel, selects and ranks their top three CMS from the five included in this category. The judges are given a lot of reign for how they rank the CMS and may consider a number of factors including performance, usability, size and support from community, accessibility, ease of configuration, customization, scalability and security.

It has been my history to be transparent to all with how I rank each CMS as my vote will have some differences to those of the panel. This time around, I find myself hesitant and under personal protest with me providing information on how I ranked the five content management systems.

I question whether we're doing any good by declaring one CMS as better than another CMS. Dean Barker discussed on his blog some time ago this same uneasy feeling you get when you judge a CMS without having some reference to real world requirements. None of these content management systems would I consider losers and all of them remain worthy of future consideration. Yet, I'm disturbed that people will look at the numbers and interpret the results in a ways I never intended my rankings to be used.

My rankings for the Five Best Open Source CMS (with number one being the highest) were:

1. SilverStripe
2. mojoPortal
3. MODx
4. XOOPS and CMS Made Simple (Tie)

I'm not a firm believer in ties when it comes to ranking content management systems. Yet, this year I did just that for XOOPS and CMS Made Simple. All five content management systems that were reviewed I would consider as a candidate for a future project. None of the CMS would I consider a "last place" CMS so I refused to do so. It is also important to note that neither Drupal, Joomla!, or WordPress competed in this ranking as previous winners in this category duke it out in the Hall of Fame category.

After three years of open source development, Drupal 7 has finally been released to the public. As Ric Shreves previously mentioned in his article, there are literally hundreds of changes in Drupal 7. I've included below a list of the more significant changes from Drupal 6 to Drupal 7. I've also included a nice Drupal 7 marketing video via Jeff Robbins at the bottom of this post. Also there is always official Drupal 7 announcement for additional information on this latest version of Drupal.

Barring any unforseen changes to how I manage this site, I expect we will be upgrading CMSReport.com from Drupal 6 to Drupal 7 within the next few months. I've been playing with Drupal 7 off and on this past year, but I must confess I haven't been as aggressive in my testing of this version of Drupal as I was with Drupal 6.

Some of the more significant changes in Drupal 7 since the release of Drupal 6 include:

1. Overhaul of the User Interface

Work has been done to improve the user experience and administration interface. The new administration theme "Seven", the overlay module, the dashboard and the configurable shortcut bar, all lead to a much more user-friendly interface.

2. Custom Fields

Drupal 7 bundles in the ability to add custom fields, similar in functionality to the Content Construction Kit (CCK) module. However, fields are no longer limited only to content types; they can be added to users, taxonomy terms, and other entities. Fields also have support for translations.

3. Image Handling

Drupal 7 brings native image handling to core. Image fields may be added to content, and have image styles applied to them, such as scaling, cropping, and other effects.

I will be taking my annual break from technology. From now through August, I'll be posting and managing the site a little less. I won't be abandoning CMS Report, but you will be seeing me a little less.

During the summer months, I like to slow down my technology usage for a few weeks. I don't think as human beings we were meant to be immersed in the huge quantity of today's digital information. From the moment we are awake to the moment we go to bed, our bodies are being loaded with information. The email, cell phone, and the Internet seem to have a never ending presence in the lives of us IT folks. I don't have much control with removing technology from my work day, but I do have options in my personal life. It's time for me to unplug and officially begin Technology Break 2010.

Last week was a very frustrating time for me. For whatever reason, an unusually number of botnets decided to zero in on my Drupal site and created what I call an unintentional  Denial of Service attack (DOS). The attack was actually from spambots looking looking for script vulnerabilities found mainly in older versions of e107 and WordPress. Since the target of these spambots were non-Drupal pages, my Drupal site responded by delivering an unusually large number of "page not found" and "access denied" error pages. Eventually, these requests from a multitude of IPs were too many for my server to handle and for all intents and purposes the botnet attack caused a distributed denial of service that prevented me and my users from accessing the site.

These type of attacks on Drupal sites and numerous other content management systems are nothing new. However, my search at Drupal.org as well as Google didn't really find a solution that completely addressed my problem. Trying to prevent a DDoS attack isn't easy to begin with and at first the answers alluded me.

I originally looked at Drupal for the solution to my problems. While I've used Mollom for months, Mollom is designed to fight off comment spam while the bots attacking my sight were looking for script vulnerabilities that didn't exist. So with Mollom being the wrong tool to fight off this kind of attack, I decided to take a look at the Drupal contributed model Bad Behavior. Bad Behavior is a set of PHP scripts which prevents spambots from accessing your site by analyzing their actual HTTP requests and comparing them to profiles from known spambots then blocks such access and logs their attempts. I actually installed an "unofficial" version of the Bad Behavior module which packages the Bad Behavior 2.1 scripts and utilizes services from Project Honey Pot.

As I had already suspected, looking for Drupal to solve this botnet attack wasn't the answer. Pretty much all Bad Behavior did for me was to take the time Drupal was spending delivering "page not found" error pages and use it to deliver "access denied" error pages. My Drupal site is likely safer with the Bad Behavior module installed, but it was the wrong tool to help me reduce the botnets from overtaxing Drupal running on my server. Ideally, you would like to prevent the attacks ever reaching your server by taking a look at such things as the firewall, router, and switches. However, since I didn't have access to the hardware, I decided it was time to look at my Apache configuration.

Guidelight Business Solutions, a custom software and web strategy company based in Texas, has put together a little video highlighting their experience at last month's DrupalCon in San Francisco. The video does a good job in capturing the fun, scale, and pace of a Drupal conference. At the start of the video, you'll also see a snip of video of me taken during an interview while we were waiting for one of the keynote speakers to come on stage. I'm honored to be included in a video among so many of the other talented faces that were there for DrupalCon.

You can check out the video either below or at the website of Guidelight Business Solutions.