Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide.
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.
We strongly...
Read moreAs 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...
Read moreFor 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.6We 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)
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:
We've posted a draft specification for CiviEvent (phase 1) on the wiki. We are actively soliciting community feedback prior to finalizing the specifications on or around December 7. If you are interested in an integrated Event Management component for CiviCRM - please review the spec carefully and post your feedback and questions as comments on the wiki. We are targeting this for the 1.7 release.
This specification reflects feedback and suggestions from many folks in the CiviCRM and Drupal communities....
Read moreI did a fair amount of research on the web regarding the state of various open source reporting packages. BIRT received quite a few excellent reviews and they also have an upcoming integration with the Zend platform/framework that I had to give it another go.
So back to the drawing board, and did an install of Eclipse and the automated install / update of BIRT. I suspected there was an issue with the latest version of BIRT (2.1.1) and decided to install the older version...
Read moreThis week i've spent a fair amount of time trying to figure out what we could potentially do to make reporting part of CiviCRM. A few joomla folks on the list have successfully used a Joomla component DBQ and were fairly happy with it. I did read a fair amount of it and took the next step of actually installing and playing around with it.
DBQ is quite nice, easy to install and works as expected. However, as Dan Robinson pointed out on the email list, it is not a reporting tool, but more a simpler way to execute queries and...
Read moreWe have integrated Selenium Testing Tool for CiviCRM v1.6, in addition to existing UnitTests for checking api functionality.
Selenium automated tests allows user to test most of the civicrm functionality.
For more details check the documentation
I installed CiviCRM 1.5 with Drupal 5.0 following the same steps I took installing it with Drupal 4.7 and got no errors.
CiviCRM wouldn't show up in the modules list in the admin section, so I poked around a bit to see what the overall setup was of the Drupal 5.0 modules.
I moved the civicrm.css file into the main civicrm folder, moved the civicrm.module file into the main civicrm folder and then created a civicrm.info file and follwed the same format as the other .info files (a couple of lines of code describing the module) to write to the civicrm.info file. I copied the...
Read more