U.S. Government Goes Open Source | Syncfusion Blogs
Live Chat Icon For mobile
Live Chat Icon
Popular Categories.NET  (173).NET Core  (29).NET MAUI  (207)Angular  (109)ASP.NET  (51)ASP.NET Core  (82)ASP.NET MVC  (89)Azure  (40)Black Friday Deal  (1)Blazor  (215)BoldSign  (14)DocIO  (24)Essential JS 2  (107)Essential Studio  (200)File Formats  (66)Flutter  (133)JavaScript  (221)Microsoft  (118)PDF  (81)Python  (1)React  (100)Streamlit  (1)Succinctly series  (131)Syncfusion  (913)TypeScript  (33)Uno Platform  (3)UWP  (4)Vue  (45)Webinar  (51)Windows Forms  (61)WinUI  (68)WPF  (158)Xamarin  (161)XlsIO  (36)Other CategoriesBarcode  (5)BI  (29)Bold BI  (8)Bold Reports  (2)Build conference  (8)Business intelligence  (55)Button  (4)C#  (147)Chart  (130)Cloud  (15)Company  (443)Dashboard  (8)Data Science  (3)Data Validation  (8)DataGrid  (63)Development  (627)Doc  (8)DockingManager  (1)eBook  (99)Enterprise  (22)Entity Framework  (5)Essential Tools  (14)Excel  (40)Extensions  (22)File Manager  (7)Gantt  (18)Gauge  (12)Git  (5)Grid  (31)HTML  (13)Installer  (2)Knockout  (2)Language  (1)LINQPad  (1)Linux  (2)M-Commerce  (1)Metro Studio  (11)Mobile  (506)Mobile MVC  (9)OLAP server  (1)Open source  (1)Orubase  (12)Partners  (21)PDF viewer  (43)Performance  (12)PHP  (2)PivotGrid  (4)Predictive Analytics  (6)Report Server  (3)Reporting  (10)Reporting / Back Office  (11)Rich Text Editor  (12)Road Map  (12)Scheduler  (52)Security  (3)SfDataGrid  (9)Silverlight  (21)Sneak Peek  (31)Solution Services  (4)Spreadsheet  (11)SQL  (10)Stock Chart  (1)Surface  (4)Tablets  (5)Theme  (12)Tips and Tricks  (112)UI  (386)Uncategorized  (68)Unix  (2)User interface  (68)Visual State Manager  (2)Visual Studio  (31)Visual Studio Code  (19)Web  (591)What's new  (331)Windows 8  (19)Windows App  (2)Windows Phone  (15)Windows Phone 7  (9)WinRT  (26)

U.S. Government Goes Open Source

Back in March, the White House released a draft of a Federal Source Code policy for public comment. The purpose of this policy was to “require new software developed specifically for or by the Federal Government to be made available for sharing and re-use across Federal agencies.” In other words, the government was going to go open source.  

         

The reasons for such a move are numerous. A couple of specific goals for the policy, emphasized in the announcement blog with bold text, were saving tax dollars, and encouraging innovation and collaboration between federal agencies. Saving money, unfortunately, is a goal thrown about endlessly in press releases from all levels of government, so a reflexive wariness of such a claim is understandable. However, saving money is virtually guaranteed when it comes to open sourcing software. Say a particular form-filling application is developed for the Department of Energy. If the Department of Defense also needed a form-filling application, it could use the Department of Energy’s application wholesale, or just as a starting point, saving potentially millions of dollars and months of development time over building its own, functionally-identical application from scratch. The federal government already spends more than $6 billion annually on software. No doubt that figure will continue to rise, but promoting code reuse and open source software can help ease the climb. The second goal, fostering innovation and collaboration, is, again, another widely used and abused one, but one that is immediately feasible in the context of open source software.

Last week, the official Federal Source Code Policy was released, outlining a plan for all new federal government software to be available for reuse across all agencies (with some exceptions, of course), and a pilot program for all federal agencies to release at least 20% of new, custom-developed software as open source software for three years. The latter rule in particular will create an environment of active, collaborative software development between the public, the federal government, and even private corporations, allowing technical knowledge to be shared easily across professional and civic divisions, and cultivating better application development through significantly broader user, developer, and knowledge bases. In some sense, you’ll be able to improve the operations of the United States government through a pull request.