At the Wikimedia Foundation, we leverage CiviCRM to maintain millions of records of donors and their contributions. Working with the product and particularly with the community has been a terrific experience. There's nothing quite like two open source organizations working together to meet their respective goals while ultimately strengthening the open source community as a whole.
CiviCRM makes it possible for non-profit organizations, even those with a limited budget, to forge strong relationships with their constituents, thus bringing them closer to fulfilling their mission. Over the years, we have seen CiviCRM develop and evolve in a very responsive way to the needs of the marketplace.
Its great to work on a project that has a profound impact on non profits. I am very excited about the work we do on CiviCRM which involves building on each other's ideas to create best of breed solutions for non profits. The fact that CiviCRM is an open source project with an amazing community and dedicated developers is an icing on the cake.
We recommend and use CiviCRM with most of our clients, and have since 2005. It's got a fantastic collection of functionality that fits the needs of non-profit organization communications, and the CiviCRM community of developers and users is growing, broad, vibrant and responsive.
The best part? When I describe to potential new converts how all of their constituent relations (donations, membership, mass emails, etc.) can be managed with a single integrated, configurable tool, I can hear an incredible yearning at the other end of the phone.
CiviCRM provides Future First with world-class database software for absolutely free. We use it to store well over 100,000 contacts with no signs of slowing. CiviCRM is so customisable that we can implement cool features without needing to reinvent the wheel each time.
If you like empowering charities in a free and open way then you are going to love Civi!
I find the engagement with our community of users to be intellectually stimulating
and rewarding. Seeing folks with expertise in a particular area step up and contribute their time and ideas to help improve the product is quite exciting. Every time I hear about a new interesting organization starting to use CiviCRM, I get a renewed sense of excitement about our work. The range of civic sector organizations currently using the software is quite amazing to me - from large international advocacy organizations to local performing arts troupes. I also really enjoy interacting with our international community - building friendships and getting to share culture (food, music, humor ....) with colleagues on every continent.
We recently had one of our groups report that merging data was resulting in data loss. Specifically, when they merged two records, they noticed that the contribution records on the record that was deleted were not carried over to the record that remained.
I investigated and found the culprit: we were missing a foreign key constraint between the contribution table and the contact table. In fact, we were missing a lot of foreign key constraints in this database.
The ability to create petitions in CiviCRM was a tremendous move forward for people using CiviCRM for political organizing. The petitions feature took another step forward with the Petition Email extension, that allows copies of your petition to be automatically sent by email to a given target. However, the holy grail of e-advocacy was still just out of reach: automatically sending your petition to the petition signer's elected official.
When generating mailing labels, CiviCRM users have the option of choosing the address to be used (e.g. you can select "Primary," "Home" or "Work") depending on where you want to reach your contacts.
CiviMail, however, does not provide this option. Instead, CiviMail automatically chooses the address for each contact - a process we can only control on a contact-by-contact basis by setting the "Bulk Mail" or "Primary" flags for each individual contact.
Have you ever completed a training a wondered whether usage of your CiviCRM database changed as a result? Have you ever wondered who were the major database users in your organization and who might need more prodding?
With the 4.3 upgrade, the Progressive Technology Project has made a number of important steps toward breaking out our work into pieces that others can use on their sites. This blog will begin a series of (hopefully) weekly blogs outlining new functionality that others can use.
Our first blog features the civicrm_petition_email Drupal module. Thanks to the hard work of agh1, a Drupal 6 version of the module is available (https://github.com/agh1/civicrm_petition_email). We just finished porting it to Drupal 7.
Progressive Technology Project has released a new Drupal module called CiviCRM Cicero that integrates with the Cicero service from Azavea. If you are using CiviCRM with Drupal, you can now add legislative district and more information to your database.
Last spring I started working on a Drupal module that would keep CiviCRM contacts in sync with Salsa contacts. I did a lot of the work on it and then, upon joining PTP's staff, the project unfortunately fell to the bottom of my stack.