> They largely circumvent a lot of the process with help from policy makers at the highest levels.
> Even then, I'm pretty sure they don't offer hosting/authorizing deployments from party sources. So they essentially have a monopoly on the ability to use OSS freely for bulding government websites.
That's not quite the case. Many agencies use a ton of OSS to build websites and other services.
The policy links above refer to those teams releasing their own code as open source, but you will find huge amounts of outside open source code being used there, and in many other agencies.
The Department of Defense is famous for (in 2003!) making sure their department knew that open source software was A-okay to use, and people refer to their amazing FAQ all the time:
> Even then, I'm pretty sure they don't offer hosting/authorizing deployments from party sources. So they essentially have a monopoly on the ability to use OSS freely for bulding government websites.
That's not quite the case. Many agencies use a ton of OSS to build websites and other services.
https://github.com/cfpb/source-code-policy https://github.com/uscensusbureau/open-source-policy https://github.com/18F/open-source-policy
The policy links above refer to those teams releasing their own code as open source, but you will find huge amounts of outside open source code being used there, and in many other agencies.
The Department of Defense is famous for (in 2003!) making sure their department knew that open source software was A-okay to use, and people refer to their amazing FAQ all the time:
http://dodcio.defense.gov/OpenSourceSoftwareFAQ.aspx
(I'm an 18F employee.)