Is Open Source Software Right For Your Organization?
Open source software is software written by programmers that can be viewed, modified or downloaded by anyone, and the software is typically developed, marketed and distributed by a loosely organized community of individuals rather than a vendor. It’s often distributed for free, which makes it appealing to organizations seeking to meet their goals on limited budgets. But “open source” can mean different things to different people—and so can “free.”
Is it a good idea for nonprofits to take it on, or can it cause more problems than it might solve? There’s much about open source software to make it interesting for nonprofits. It’s generally free to download, for example, but the actual costs of successfully implementing the software once staff time and consulting costs are taken into account can vary dramatically. Some open source software packages are easy to get started with, but others expect you to have someone technically savvy to get them up and running. And though a constellation of consultants and vendors tend to support most open source packages, support costs can be as high or higher than those for traditional software.
For organizations looking to build a customized solution on an existing platform of functionality and features, the lack of restrictions on modification also makes open source software attractive. Source code access can be valuable in certain circumstances—for example, to an organization looking to tailor a Constituent Relationship Management system or website Content Management System to very specific needs. But for many organizations and applications, it’s not necessary, or even desirable, to customize a piece of software through the code itself.
Traditional software requires that organizations not only track licenses, but also the type of license agreement that applies to each piece of software. For instance, one package might require each user to have a license, while another requires only enough licenses to cover simultaneous or “concurrent” users. Some require licenses per machine, or per processor within a machine. It’s easy even for conscientious organizations to end up in violation of license agreements, leaving them vulnerable to legal action and fines. Open source gives nonprofits more flexibility, since it can be installed on as many systems as needed without tracking licenses.
Expert opinion is, generally, divided. Open source evangelists believe in supporting such options wherever possible, and encourage organizations to share any useful modifications they make to the code. But for most nonprofits, budget and functionality are the primary drivers of software decisions. Open source could be useful, but it isn’t necessarily the best solution just because it’s open source.
Whether or not open source software is a good idea for you can also depend on the culture of your organization. Some organizations tend to stick with established technology brands, and prefer Microsoft’s software and all the support and brand recognition that comes with it over a smaller provider’s competing releases. If that’s the case at your nonprofit, make sure you seek and receive strong buy-in at all levels before going too far down the open source path.
Most nonprofits making software purchase decisions have to balance their needs against the time and budget they can afford to devote to implementing the new system. Which means open source software is not going to be the right choice for every organization. How do you decide if it’s right for yours? Consider all your criteria, and prioritize them. Weigh your needs against compatibility and interoperability, ease of use, availability of support, and all associated costs. Make your decision based on how well a given solution fits your needs—not whether that solution is open source.
For more information, read the full article here.
