Risk is part of every project. Risk can be associated with product quality, cost overruns, and schedule slips, to name a few. You don't have to be using an open source application like Drupal to experience these risks. But if you are going to manage your project in such a way as to mitigate risk, you should be aware of a few aspects of open source applications that can introduce risk to your project.
Following are examples of potential risks for which you might want to create mitigation plans. When reviewing these risks, consider the probability of the risk actually occurring and what avoiding the risk in the first place would take. You might find that the effort to avoid risks costs more than the risk itself.
Unlike with proprietary applications, “support” in an open source community is not someone sitting at a virtual help desk waiting for your chat call or email. Even when you choose to request paid support from a vendor, you might not get what you need.
What do you do when you can't find a knowledgeable volunteer from the community to help you? Following are some options to consider when mitigating support risk:
If you were a user of Microsoft Office 2003 and are ...