Blogs

I'm writing from the third day of the post-CiviCon code sprint in Truckee, California.  With 36 participants, we've divided into several groups focused upon making the upcoming CiviCRM 4.5 release as stable and useful as possible. Led by Dave Greenberg and Yashodha Chaku, our group has tackled several bugs and limitations, yielding a number of improvements in just a couple of days.

After having worked with CiviCRM for going on a year, I was excited to see the community around the project and learn more about others who are using CiviCRM. Initially, I questioned the risk vs. reward of traveling 3000 miles across the country and leaving my new business for so many days. As the time drew closer and I started digging deeper into the session descriptions I began to get excited.

I had fallen into technology almost by accident. As someone who enjoys delivering solutions I often find myself in conversations with people who are trying to build software infrastructures. It spawned a curiosity of technology puzzles. This brought me to Open Source software and I was soon building and configuring WordPress websites, and creating a workspace that allowed me to collaborate with the larger software communities.

Here's another exciting release of CiviCRM, with maintenance and stability improvements to give you the best possible experience. Download CiviCRM 4.4.5 now.

» View all issues fixed in the 4.4.5 release.

We're excited to share that CiviHR 1.2 stable is ready for release. If you are new to CiviHR 1.2, you can read about its beta version here.

CiviHR 1.2 will save manhours and paperwork in non-profits in several new ways:

We still have to do a really good showcase, but I do quickly want to share some encouraging figures from the MAF Norge CiviCRM implementation with you:

A final blog about our Donor Journey sprint with Steinar and Helen from MAF Norge. Or I should really say our sprint on CiviCRM Trigger Action. We set out to at least create the first basic version of the engine to automatically do stuff based on stuff in CiviCRM :-) Some kind of mechanism that would allow MAF Norge to automatically move donors into specific groups once they have contributed for the first time or set up a recurring payment for example.

CiviCase is a case-management system for tracking multistep interactions with constituents -- such as social support services, constituent services, and applications for employment. The CiviCase toolset enables organizations to provide a more consistent quality-of-service to their constituents by setting out a base timeline for the services to provide to each constituent.

Today a new blog post about the progress of the implementation of Donor Journeys into CiviCRM. The route we are taking is that we want to create a trigger/action extension for civicrm because most the donor journey automation is based on a trigger/action. e.g. payment coming in resulting in a thank you SMS a day later.