Please feel free to add to this wiki!
A few resources from today's BoF:
- #npdrupal ("nonprofit Drupal") -- hashtag on Twitter
- #drupal-ngo room on IRC -- usually very quiet
- http://bit.ly/npdrupalnotes -- monthly nonprofit/social change discussion calls
Distros
- Open Atrium - v2 just released
- OpenAid - D7 version out, focuses on project descriptions
- Springboard - D7 alpha out
- Drupal Commons - good out of the box, harder to customize
- Totem - D7 beta3 out
- Conference Organizing Distribution - D7 alpha out (not production ready)
- Vojo.co (install profile) - collect stories via SMS and the site, based on VozMob
- OpenCivic - sharing "civic software" used by governments and nonprofit organizations to provide public services
CRMs
- RedHen - Drupal module suite, optional Salesforce integration
- CiviCRM - add-on module, integrates with Drupal, open-source
- Salesforce - SAAS, free to 501c3s
- Avectra - proprietary, $$$
- Blackbaud - Convio, SAAS, $$
- Salsa - formerly Democracy in Action, SAAS, $$
- Zoho - free
- SugarCRM - open-source & SAAS
Other things to discuss (that we didn't get to)
- donations in/with Drupal
- SMS/VOIP (be sure to see vojo.co)
- validation of action (e.g. report-backs from supporters to demonstrate that they've done something)
- success stories with engagement
- definition of "for good"
Comments
Atrium vs. Commons
Unfortunately I missed the beginning of this meetup. I have a question: Does anyone have any thoughts on the different use cases of Atrium vs. Commons, and/or thoughts on which is better for general community building purposes? Thanks.
Intelligent Human Agent
Three thoughts
If you'll be able to make our next call on June 27 (or think you might), please add it to our list of upcoming topics! bit.ly/npdrupalnotes
It probably depends on your use case. Atrium could be good for really collaborative teams of people -- for instance, large numbers of staff or volunteers working in teams to plan a project or campaign. But for average-supporter involvement, Commons is probably better suited because it encourages connections rather than collaboration.
Atrium just came out with a new 2.0 version, but Commons is probably better supported and tested because it has Acquia backing it and working on it for their own hosted Commons site. So if you're worried about stability/longevity, Commons is probably the way to go. Atrium I've seen used more by internal teams who don't mind as much if they don't have the flashiest internal collaboration tool, and don't mind if it has to be completely torn down and rebuilt every year or two.