By golly, I have been so busy the past couple weeks that I didn't even had a chance to check out a beta of Wordpress 2.2.  Now it's too late for me because Wordpress 2.2 has been officially released.  Not only does this release include over 200 bug fixes, but it also has some new nifty features.

• WordPress Widgets allowing you to easily rearrange and customize areas of your weblog (usually sidebars) with drag-and-drop simplicity.
• Full Atom support, including updating our Atom feeds to use the 1.0 standard spec and including an implementation of the Atom Publishing API to complement the XML-RPC interface.
• A new Blogger importer that is able to handle the latest version of Google’s Blogger product and seamlessly import posts and comments without any user interaction beyond entering your login.

I'm currently in the process of moving CMS Report and some other sites I manage to a new VPS.  The original reason for the change was to move my sites off of a legacy version of Linux (Fedora Core 2).  However, I'm also making the server change because of too much bleeding edge experimentation by yours truly that has brought my server's stability into question.  Believe it or not, a reboot of the server doesn't fix everything!

Those that have followed my writings (even from the WebCMSForum days) know I've spent about the past year or two dealing with an aging  PC.  Even the wife, who doesn't always appreciate the geek part of her husband, says it is time for a computer upgrade.  When she says it's time, you know the deadline is near to order up a new computer.

For the past several years I've configured my home PCs with a dual-boot of Windows/Linux.  While there are some things I don't like about Apple's propriety hardware for it's OS, the need for something different has me considering purchasing a Mac.  However, as I posted at the Open Source Community, I've started to wonder if over time the desktops for Linux and the Mac won't be that much different from one another.

KDE 4.0: Why I likely won't get a Mac -

Desktop Linux has an article and shapshots out on the first alpha version of KDE 4.0. The article is titled, KDE 4.0 alpha arrives!.

Features in this alpha version of KDE include:

• A new visual appearance through Oxygen (think Aqua)

Plone 3 beta 3 was released on Wednesday of this week.  The announcement posted at Plone.org also invited users, administrators, and developers to help test the new software.  Plone 3, built on the Zope application server, is nearing a year of development .  By the time the final version of Plone 3 is released you should see the following new features included in the content management system.

• Full versioning, roll-back capabilities, in-place staging (ie. working copy support) and locking for all content.
• Inline editing of content using Ajax.
• Link integrity checking and automatic handling of moved or renamed content.

Until this post by Nick Lewis, I've been in the camp with the folks that say PHP-based content management systems such as Drupal should be compatible with both PHP 4 and PHP 5.   After reading his post, I'm convinced he's correct that new development should be geared toward PHP 5.  It's hard to fight for the future when you continue to hold on to the past...

Should Drupal move to PHP 5?

In one word: absolutely.

In one sentence: if we don't, the drupal project will die along with PHP.

CMS Watch has a very good article on their site titled, "Question CMS Consolidation". The article serves as a reminder for IT and managers that, although technically feasible, an organization may not want to put everyone on the same content management system (CMS).  Why would an organization want to to consolidate their systems in the first place?  For those at top of the organization there may be some obvious reasons to unify the organization onto a single CMS.

Many organizations are looking at a portfolio of dozens of content management systems running somewhere on their network. From sheer tidiness alone, it’d be nice to have a shorter list. And such tidiness can have real benefits: better negotiating leverage with vendors, reduced overhead to manage contracts, reductions in the number of servers and hence in datacenter space (with attendant power and operational costs), and so on. Finally, increased demands for compliance and control are placing a premium on simplifying information management.

In my own organization, we have had both Internet and intranet servers since the mid 1990's supporting operations and administrators.  While we moved our Internet web servers onto a CMS a few years ago, it is only the past few months that many of our offices and departments have shifted their intranet from static pages to much more dynamic system.  As many of our field offices migrate their servers to utilizing newer Web 2.0 and collaboration applications, IT and management have a strong desire to consolidate those applications and servers.

CiviCRM 1.7 has been released. The CiviCRM is the "first open source and freely downloadable constituent relationship management solution". CiviCRM is web-based (integrating with Joomla! or Drupal), internationalised, and designed to meet the needs of advocacy, non-profit and non-governmental groups.

The following are highlights for CivicCRM 1.7:

"Brad" from Joomla! wrote "RobInk hit the big 10k posts  today." at the Joomla! forum.  He goes on to write:

There is a thread going where you might like to add you congratulations etc.

It’s incredible to reflect upon just how many people have been helped by Rob’s posts, as well as the posts of all those who help out. Did you know, we have 28 members at the moment who have 2000 posts and above, and more than 70 with 1000 posts or more. Now that is CONTRIBUTING!

A special congratulations to Rob, and to everyone else THANKS for your continued help and support.