Language Selection

English French German Italian Portuguese Spanish

White House continues push to open source federal code

Filed under
OSS

The White House on Thursday issued a draft policy for public comment that would support making computer code used by federal agencies open source.

It's part of an on-going effort by the Obama administration to make government computer systems more efficient both by using open source programs and by releasing code written by government agencies both inside and outside the government to use.

Read more

Lots more coming...

  • OMB’s 3rd policy memo in a week targets software purchasing

    The Office of Management and Budget’s busy week continued Thursday with its third policy memo in the last seven days.

    Along with a draft data consolidation guidance and a final mandate for every agency to set up a Buyers Club for innovative acquisitions, OMB now is taking aim at the software that runs in those data centers and is bought by those procurement experts.

    Federal Chief Information Officer Tony Scott released a draft open source software policy March 10 with a goal of reducing duplicative purchases and taking advantage of industry best practices.

  • Are you ready to share your code?

    The Office of Management and Budget has released a draft policy to improve how custom code developed for the government – including code developed by contractors – is acquired and distributed.

  • White House wants more sharable, reusable code

    The White House is looking to make software code used by the federal agencies more open, sharable and reusable. In a March 10 blog post, federal CIO Tony Scott announced a new draft Federal Source Code policy that would create a new set of rules for custom code developed by or for the federal government.

  • Agencies would face new open source software requirements under OMB draft policy

    The White House issued a draft policy today that would require federal agencies to open source a significant portion of its software code. Under the proposed Federal Source Code Policy, the Office of Management and Budget would pilot the requirement to share publicly all custom code developed in-house by federal IT personnel and at least 20 percent of newly developed custom code by third party developers or vendors on behalf of a covered agency.

  • OMB moves to make all federal code open source

    The administration has been looking to embrace the best practices in software development, using innovation shops like 18F and the U.S. Digital Service to test and promote methods like agile development and making use of open source code.

    Now, the entire federal government will be getting on board with the latter. The Office of Management and Budget released the first draft of the Federal Source Code policy, a mandate to make federally-developed code available to everyone.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

Linux-Ready Hardware and Android Leftovers

Red Hat, Oracle's RHEL Clone, and Fedora

Debian and Derivatives: SnowCamp, Debian Gitlab, Debian/TeX Live, Snap Apps

  • Report from Debian SnowCamp: day 3
    Thanks to Valhalla and other members of LIFO, a bunch of fine Debian folks have convened in Laveno, on the shores of Lake Maggiore, for a nice weekend of relaxing and sprinting on various topics, a SnowCamp.
  • Report from SnowCamp #1
    As Nicolas already reported, a bunch of Debian folk gathered in the North of Italy for a long weekend of work and socialisation.
  • Debian Gitlab (salsa.debian.org) tricks
  • Debian/TeX Live 2017.20180225-1
    To my big surprise, the big rework didn’t create any havoc at all, not one bug report regarding the change. That is good. OTOH, I took some time off due to various surprising (and sometimes disturbing) things that have happened in the last month, so the next release took a bit longer than expected.
  • Ubuntu Software Will Soon Let You Install Beta, Bleeding Edge Snap Apps
    No, not TV channels, or the sort the that ferries goods between countries, but development channels, e.g, beta, bleeding edge, stable, etc. Snap developers are able to distribute different versions of their app over “channels”, and have for almost as long as Snappy has been around in fact.