Open source as the default in government
Open source by default?
"Over the last ten years, open source has become unremarkable. I think that’s a great achievement. We no longer argue about whether it’s secure or not, or whether it’s safe to use. We focus now on how best to use open source to get the best value for every tax dollar," said Gunnar Hellekson, Chief Technology Strategist for Red Hat’s US Public Sector Group.
He noted that for the past couple of years, open source software has been helping public sector organisations become more innovative, more agile and more cost-effective by building on the collaborative efforts of open source communities.
The National Security Agency, for example, has used open source to reduce the cost of its high-security systems to drive better security. Similarly, the Consumer Financial Protection Bureau—a relatively new agency—has even gone as far as being 'open source by default', by releasing everything it does to the community.
"They do this because they feel that citizens should benefit from the software they helped pay for. In addition, they also want to allow citizens to improve the software that they’re using," he said.
"Another excellent example would be when the USGovernment released a great deal of health data, and sponsored events that invited developers to analyse and visualise that data, making it more valuable for the government and citizens alike."
While these initiatives may be small, according to Hellekson, they have enabled people to see the huge potential of open source and showed them the kind of opportunities that lie before them.
"I think it comes down to this question: Are there more smart people inside government, or outside government? If governments are using proprietary software, they are cutting themselves off from some very smart people who want to help. However, if they use open source, they are making themselves available to that intelligence and that enthusiasm, and can use it to improve the services that they deliver."
However, as with any new solution introduced into an agency, open source didn’t come without its challenges. Apart from concerns relating to stability and security, Hellekson said implementing open source meant replacing existing systems, which then translates to big investments in time, talent and resources.
In addition, great effort must also be exerted in managing changing behaviours and in introducing different ways of doing things.
"Change is hard, especially in government," he said. "Just like new proprietary solutions, Open Source solutions must make the case that they’re worth the transition costs, that they will do the job better, and set up the agency for success in the future."
"In particular, agencies who are new to Open Source worry about the right way to acquire and maintain it. Who will patch it? Who will implement it? How can we use something we don’t buy?"
Hellekson is confident that this is where companies like Red Hat come in—to make open source simple, predictable, and safer to use in an enterprise.
Originally posted on FutureGov. Reposted with permission.