The API was a big topic at CiviCamp. We had a good discussion on the mistakes we made in the past and things we can do better going forward. Due to a variety of reasons (internal and external), the API migration between 1.9 and 2.0 was a disaster. We resolved to not let this happen in the future. Here are a few things we agreed upon
Blog posts by lobo
We coded / migrated / bugfixed a few drupal modules as part of CiviCamp (blog reports here and here). We also decided to ship these modules with our 2.1 release. You can get the current version of these modules here. CiviCRM v2.1.2 will include the following drupal integration modules:
We have 4 more slots available for CiviCamp. CiviCamp will be held at Yahoo!'s San francisco offices (downtown, Sansome street, close to BART/Muni etc).
The CiviCamp agenda is on our wiki here: http://wiki.civicrm.org/confluence/display/CRM/CiviCamp+-+Oct+13-14%2C+2008. Some other details of the camp in prior blog posts
So the good folks at USPIRG our continuing their support of CiviCRM and are sponsoring quite a few cool features for CiviCRM v2.2. In case you were not aware, they also sponsored quite a few cool features for 2.1.
The CiviCRM team will have pretty good representation at BADCamp in Berkeley on Oct 11/12. A few of our senior developers from India (Yashodha, Deepak and Kurund) will be in the Bay Area at that time. We are also hoping that either Michal or Piotr from Poland will join the party.
The CiviCRM team branched off v2.1 late last week. We hope to knock off most of the remaining v2.1 issues over the next few days and release the the first beta candidate.
Most of you are aware that CiviCRM collects version, CMS and an MD5 hash of the base url from a CiviCRM install. We discussed this feature in the blog post: Extending the Version Check Mechanism in CiviCRM 2.0. The CiviCRM admin can decide not to participate in the ping back mechanism.
Here are some useful stats that we've collected using this feature: We've got close to 4000 installs running CiviCRM v2.0. Approx 66% are Drupal, 34% are Joomla. We have 133 installs testing various versions of 2.1 alpha, 98 Drupal / 35 Joomla.
David Geilhufe (full disclosure: he is on the board of Social Source Foundation, the non-profit behind CiviCRM) has written a good article on What is Donor Management Software. The article discusses some of the potential reasons on the exclusion of CiviCRM from the list of software products.
Do you use Drupal/CiviCRM or Joomla/CiviCRM to manage your donors? Do you think CiviCRM is a good fit for your donor management software needs? Show your appreciation for CiviCRM/Drupal/Joomla and open source software by taking part in the NTEN Donor Management Survey.