I often talk about what it takes to product-ize open source software. Most regular people consider open source to be "not ready" or "almost there". This interchange on the CiviCRM boards is a great reminder of the need for an ecology around open source products.
Basically, a small, no resource organization wants CiviCRM to work better with IE. The open source projects asks the no-resource organization to invest time and/or money into making CiviCRM work better with IE. The small organization gets frustrated and says:
Not working on the UI in the most common browser on the planet (especially for low-income people in need) is--to me--shooting yourselves in the foot WRT accomplishing your goals. But perhaps you are not building this "for the people," but really for geeks. If that's the case, then be clear about it. If your goal is to help non-profits, this is one place you fall very seriously short.The simple fact is that the "people" don't have the resources to contribute, and the geeks and large budget nonprofits do.
Or is that really true?
Non-profit accidental techies with no time and little or no power in their orgs make up a huge portion of your user base (as I understand it, anyway). I am wondering if we should be discussing how to make this "community" model work better, because I don't feel like it's well-directed to do what you want it to do--supplement the good work you guys are doing.And here is the crux... how do you make the community module work better? I think it is probably by providing clear, simple, low time commitment tasks to the community:
- Take 1 hr talk to the CiviCRM team about how to do testing and test CiviCRM in IE. Then log the bugs found.
- Take 1 hr, send an email to everyone you know asking for a volunteer programmer/geek to come in and fix those bugs.