BackOffice Thinking has created a Giving Tuesday campaign for CiviCRM. We are inviting you to join us so that the world sees the unity of the CiviCRM community. The idea is to harness the energy and conversations that are taking place in our ecosystem around Giving Tuesday and ask the CiviCRM community to Donate to protect their investment in their own technical infrastructure. (Click on the links for more information about Giving Tuesday and Stats about Giving Tuesday's Success).
My name is Erik Hommel, 51 years old. I live in the Netherlands in a small village called Brummen(between Apeldoorn and Arnhem) with my wife Floor, our 2 youngest children and four Siamese cats. Our 2 oldest kids have either left home or are in the process of doing so. My working career in ICT started in 1988 as an RPG programmer on the IBM S/38. Having moved past positions as technical consultant, project manager, IT manager and ERP consultant I call myself a CiviCRM project manager/consultant/developer and love it!
CiviCRM has been part of my life since 2010 I think. The first official date I can find is a certficate from a CiviCRM Developer Training in Brussels in February 2010. At the time I was working together with Erik Brouwer as EE-atWork and we were mainly working with Dutch housing corporations as software implementors and consultants. In 2009 we bumped into Drupal when we were developing our own website, and as we focused on CRM within housing...Read more
As you may know from a recent blog post by artfulrobot, CiviCRM is applying for a dedicated platform on Stack Exchange. I don't know about you, but I would love to see this happen. (If you wonder what this is all about, please refer to the beforementioned blog post which explains it very well.)
This initiative needs backing from Stack Exchange veterans now! Here is why:
In the current phase of the proposal, Stack Exchange wants to see how many and what kind of people would actually be contributing to the platform. People are asked to commit to using it. Three values are being measured, out of which the minimum counts. In our case, this is "committers with 200+ reputation on any other [SE] site" with only 8 out of the required 100 committers so far. So while we...Read more
I just returned from my first CiviCRM sprint. It was called the DC Sprint, but as Jeremy has already posted, we were actually in Maryland.
As a first time attendee of a CiviCRM conference and sprint, I really did not know what to expect. I was very pleased that both WordPress and Joomla! received some real attention at the sprint and I hope we are heading to a place where CiviCRM can be truly CMS agnostic.
WordPress CiviCRM installs can now benefit from WP-CLI tools. WP-CLI is a Drush equivilant for WordPress. We were able to merge Andy Walker's port into 4.5 and Tim Otten added full API Explorer support for this. At the developer training day in DC on Saturday, we noticed an issue with civix and WordPress. This also fixed and now civix works with all CMSs without having to be directly tied to one as in the past. These two enhancements will help WordPress developers immensely.
Dana Skallman and I also worked through the unresolved tickets for WordPress. A great...Read more
We're approaching the middle of the third day of the 2014 East Coast code sprint, situated in a bucolic farmhouse just outside of Frederick, Maryland. The location has made this sprint a little different, with some people being able to commute back and forth. In total, 14 or so sprinters have been working on webtests, improvements to CiviVolunteer, and improvements to buildkit for all platforms, which some renewed focus on Joomla and Wordpress. It's looking promising that buildkit will be fully supporting all the CMS platforms by the end of the sprint, making it even easier to contribute.
As this was my first sprint, I wasn't completely sure what to expect. In between some intense, heads-down work, we've found time for decompression as well. We've worked in great meals on the various porches at the farmhouse, great conversation around the firepit, and a spirited round of "The Greatest Game Ever." Monday also included a spirited discussion on forms strategy for Civi 5.0...Read more
We’ve been having some discussions among the folks who triage security issues, who publish new releases, and who maintain backports. We'll update the policy beginning with the upcoming 4.4.7 release (and related 4.2.19 and 4.3.9 releases).
Release Policy: The release window
For the past year (at least), the policy has been that new security releases must drop on the first Wednesday of a given month, and that other releases can drop anytime (with an undocumented requirement to target Tue/Wed/Thu). This aimed to strike a balance among predictability, security, and flexibility.
The revised policy is to allow stable point-releases on the first or third Wednesday of the month. This is another attempt to balance predictability/security/flexibility, and has a few notable implications:
- Overall, it’s more predictable...
CiviCooP just received it's yearly bookkeeping report and as it turns out there is still some money left after all CiviCooP participants got paid for their work and our costs (marketing, website, CiviCRM partnership, community, administration) are paid. So we decided to donate the rest (roughly about 2000 euro) to the CiviCRM community. Speaking to Michael McAndrew and Dave Greenberg we will contribute to the Continuous Integration project, which is pretty technical so hard to fund. And we as a community will all benefit because the testing process will improve! If you want to know more about the Continuous Integration project, speak to Dave Greenberg or Tim Otten.
CiviCooP was set up as a non-profit vehicle to work together as community members on bigger projects and to be able to offer continous support with a combined helpdesk. In the last year we have been pretty succesful with some bigger projects, and we hope some of them will come to CiviCon London to tell the...Read more