We are excited to announce that the initial Alpha release of 2.1 is now available for download, AND to try out on our sandbox site. We're really excited about all the cool new features and improvements. Check out Dave's last blog for some highlights... or the 2.1 Roadmap for a more complete listing.
We strongly encourage folks to download and test the alpha release and help improve the final product. Upgrading to 2.1 requires a simultaneous upgrade of Drupal to 6.3, and we need test-drivers who can help us iron out any bleeps or burps that we haven't discovered in our own testing. You can contribute significantly to the project by testing the upgrade process against a copy of your 2.0 data, as well as running your regular tasks on an upgraded site.
Joe Murray forwarded this announcement to me - and I'm posting it here in case any CiviCRM folks in Seattle might be interested in doing a 5 minute talk on how they use CiviContribute for fundraising. (Even if you're not up for speaking, probably an interesting session to attend if you're in the Seattle area)...
Call for speakers on online/tech enabled fundraising.
I co-host Seattle Net Tuesday and our September event is focused on utilizing technology for fundraising. We're looking for a couple of people who experimented with online fundraising within their
This camp is now confirmed. The dates are Oct 13th / 14th. Follow up blog post here
Following the lead from our friends at Ubercart with Ubercamp, we figured having CiviCamp might not be a bad idea. We suspect that doing it around BADCamp will give folks the opportunity who are traveling to combine two unconferences in one visit.
BADCamp is schedule for Oct 11/12, CiviCamp will be held on Oct 13/14.
The 2.1 release hits code freeze this week - and we're really excited about all the cool new features and improvements. For folks who haven't been following progress on the release with "baited breath" - some highlights:
- Joomla 1.5 and Drupal 6 compatibility
- Contribution Pledges (back-office and self-service)
- Multi-language / single site support (with thanks to Google Summer of Code and the Joomla team)
One of the issues to solve when implementing the view-based approach described in my previous post on the topic is how to make the current codebase be aware of when to use a view and when to keep operating on a table.