Steve Borsch weighs free & open against for-fee and closed. In in he brings up some great points – namely, if the problem you have is solved – good enough – by a hosted, for-pay service, then installing and setting up a “free”, open-source system isn’t worth it.
Personally, I’m not keen on SurveyMonkey’s presentation – and if I had need for a browser-based survey, I’d want to polish the presentation more than they permit easily. In that sense, tweaking PHPSurvey might be worth the effort. Same may be true of integrating into other systems. Same may be true if I, for whatever reason, don’t want the service provider to have my data.
Whichever solution I go with, it will take some amount of setup time, time to get familiar with the tool, and time to make it work the way I work. Question is – which will make the most sense for my specific problem.
Depends. If the problem doesn’t include customization or integration, then open source isn’t a good candidate. If the inverse is true, then an open source project will get you up and running faster than building from scratch.
I do agree with Steve, there’s a huge opportunity for organizations to take free, open-source projects, polish them up, make them dead-simple for a specific group of people to use, and sell access to the implementation back to the audience. Stikipad v. Instiki as wiki solutions come to mind. This transformation: