CiviCRM used in Wikimedia fundraising site ...

Wikipedia Fundraising C.O.R.E designed and developed by the folks at Four Kitchen Studios is using CiviCRM v1.5 and Drupal 4.7. In their own words:

Fundraising C.O.R.E connects to the CiviCRM data tables as the source of data. CiviCRM in turn gets its data from the PayPal and Moneybookers synchronization engines we manage. Finally, we're using i18n for internationalization.

We also manage the fundraising pages on the Wikimedia Foundation site that feed data in.

Wedding Bells...

Last weekend Rupam Jaiswal, our CiviCRM team developer from India got married. A few of us from the team had gone for the wedding. It was great to see the transition from a developer whose days revolved around putting together code, into a bride who was now busy getting things together for the big day. She looked resplendent in her traditional Indian outfit.

Load Testing CiviCRM ....

One of our major goals for this year is to optimize CiviCRM to handle load in a graceful manner. This is extremely important for us with the Branner Project. One of our main goals for the project this year is to optimize CiviCRM to be able to handle the last weekend load nicely (similar to the slashdot effect, the application process has most of the applications being filed and completed the weekend it is due)

CiviCRM install services ...

One of the most frequently asked questions on the CiviCRM dev list is for help with installing CiviCRM. Most of the questions are quite similar, although each of them seems to have their own specific twist. We do agree that installing CiviCRM is not for the faint-hearted and it takes a fair amount of skill to get it up and running the first time.

CiviCRM financials ......

Don't worry, the body is not as dire as the subject indicates. Just wanted to give folks some background about how we operate and manage to do what we do, and what we need to do to continue delivering an awesome product (or so we think ...)

We currently are spread across India (9 developers), Poland (1.5 developers), US (dave) and NZ (lobo).

Candidate Feature List for CiviCRM 1.7

Now that 1.6 beta has been released - it's time to look ahead and prioritize the NEXT release (1.7).

There are a few "big features" we're targeting:

... and a number of smaller but significant feature candidates.

Check out the proposed release features here.

Development team expands into New Zealand ...

As some of you are aware our development team is fairly distributed. We have developers in Mumbai - India, Warsaw - Poland and San Francisco - US. Effective next week, we will have a presence in Nelson - New Zealand. I'm moving to NZ for 9 months and am looking forward to it. You could follow our adventures on my newly created personal blog. If there are any CiviCRM'ers / Drupal'ers in the Nelson area, would be great to form a co-working space, join forces and spread the open source paradigm with organizations in that area.

Dave Greenberg will also be on vacation for a large part of December. We are pretty confident that the rest of the team will do a great job of keeping the project and community moving forward at our normal blistering pace. Feel free to keep them busy and on their toes with a constant supply of feature requests, bug reports and installation issues :)

Branch for CiviCRM v1.6 ...

For folks downloading the latest code from the svn repository, we have branched the v1.6 code base. The main trunk is now be focussed on v1.7 development and is considered unstable. Please do an svn switch in your directory

$ svn switch http://svn.civicrm.org/branches/v1.6

We will be more proactive about letting folks know about such events before they happen. We'll also be merging 0.4.1 of the dojo when its officially released (its currently in RC2)

CiviReport: More on CiviReport and BIRT ...

It was a pretty productive thanksgiving weekend :) Learnt way more about reporting, how complex an issue it is and the number of companies that are built on reporting (or to use a more trendy phrase, Business Intelligence). So here are some conclusions:

  • PHP does not have a decent open (or closed) source reporting tool.
  • Reporting is too complex an application and fairly well addressed by other open source projects. We should use one of those applications rather than doing it ourselves
  • All the reporting open source projects use Java / Tomcat. CiviCRM users will need both java and php tools if we adopt this route