Blogs
UPDATE: We have discontinued our use of UserVoice as of 12/11/2008
We've been trying to figure out a good structured and fair way of getting user input. We were pointed to UserVoice.com by Greg Heller at NTEN. UserVoice seems a fairly simple Web 2.0 site which does exactly that. Hopefully it has a decent search / sort / categoization system to handle an expanding list of features.
It feels like 2008 is the year of CiviCRM training. Following in the heels of our Melbourne bootcamp is the CiviCRM webinar bought to you by Michelle Murrain and the good folks from NTEN.
Earlier today we pushed out v2.0.2 of CiviCRM. You can download it here. We have fixed approx 67 issues between 2.0.1 and 2.0.2 (this involved approx 170 commits). This brings us to a grand total of 504 issues resolved for the 2.0 series. We suspect (and hope) that the rate of bugs filed / issues fixed will slow down significantly for future 2.0.x releases.
Notes from the NTEN Nonprofit Technology Conference, New Orleans, March 19-21, 2008
Notes from the CiviCRM affinity group meeting and the CiviCRM lunch table discussion have links on the bottom of the page http://wiki.civicrm.org/confluence/display/CRMDOC/Presentations. Both meetings were very productive.
Mari Tilos has posted a few additional screencasts on our screencast wiki page. You can read and post your feedback on the forum topic here. If you have any ideas or suggestions for additional screencasts, please do post a comment on the forum topic
Thanks to the awesome folks over at the Joomla! project, CiviCRM will have a few projects in Google's Summer of Code this year.
You can see the list of proposed project ideas here: http://docs.joomla.org/Summer_of_Code_2008_Project_Ideas#CiviCRM_Projects
The biggest thing we need now are students to apply!
Here are the top 3 reasons why you (or a student you know) should work on CiviCRM this summer:
We monitor the forums quite a bit and are always trying to figure out how to reduce / minimize the repeated requests. Many a time my strong stance on refusing to fix something obvious delays a few fixes (yes, i'm learning all the time and hopefully improving and becoming a wee bit wiser). I got a bit tired and fed up of seeing the same requests over and over again, so earlier today I went on a spree and fixed (or attempted to fix) a few of the most common support requests or mistakes.