Last Thursday we had a developer meeting aimed at organisations and individuals developing with CiviCRM in the UK. Nine of us made it out. I'll try and give a flavour of the participants...
Blogues
I've been working for the past few months with CiviCRM and despite the differences which came as a bit of a culture-shock to me, I've cobbled together a few ideas for things that perhaps could be considered for future versions.
Please bear in mind that these are simply things that I have had to add myself for a live contract and in no way reflects poorly on the CiviCRM system as it stands. On the contrary, I think the fundamental aspects of CiviCRM offer an easy way to add crm functionality to your site.
UPDATE: Please use the v2.2 beta downloads. The below version is now obsolete
In conjunction with some awesome folks in the Joomla core team and Elin Waring (mcsmom), we've restructured the CiviCRM install process for J! 1.5.9 in the hope of increasing the install success rate on shared hosting. There are changes to the front end (contributed by Elin) to simplify menu creation.
I'm hoping by posting this I can get a feel for how useful a Sage plugin and associated module for CiviCRM would be. We have a client that needs to have transactions from the various portions of CiviCRM that tend money to be recorded in their accounting package. I personally think it would be a great addition and being a client requirement, it has been factored into the costs.
There are several considerations as to how to approach this, I have thought of a good few ways of achieving the goal but I’d like if I may to ask for a little help fleshing out the details.
Earlier today we had a conference call with a few consulting firms and individuals who integrate and deploy CiviCRM for clients. There were approximately 15 folks in the room. The agenda and quite a few comments are documented on this wiki page.
Some links to recent blog posts about CiviCRM. We've also started tweeting about CiviCRM. You can follow us here
Hi,
As you know, CiviCRM collects informations about the installations, like numbers of contacts, what modules are used.
I'm wondering if you would find useful to have more statistics in a new reporting screen on your installation (beside the numbers of records, knowing how many are tagged, have a postal address, have a phone, have relationships...).
I spent some time analyzing data that we've been collecting over the past few months. In v2.1 we added a ping back feature which lets us know what component folks are using and the size of some of the tables (which gives us an estimate of the size of the site etc). All information is hashed and we do not record any IP addresses. Details of what we collect are in a prior blog post