Blogs

v2.0 has significant schema changes, and hence a simple sql script could no longer serve as our primary upgrade mechanism. We are introducing a new upgrade system in 2.0 which will run in a couple of steps and upgrade the user's database. It has been an interesting exercise to come up with the upgrade script. Here are a few things we learned as we went through the process.

The results of the first day of our Mumbai meetup were quite impressive. We successfully knocked out around 7-8 issues.

Day two started out with high energy levels. We divided the day into three sessions.

Most of the CiviCRM team is currently in Mumbai, India where we are having our first world wide developer meeting. :) We are missing Dave Greenberg who unfortunately had to cut short his trip to India. :( But he is present via the wiki, blog and issue queue prodding us along. :)

I had a great discussion with Michal Mach and Dave Greenberg of CiviCRM about the new case management features in CiviCRM. I had a look at them, and I felt they are a good start. But they need some help. Getting a free and open source software tool for small organizations to do case management has been something I'd hoped for for a while, and having written a case management tool or two, I have a soft spot in my heart for this problem. I volunteered to gather a small team together of folks who would help the CiviCRM team by coming up with some good use cases, and helping them figure out features that would be necessary for organizations to adopt CiviCRM to do case management. If you know some things about case management implementation in small organizations (this tool would, at this point, probably not work for large orgs with major case management needs) and are interested in helping out, please drop me an email.

You can contact Michelle at michelle at nosi dot net

For several versions now, CiviCRM ships with version checking mechanism that pings our server from time to time (every time you visit the Administer CiviCRM page of your install, but not more often than once a day) and lets you know if there’s a new major stable version available for download. (This mechanism can be turned off by visiting Administer CiviCRM → Global Settings → Miscellaneous Settings.)

We have delayed CiviCRM v2.0 code freeze (and hence alpha/beta/final) dates. This was primarily because of other commitments, specifically developer boot camps and our combined travel schedules. We expect to have the code freeze in the second week of January (01/07/2008) to be followed by alpha, beta and final releases spaced out over the next six weeks.

A few of the NY based CiviCRM folks gathered together near Union Square in NY. We lucked into a pretty good meeting spot, thanx to fellow CiviCRM'er Chris P. We had 10 people participate in this meetup. This included a couple of folks who were in the investigative stages regarding CiviCRM. The agenda and some of the highlights include:

This is an old report, Check the latest report here:CiviCRM gets a solid A in the 2009 Data Ecosystem Survey Report (we did even better this time around!)