Lesson Plan: eEurope
Thursday, October 16th, 2003Many governments across the globe are beginning to believe in Free and Open Source Software (FOSS). But, after all, beginning is just the beginning. They now must follow through.
Much open source in government today happens because it is often easier and cheaper to get the job done that way. Equipment can be re-purposed and there is no long procurement process. The downside is that there is little solid support or official recognition for systems built this way and their vitality depends upon the continued availability of a few talented or enthusiastic internal proponents.
Ultimately to harvest the benefits of FOSS, the ground must be prepared now and proper seeds sown. For many in the European Union, this ground is a new knowledge-based economic paradigm called eEurope. Policy makers insist that eEurope can only be built by emphasizing open standards while at the same time establishing a stronger competitive tension between FOSS and proprietary software models. Into this fertile ground concrete projects are being sown. Across Europe, three initiatives are emerging. Specifically, proponents of FOSS and eEurope see the need to:
1. Clearly state the problem: lock-in by fragile and expensive single source software
Leading the way in articulating the software problem has been Germany. Like other large enterprise customers, Germany is faced with changes in Microsoft licensing that threaten to multiply costs. The root cause of stiff new licensing terms, according to German analysis, is lack of effective competition. Dependence on a single vendor increases lock-in and promotes higher prices. In addition, new risks appear, including 9/11. 9/11 represents the vulnerability of non-diversified IT infrastructure to catastrophic disruption. Other threats include the rampant and costly spread of e-mail viruses, made easy by the fact that everyone uses the same proprietary e-mail program having the same cookie-cutter vulnerabilities. The German Information Ministry coined the moniker “IT monoculture” to capture the economic dependence and security risks of monopolistic, proprietary software.
2. Develop an information and support campaign: web-sites, mailing lists, conferences, call-in help, contracted support
Solving the IT monoculture problem is impeded by the its very success and ubiquity. Nobody wants to learn new ways of doing things, when the old ways work just fine. After all, ordinary users care less about the fragility or cost of a software monoculture than its perceived ease of use and utility. To overcome the perception that Open Source is more difficult or less useful, governments are beginning to build official support mechanisms and to promote complete infrastructure switch-overs.
For example, the Scandinavian countries have jointly produced a multi-language Nordic Open Source Website to explain and to provide links to the best consumer oriented FOSS products. Germany sponsors a much larger and more technical FOSS information and support service called BerliOS. BerliOS tries to meet the interrelated interests of users, developers and commercial providers of OSS. Germany has also contracted with commercial firms such as IBM to provide OSS support to government jurisdictions and agencies. The German Information Ministry expects these efforts to transition as many as 10% of government desktops to Linux and OSS. Intentional diversity will increase pressure to meet open standards across all products and will induce healthy competition and serve to lower prices.
3. Set policy
As long as policy about Open Source is silent, experience demonstrates that formal procurement criteria will always favor proprietary interests. To break this cycle, the government must be proactive in policy formulation. Today, the European Union and many of the strongest member countries are beginning to codify an encouragement of open standards and FOSS. While the effect so far has been modest in terms of practical procurements, the long-range influence is likely to devastate core proprietary software interests. Significant policy formulation is occurring at the level of the European Union because of its desire to further unify the economies and e-governance of the constituent nations. The EU’s eEurope envisions joining all the information processing of public administrations in Europe. Such interoperability and sharing can only be based upon open standards and the initiative explicitly encourages FOSS.
Conclusion
Government Open Source advocates must study the detailed lessons of eEurope as it unfolds in the EU and plays out in the member countries. But the broad lesson plan is already established: the right problems must be recognized, supportive processes must be encouraged, and strong policies must be enacted. Real projects and real resources are being applied to building a next-generation, knowledge-based economy in Europe using open standards and FOSS. By the collaborative feedback of open technology, the benefits eEurope derives will in turn promote the global knowledge-based economy. And that’s a lesson every country can learn.
