I have been keeping an eye lately on two version control systems, Subversion (SVN) and Concurrent Versions System (CVS). My sudden interest in version control is due to a project team I'm on for my organization. The team is in the early phases of project management and needing to pick either CVS or SVN. At this time we are leaning toward SVN.
I'll admit, I have some hesitancy to commit to SVN. The reasons for my hesitancy likely has more to do with personal reasons and likely less organizational needs. Some of my favorite open source project, including Drupal, are still using CVS. I'm not sure we'll be using Drupal for this project, but there are bound to be some open source applications we end up using where the code is still stored on CVS. If the developers of the open source applications are using CVS, perhaps there is some validity in choosing CVS over SVN.
Sigh...another round of security updates coming from the folks at Mozilla. It looks like version 220.127.116.11 will be at our doorsteps soon. Now at home, updating Firefox and Thunderbird on the Windows PC is a snap since it is all automatic. However, updating in a secure enterprise environment is a different matter.
In most enterprises, most users don't have administrative privileges and without those rights Firefox and Thunderbird in most cases will not auto install the new version. What would really help is if Mozilla would provide their software in a MSI package. Until MSI packages are provided by Mozilla, it is difficult for me to accept Firefox and Thunderbird as "enterprise software". In a Windows Server 2003 environment, MSI packages are a must for easy deployment, management, and auditing.
Serendipity's own Garvin has some helpful hints. While only those using the blogging application Serendipity will likely only have interest in this post, I thought I would post it up front anyway. There have not been a huge amount of real news from the various blogging applications except for a couple exceptions. Regardless, I like to promote blogging applications as much as I can.
While blogs are really just a subset of content management systems (CMS), they have played a significant role in getting people comfortable to using a modern CMS to drive their Websites. Let's face it, many of us really would not have trusted a database to manage our Web sites and replace our trusty HTML files until we saw how blogs worked. We owe a lot to blogging applications such as Wordpress, Serendipity, and Nucleus.
So with no more delay here is an excerpt regarding one of our favorite blogging applications:
For ages, Serendipity has given users the flexibility to move around plugins in the left/right sidebar. Two sidebars were a usual concept for blogs in the days past, and for surely some more days to come.
As some of you may have noticed, I returned a few days ago from my low-tech week. It's taking me awhile to adjust being stuck at the computer so you'll have to bear with me. It's been tough enough to spend the PC time at work, so spending my "free time" on the PC is challenging. It's kind of like not eating fast food for a week and then suddenly having to ingest it for every meal. Drupal addict and Yoga for Geeks guru, Sarah Pullman, mentioned a similar experience in one of her posts. To add insult to injury, I blew up three sites on my VPS and had to put the pieces back together.
A new version of SMF has been released to the public, SMF 1.1 RC3. For users of the forum software, this has been an unusually long period of time for waiting to see a new release candidate of the software.
As the title says, phpBB 3.0 (code name Olympus) is now out as a second beta. I see a lot of encouraging things about phpBB 3.0 and it will likely be seen as a big improvement over 2.x. The features and improvements to phpBB from version 2.x to 3.x are numerous and I'll probably chat about them as 3.0 near its actual actual release date.
The only comment I'll really make here is...I'm sure glad I didn't build a near production site on phpBB 3.0 Beta1. If you read the few lines below you'll see that no update path is offered between the first and second beta. Ouch!
We are pleased to announce the availability of the phpBB3 Beta2 package. With this second beta release we are a great step forward.
There is no update path provided due to a number of extensive database schema changes. Everyone having the first beta installed need to re-install the software. If you do a new installation, please be sure to also remove any remaining files, especially those within the cache folder. Complete Story
The past couple days has been a busy time for those involved in the Rails open source project. Just as busy as the Rails core developers were the users running Ruby on Rails applications (such the Radiant content management system). On Wednesday, the project's developers released Rails 1.1.5. In the announcement of the Rails release, David August called upgrading the new version "mandatory" since the security vulnerability was so severe. However, he didn't want to go into the details to the exact nature of the vulnerability and only stated that, "The issue is in fact of such a criticality that we’re not going to dig into the specifics. No need to arm would-be assailants."
I'm working on an ecommerce site using osCommerce to enable the shopping cart functionality for my client's online store. This is the first time I've used osCommerce so I'm still working on improving my comfort level with the application. osCommerce is open source and released under the GNU General Public License. According to the osCommerce site:
"The label 2.0 has become so overused that it is now a tic, a reflex action, a device that gets trotted out because someone thinks it sounds both hip and techie. And it did — for a while. Now it’s tired."
Given that this site, CMS Report, is less than six months old...I am truly amazed with the number of visitors the site receives in a day. While the number of visitors may be small compared to other well known sites, this is the first time I've had a site of my own that has drawn some attention. What a cool experience this has been!
I was flattered to see Drupal blogger, Greg Knaddison, mention CMS Report in one of his posts. Mr. Knaddison could have chosen for discussion so many other Drupal sites but for whatever reason he likes what he sees here. However, as postive as his message was for CMS Report, he also indicated through his post that the current mix of original content and aggregated news isn't for him.
With a tip of the hat to CMSReport. CMS report aggregates lots of content about all CMS, but they also have some original content. I'd prefer more of the latter and less of the former, but that's just me.
While CMS Report still needs to evolve and mature, its purpose was defined from the beginning. The primary mission of the site is to inform readers of the latest happenings in the world of content management systems. Now how that job gets done is another matter and readers have preferences.