Freeform Solutions uses CiviCRM to help the non-profit organizations we develop sites for to manage information about their members, volunteers, activists, donors, employees and other contacts, and to handle donations, correspondence, mailings and more. We support the CiviCRM community by contributing documentation, patches, modules and code, and are a silver sponsor of CiviCon 2013.
CiviCRM brings continuity and coordination into our ever-growing company and database. By tracking the activities of our constituents, we can better serve them. By better serving our constituents, we can focus more on our mission: Developing young people into magnificent human beings through participation in the performing arts.
Working as a part of GMCVO Databases I implement CiviCRM and support local organisations with their installs. The diverse range of clients we have is a testament to how adaptable
and flexible CiviCRM is to meet the needs of so many organisations.
A lot of our clients are small grass-roots organisations that run entirely on volunteers. They often don’t have the budgets to pay for bespoke systems and CiviCRM offers a robust and adaptable system that is affordable too.
Over the past 15 years I've been involved in several open source communities.
CiviCRM is without any doubt the one that has the strongest focus in welcoming "newbies" and letting everyone feel at home here. Another impressive feature is the focus on shipping. No matter what you think of CiviCRM today, you are almost sure that there will be a newer and better version in a few months.
CiviCRM has had an array of powerful import tools for as long as I can remember but the availble options have been limited. Contacts, Contributions, Participants, Memberships and Activities...sure....but what about the Events themselves? Sorry. What about Grants? Nope.
"Sort Name" is used by CiviCRM for tabular search results. CiviCRM has historically just copied the Household and Organization names directly into the Sort Name field. For names such the "The Can Company" and "Tom and Jeri Cooper" this doesn't work out so well; the sort will happen on the letter T as in "The" rather than the letter C as is more appropriate.
Proper GRM tools can make all the difference in the success or failure of your herd. As many developers have found, working with a proprietary goat resource management system can seem simple in the beginning, but customizing it to your herd's specific needs can feel like eating brambles. With the new CiviCRM extensions framework and easily digestible API 3.0, developers can dig in and produce at an unprecedented rate.
There have been several hook() or Drupal module based solutions for "members only" pricing for events or for other 'discounts' related to memberships.
If you are using Drupal 6, you have a vested interest in extended Drupal 6 support for CiviCRM 3.4 until spring 2012. If you are staying with Drupal 6 because of budgetary reasons or because Drupal 7 doesn't yet support all the modules you need for your site, this is vital for you. You will make sure your 3.4 CiviCRM/Drupal 6 setup remains healthy and safe.
Hi this is Stuart from Korlon LLC. I decided to write a case study about ACLs since they don't seem to get a lot of attention. If you've ever wondered (or asked) "what if some people should only be able to see certain data in Civi?" then ACLs will probably accomplish what you want.
These are some graphs I created from the data publically available at CiviCRM's Sourceforge. Sourceforge provides limited data only on the release dates of a version (i.e. 3.1.5) and then the number of subsequent downloads to date but we can still interpret some useful conclusions from the data. Dave Greenberg shared one of these graphs at CiviCon. The data is from Mar 1, 2011 so I wanted to publish them before the data became too stale.
The first graphic is the simplest to understand - CiviCRM all versions 2.x compared to all versions 3.x. Note that the timeframe measured in this graph is similar. As such, we can conclude that the number of downloads for 3.x have increased about 27% compared to 2.x.