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

Games and CrossOver

Red Hat and Fedora

Android Leftovers

Leftovers: OSS and Sharing

  • CoreOS Tectonic Now Installs Kubernetes on OpenStack
    CoreOS and OpenStack have a somewhat intertwined history, which is why it's somewhat surprising it took until today for CoreOS's Tectonic Kubernetes distribution to provide an installer that targets OpenStack cloud deployments.
  • Docker and Core OS plan to donate their container technologies to CNCF
    Containers have become a critical component of modern cloud, and Docker Inc. controls the heart of containers, the container runtime. There has been a growing demand that this critical piece of technology should be under control of a neutral, third party so that the community can invest in it freely.
  • How Blockchain Is Helping China Go Greener
    Blockchain has near-universal applicability as a distributed transaction platform for securely authenticating exchanges of data, goods, and services. IBM and the Beijing-based Energy-Blockchain Labs are even using it to help reduce carbon emissions in air-polluted China.
  • An efficient approach to continuous documentation
  • The peril in counting source lines on an OSS project
    There seems to be a phase that OSS projects go through where as they mature and gain traction. As they do it becomes increasingly important for vendors to point to their contributions to credibly say they are the ‘xyz’ company. Heptio is one such vendor operating in the OSS space, and this isn’t lost on us. :) It helps during a sales cycle to be able to say “we are the a big contributor to this project, look at the percentage of code and PRs we submitted”. While transparency is important as is recognizing the contributions that key vendors, focus on a single metric in isolation (and LoC in particular) creates a perverse incentive structure. Taken to its extreme it becomes detrimental to project health.
  • An Open Source Unicycle Motor
    And something to ponder. The company that sells this electric unicycle could choose to use a motor with open firmware or one with closed firmware. To many consumers, that difference might not be so significant. To this consumer, though, that’s a vital difference. To me, I fully own the product I bought when the firmware is open. I explain to others that they ought to choose that level of full ownership whenever they get a chance. And if they join a local makerspace, they will likely meet others with similar values. If you don’t yet have a makerspace in your community, inquire around to see if anyone is in the process of forming one. Then find ways to offer them support. That’s how we do things in the FOSS community.
  • The A/V guy’s take on PyCon Pune
    “This is crazy!”, that was my reaction at some point in PyCon Pune. This is one of my first conference where I participated in a lot of things starting from the website to audio/video and of course being the speaker. I saw a lot of aspects of how a conference works and where what can go wrong. I met some amazing people, people who impacted my life , people who I will never forget. I received so much of love and affection that I can never express in words. So before writing anything else I want to thank each and everyone of you , “Thank you!”.
  • Azure Service Fabric takes first tentative steps toward open source [Ed: Microsoft Peter is openwashing a patent trap with back doors]
  • Simulate the Internet with Flashback, a New WebDev Test Tool from LinkedIn
  • Mashape Raises $18M for API Gateway Tech
    Casado sees Mashape's Kong API gateway in particular as being a particularly well positioned technology. Kong is an open-source API gateway and microservice management technology.
  • PrismTech to Demonstrate Open Source FACE 2.1 Transport Services Segment (TSS) Reference Implementation at Air Force FACE Technical Interchange Meeting
    PrismTech’s TSS reference implementation is being made available under GNU Lesser General Public License (LGPL) v3 open source license terms.
  • How Open-Source Robotics Hardware Is Accelerating Research and Innovation

    The latest issue of the IEEE Robotics & Automation Magazine features a special report on open-source robotics hardware and its impact in the field.