Blogs

After a big conversation at the coding sprint, we seem to be in consensus about transitioning CiviCRM's revision control system from using subversion to using git.

If you are a user or integrator that installs CiviCRM by downloading the zip or tar ball from the CiviCRM site, this transition won't affect you in any way.

Several CiviCRM users have expressed an interest in managing CiviCRM activities with a smooth, interactive calendar screen.  Since calendaring can be a complex topic, we've put together a basic, working calendar to facilitate discussion.  The prototype resembles the calendar included in other relationship-management tools:

If you've ever configured a schedule task (aka cron job) for CiviCRM, you know the routine. You have to look up the username and password for a user in your database that has database permissions, you have to find a really long mess of characters known as your site key, you have to find the proper name of the job you want (like UpdateAddress.php or civimail.cronjob.php) and then you must string them all together in precisely the right way to make the cron job.

What a tedious drag.

I´m Abril from Mexico City, I´m working in Alternativas y Capacidades, a civil society organization that was founded in 2002  to contribute to Mexico’s social development, by strengthening civil society organizations and grant makers, working towards a favorable environment for their professionalization, promoting their advocacy capacities and encouraging inter-sectoral collaboration.

We've been working hella hard on the sprint so far and yesterday was no exception!  at least for the book sprinters, the coders went off on a social to Stamford castle.  Although they weren't out of contact for long, we met up with them on IRC while they stopped for a Costa coffee "Come for the coffee, stay for the WiFi" or so the saying goes .  

On a system with roughly 25,000 activities, running on a dedicated server, the case dashboard would take over a minute to load. Other orgs have reported similar problems, and in at least two cases the consultants simply removed the upcoming/recent sections from the dashboard since it was just too slow.

Taking for example the upcoming section, on the server above the query would take about 26 seconds. With some optimization, it now takes less than 1 second.

Code sprint is always fun. It's gives you great opportunity to meet fellow civi folks, collaborate and implement kool stuff :). Last few days has been very interesting. Besides some great meals we also managed to get some work done. ( If you still don't know, food is the most important part of CiviCRM Sprints )