Blogues

For a first timer, it sounds daunting to go the CiviCRM code sprint. While I had worked with CiviCRM for a while and fixed many client issues with AGH Strategies, I was wondering how I would contribute to the CiviCRM community during the sprint. Like many other contributors I brought my own ideas and vision for how this week would go.

We have been having a very enjoyable, and very productive time at the Tahoe sprints. Amongst other achievements, we have agreed the specification of those issues to be included in version 1.4 of CiviHR, scheduled for release in time for CiviCon London in September. This release will focus on improvements to the existing features, following the feedback we have received from our users.

We are four days into the sprint now and things are going great! I think everyone was ready to get right to it this morning since the crew got to sneak away yesterday for an afternoon out at Lake Tahoe. The breath taking view from Eagle Rock was a great way to regroup and get ready for the remainder of the week.

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.

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.