I believe that you start taking advantage of CiviCRM when you start thinking that your needs are not only yours. At the CiviCRM Community, that's the general attitude. If one has a problem, one looks for a general solution that can also be useful to others. Everybody benefits from everybody’s contributions, inspiring philosophy, isn't it?
Blogs
Despite having enough on their plate with a few billion kids worth of presents to build, and with Rudolfs unfortunate flu (well why else would he have a red nose?), Santa's little elves over in the UK have been working hard to also bring you a brand new CiviCRM extension/module - CiviBooking! Having now been extensively tested for sleigh management purposes we're really pleased to announce the first stable release available now from the extensions directory.
A few of us have started exploring how we can integrate Doctrine into future versions of CiviCRM. A large part of this work was initiated by Peter Haight from Giant Rabbit who explained his thinking and approach in this blog post on Persistence Refactoring. One of our goals for the next few releases of CiviCRM is to improve the technology backbone that Civi is based on. It made sense to most of us to start from the database layer and then move outwards and using doctrine and working with peter seemed a good logical next step.
We decided to spend 3 weeks (till mid january) on various exploratory sprints and try and answer a few questions and see how things are done in the doctrine/symfony world of things. We also decided to start adopting more scrum - like technques and iterate on a weekly basis. Our goal is to come up with a list of things that we are curious about going forward and work on some potential answers during the week. So without further ado, here are some of the things that we decided to investigate and research this week: