White House Further Embraces Open Source For Government... But Tell It To Do Even More

from the good-to-see dept

This policy requires that, among other things: (1) new custom code whose development is paid for by the Federal Government be made available for reuse across Federal agencies; and (2) a portion of that new custom code be released to the public as Open Source Software (OSS).

Would an “open source by default” approach that required all new Federal custom code to be released as OSS, subject to exceptions for things like national security, be more or less effective in achieving the goals above?

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community. Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis. While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

With so much annoying stuff coming out of the White House lately, it's good to see the tech folks there continue to do some good work, including pushing for a policy that should lead to further embracing open source technologies inside the federal government -- in part by pushing the government itself to open source the code it writes for its own work (and even when not releasing the code to the public, at least sharing it inside the government for other agencies to use).This new policy has been put out for comment, andwith this policy. The current request asks if the policy could be improved in the following manner:I think the answer to this question needs to be that, yes, such a policy would be greatly improved by pushing for open source by default. With the current policy stating that just "a portion" of the code is released that way, it almost guarantees thatwill be. Moving to a policy where it's open source by default would lead to a design mentality that keeps that in mind.Of course, some may (quite reasonably!) argue that copyright does not apply to any works created by the federal government itself (though itto anything written by contractors, who can then assign that copyright to the government). Thus, if the software in question was created by federal employees, then it should, automatically be, in which case the government has no legal right to placelegal restrictions on its use, even open source restrictions. Though, of course, in that case, it still has to make the decision over whether or not to release the code publicly. Unfortunately, the current policy says that it would apply to software written by federal employees as well -- and that might actually not be allowed under the law. That software is in the public domain.Of course, it's likely that plenty of code used in government is actually written by contractors, and for that code, the default shouldbe that it be open sourced whenever possible.For what it's worth, rather than the annoying standard commenting process for most government comments, this one is being done on Github , so join in.

Filed Under: code sharing, copyright, federal government, open source, public domain