News

Letter to Obama: Consider Open Source

The Collaborative Software Initiative (CSI) today posted an open letter to President Barack Obama on open source software. The letter urges him to mandate that the U.S. government consider open source software for federal IT initiatives.

The letter was signed by top executives of companies with a vested interest in open source, including Alfresco, Ingres, Jaspersoft, OpenLogic and Unisys Open Source Business. It was subsequently signed by several dozen others.

"We urge you to make it mandatory to consider the source of an application solution (open or closed) as part of the government's technology acquisition process, just as considering accessibility by the handicapped is required today (as defined by section 508)," the letter said.

CSI helps companies and public organizations build solutions based on open source software and methodologies. For example, the CSI-supported TriSano effort is an open source system designed to support infectious disease surveillance and outbreak management.

The letter was the brainchild of David Christiansen, a CSI senior developer, who decided to write the letter upon reading that creating electronic medical records was a priority for the president. In an interview on Tuesday, Christiansen emphasized that the letter is not intended to suggest that open source software be required. Instead, CSI's view is that open source should be considered in RFPs and federally funded programs.

"I don't want to mandate everything the government does should be open source," Christiansen said. "I think software should stand on its own merits, but I honestly believe that one of its merits should be the sourcing of the software, the way it's built and who owns the technology."

The government has used open source software in a number of projects, including at the Department of Defense. However, CSI's CEO Stuart Cohen believes it is often difficult to get open source software considered, although the situation is not as bad as it was years ago.

"I think it's getting there, but if we really thought it was there, we wouldn't have written the letter to begin with," Cohen said.

Some see open source software as the way to go, from a general perspective.

"We need the government to put its money where its mouth should be," said James Vivian, a Web developer at Burlington, Vt.-based Dealer.com, emphasizing he was not speaking on behalf of his company. "We need to start spending as a society on open source initiatives."

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube