Blogues

Before I started working as a CiviCRM consultant, I was a CiviCRM user at a small nonprofit. We got a large chunk of our revenue through grassroots donations, but we never had an opportunity to see how we compared to other organizations like ours.

CiviCamp 2017, formerly known as CiviDay, took place in Denver on February 22. This is a casual gathering that is organized by CiviCRM experts to create a forum to discuss, discover and evaluate topics related to CiviCRM in a relaxed and candid atmosphere.

Thursday 23th and Friday 24th of March we are having a mini-sprint in the Ede (NL) in which we will fix CiviCRM bugs. We are with four of us already (Erik Hommel, Alain Benbassat, Klaas Eikelboom and me) so it is going to be fun! That is the main reason and the other reason is that we want to contribute to CiviCRM Core.

Our plan is to have two days for fixing CiviCRM bugs once in the month or once in the two months. But at least regularly and fitting to our busy schedule.

Some of you will know, use and might even love the CiviRules extension. We certainly do! Quite a few of the organizations we support with their CiviCRM stuff use and love it, and judging by the question on StackExchange and issues and pull requests on GitHub quite a few more do too!

AGH Strategies will be presenting a two-day CiviCRM User and Administrator Training in Washington, DC, and this week you can save $100 off the training fee. Register online with the code MARDIGRAS to save $100 through March 4.

In this blog I want to explain the round up we have done around the refactoring of the acl_contact_cache. In the previous sprints we discovered that a lot of the performance was slowed down by the way the acl_contact_cache was used (or rather not used at all).

Just a heads up for the community that "Using CiviCRM" by Joe Murray and Brian Shaughnessy is Packt Publishing's free book of the day. See https://www.packtpub.com/packt/offers/free-learning.

This book is a good overview of the system despite being written for a much older version of CiviCRM. In particular the early chapter on planning your CRM implementation is still applicable and valuable information that is often overlooked.

If you contribute to CiviCRM, we want to know about it. Now, you might ask "don't you already know given that contributions improve the code, coordinate events, extend the system, etc.?" Well, yes, that is true, but coordinating all of that information in such a way that we, as a small Core Team, can recognize it effectively is no small task.