Skip to main content

What is a Government Evangelist?

3 min read Written while I was at GitHub

Summary: The Government Evangelist role at GitHub is about helping government agencies to ship software better, to fold the map in half, and bring the West coast a bit closer to the East coast. Someone who knows open source, wears a suit, and speaks the agency’s language makes that first scary step easier for everyone.

Two of the most frequent questions I get, as GitHub’s Government Evangelist (other than “is that your real title?”, of course), are “what exactly does a Government Evangelist do?”, almost always followed by “wait, but why would GitHub do that?”. Here’s the what and why, along with why it’s important to the open source community that roles like that exist, at GitHub and elsewhere:

What is a Government Evangelist

In a sentence, the Government Evangelist role at GitHub is about helping government agencies to ship (open source) software better: to fold the map in half, and bring the West coast a bit closer to the East coast. We encourage agencies to take the first, often scary, step into the world of open source, open data, and open government, and to make sure that once they do, the agency has the resources and support they need to succeed.

Use the term “open source” in government, especially around those that wear a suit on a daily basis, and you might conjure up images of hippies with tie-dyed laptops passing around source code like they might pass around an illicit substance. In many agencies, open source isn’t taken seriously, nor is it seen as a potential “enterprise-grade solution”. While closed-source software has dedicated sales teams to have a presence at government technology conferences and explain how their product might improve the agency’s workflow, open source traditionally doesn’t have any such seat at the table. It’s not part of the conversation. And why would it be?

Why does it matter if GitHub has one

From the outside looking in, the government speaks a different language and transacts business differently than the rest of the world. What you and I might call “a site”, an agency, when writing a procurement document, might call that same collection of code a “scalable, cross-platform, digital public engagement platform”. Unfortunately, Google Translate hasn’t yet figured out how to translate between “government” and “geek”.

Government agencies had been using GitHub prior to the role’s creation, but whereas a private-sector firm might just type in their credit card number to upgrade their account to a $25 subscription, those same transactions in government require a certain level of white-glove support. Custom terms of service need to be negotiated (government employees can’t just click “sign up”), new billing mechanisms need to be developed (subscription services can violate the Antideficiency Act), and government-specific resources need to be curated (misinterpretations of government security and privacy frameworks can render open source a forbidden venture).

The government evangelist role gives agencies someone familiar with open source who wears a suit, speaks their language, and knows the unique challenges they face. When they approach us to take that first step towards joining the open source community, we can make it easier (and more successful) for everyone involved.

If we’re going to try and break government out of its anachronistic ways, we’re going to need to expose government agencies to new, leaner ways of working. If you’ve got a project, open source or otherwise, and the government can benefit, speaking their language is just the start.

This is an excerpt, originally posted on opensource.com, and is republished here under a CC-BY-SA license.

Keep reading

Ben Balter

I'm Ben Balter, and I write here about developer platforms, product and engineering leadership, open source, and showing your work. I'm a principal product manager for API (developer) experience at Cloudflare, where I work on making it an even better place to build, for developers and their agents. Before that, I spent over a decade building developer platforms at GitHub. For five years I was a product manager for trust and safety, shipping 500+ features and policies to 50M+ developers, plus github.com API endpoints for trust and safety workflows. I also led a bottom-up rewrite of GitHub Pages, maintained Jekyll, and wrote the plugins most GitHub Pages sites run on. My open source projects have hundreds of millions of downloads. I wrote Open and Async, the playbook for remote and distributed teams. More about the author

Follow along: Bluesky LinkedIn

Originally published October 15, 2014 View revision history

This page is open source Help improve this article on GitHub

Keyboard shortcuts

Search

  • / or ⌘ K Open search
  • ↓ or j ↑ or k Move through results
  • Enter Open the selected result
  • Esc Close search

Go to

  • g then h Home
  • g then p All posts

This page

  • y Copy link to this page
  • ? Show this list

Turn off if you use voice control or keep triggering them by accident. ⌘ K still opens search, and this list stays under "Keyboard shortcuts" in the footer.