I encourage you to read through Open Source for Government, a collaborative resource for government employees looking to participate in the open source community.
Also please feel free to fork and contribute (no technical knowledge necessary).
I encourage you to read through Open Source for Government, a collaborative resource for government employees looking to participate in the open source community.
Also please feel free to fork and contribute (no technical knowledge necessary).
Like what you read? Subscribe via RSS to get notified when new posts are published.
More to explore
The White House Open Source Policy should prefer existing platforms, build real communities, and share code as widely as possible.
Open source has always been about the right to modify, not contribute. As those workflows spread beyond software, we may need a new word.
Publishing code without fostering community isn't open source — it's disclosed source. True open source is a two-way relationship.
Eight reasons government contractors should embrace open source — from free advertising and better code to attracting top talent.
What a GitHub Government Evangelist does: help agencies ship software better and bring Silicon Valley practices to Washington.
What government lawyers need to know about open source licensing — from MIT to GPL, consuming, publishing, and accepting contributions.
Change aversion, lack of technocratic leadership, and heavyweight processes bred by distrust keep government IT 5-10 years behind the private sector
From enterprise FUD to closed-source contractors to a culture of no, an entire value chain keeps taxpayer-funded code behind the firewall.
CFPB's open-source policy nails code procurement and publishing, but misses the secret sauce of actively participating in the open-source community.