Open Source for Government
TL;DR: A collaborative resource for government employees looking to participate in the open source community.
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).
If you enjoyed this post, you might also enjoy:
- Why open source
- Everything a government attorney needs to know about open source software licensing
- Open source, not just software anymore
- Five best practices in open source: external engagement
- 19 reasons why technologists don't want to work at your government agency
- Five best practices in open source: internal collaboration
- A White House open source policy written by a geek
- Twelve tips for growing communities around your open source project
- Disclosed source is not the same as open source
- Everything an open source maintainer might need to know about open source licensing
- Why isn't all government software open source?
Ben Balter is Chief of Staff for Security and Engineering at GitHub, the world’s largest software development platform. Previously, as a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →