It has been a long time since I had anything to report about eGroupWare, an enterprise groupware package.  It also doesn't help that I haven't used the software for about a year.  However, eGroupWare 1.6 Final was released last week giving us some new news.

New additions and improvements in eGroupWare 1.6 include:

• Complete new implementation of the filemanager DMS by means of PHP stream-wrapper and WebDAV, ACL control on directories and files - the new architecture allows now uploading of big files.
• Implementation of new functions like multiple mail accounts and many bugfixes in the email client.
• Extensive new features for the tracker-application: for example escalation-matrix for tickets and automatic mail-conversion as a ticket.
• Improved calendar functions
• Supplements and adaptations in the addressbook like appointment-view, custom fields, distribution lists shown in the contact directly and in the addressbook list, multiple categorization of contacts in the addressbook list.
• Improvement of the template functionality of the project manager and some bugfixes.
• New theme for the 1.6 release

All package types are available from eGroupWare's download page.

"From mid December 2007 on, you can get a printed User Manual in English
language, beside the German one available since some years.

The User Manual Version 1.4 contains several descriptions of
the eGroupWare applications and one Chapter about "getting started" in
the popular eGroupWare modules. The manual has 180 pages and nearly 110
colored screenshots."

Complete Story

I mentioned not long ago reading that there are an estimated 1700 applications on the market for content management systems. In an ideal world, I would love to cover them all here at CMS Report. In the real world, I just don't have time to put focus on every single thing involving content management system (CMS).

I have and will try my best to spend the time browsing the Internet and reading the trade journals for stories that may interest you. I'm grateful for stories or links that readers have also submitted though the contact page. I can't recall a single legitimate story or request that I've received in my mailbag that I didn't publish, no matter how known or unknown the CMS of interest may be to the rest us. I'm also hoping to roll out some additional ways that you, the reader, may contribute to the stories we post here at the site.

I'm just catching up on the eGroupWare news.  For those that may not have noticed, a bugfix and maintenance release for the 1.2 branch of eGroupWare went out last month.  The changes/fixes included:

• PHP5.2 compatibility
• various fixes in the calendar
• PostgreSQL 8.1 compatibility
• Setup/LDAP import fixed
  

My place of business has started using eGroupWare for the IT folks so you can expect more coverage by me of eGroupWare than you've seen in the past.

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 poen source applications are using CVS, perhaps there is some validity in choosing CVS over SVN.

Regardless, it is hard to ignore the popular trend of moving to SVN for some of it's more "modern" features (so I've been told). A number of developers in my own organization have also mentioned there own projects either using SVN or in the process of moving from CVS to SVN. However, it doesn't seem to be an easy decision as I have seen a number of posts lately indicating the internal struggles that go with making such a decision. For example, Paul Reed from Mozilla, had this to say about a possible move by Mozilla to shift their code off of CVS and on to SVN: