Developers need to follow a new process to request automated distribution for their extensions. Volunteers are needed to perform extension reviews.
Ginkgo Street Labs is pleased to announce the availability of CiviVolunteer 2.2.
Two themes are evident in this release: improving stability and furthering the multi-tier use case. The increased adoption of CiviVolunteer as a multi-tier system, where one organization facilitates the volunteer programs of partner organizations, has necessitated improvements to permissions granularity as well as streamlining of interfaces. Improvements in CiviVolunteer 2.2 include:
I discovered CiviCRM as I was transitioning from accidental techie to intentional techie. While it's true that a TRS-80 Color Computer featured heavily in my childhood — I would secretly leave it powered on for the days it would take me to key in the recipes from Getting Started with Color BASIC, as we didn't have the cassette storage peripheral that would have allowed me to save my progress — I never set out to become... well, a geek.
In my last blog post I promised I'd share more about CiviVolunteer 2.0's new features as they come together. We've finished our first round of development on what I've been calling the volunteer opportunity shopping cart, and I'm excited to share it with you.
As Andrew wrote earlier this week, the post-CiviCon code sprint in Tahoe, CA, has divided up into smaller teams in an effort to bring version 4.5 to feature-freeze. I've been working in Kurund's group, and I've been nominated to report on our progress thus far. As we head into Day 4 of the sprint, we've closed 15 of the 26 issues assigned to our group and tackled a few issues in other groups' queues.