Blogs
We had another well-attended meetup last thursday, hosted by the folks at Rayogram, with about 20 people participating.
Let's hear it for Rayogram and their hospitality to the CiviCRM community by hosting the New York City Meetup last Thursday! We accomplish so much using all of our electronic tools but there is still a kind of creativity that happens so much more efficiently in real time, face to face. One of the breakout groups at the Meetup was with persons interested in talking about CiviPledge.
The Physician Health Program of BC has a task that goes something like this: Their vendors, and even staff and board members, are not paid directly by them but by the provincial medical association (BCMA), so when invoices from vendors come in, they need to enter the information onto a special form and send that off to the BCMA for payment. Then they periodically send back a statement to reconcile against.
Not a well known fact until now - during 3.0 release cycle, we've been working hard with DharmaTech to start regularly using unit tests for CiviCRM development and quality assurance. It's time to go out of the closet, since we're nearing the end of the first stage of this project - which was setting up everyone in the team with proper tools and migrating all the tests that we wrote before to our new framework.
So here's what we have right now:
The team is starting to roll on CiviCRM v3.1. One of the sponsored items is the ability to allow one custom group to be used with multiple relationship types. I'll use relationship types as my example here. This feature will also work with other objects that can be extended: specifically In v3.0 and prior a custom group can only be used for one specific relationship type.