Oct 2017 – Apr 2019 · 1 yr 6 mos · Remote

• After spending 3 years working closely with communities and companies that build open source software on GitHub, a common theme emerged: GitHub can't directly solve every problem in software development, and developers don't want us to. Instead, they want GitHub to be a platform that connects to all their favorite tools.
• So I moved back into Engineering to to make the GitHub platform more capable and easier to build on. I helped define company-wide Product strategy around evolving GitHub into a platform for software development, lead a team that built and shipped a GitHub + Slack integration (https://slack.github.com/), and created a framework for building GitHub Apps (https://probot.github.io/).

Jan 2016 – Oct 2017 · 1 yr 9 mos · Remote

• In January 2015, the GitHub community wrote a widely publicized letter to express their frustration and disappointment. After coordinating the response to "Dear GitHub" (https://github.com/dear-github/dear-github/pull/115), I was asked by our VP of Product and Marketing to create a team that could ensure we live up to our responsibility to the open source community.
• I hired a new team, lead a strategic planning process, and coordinated our efforts as a team. We created a direct channel between high-value open source maintainers and the GitHub product organization, giving maintainers the opportunity to surface challenges, and giving product managers the opportunity to get feedback.
• Our team also shipped several significant resources to help address some of the challenges we identified in the open source community, including the Open Source Guides (https://opensource.guide/), the largest and most comprehensive survey of the open source community to date (http://opensourcesurvey.org/2017/), and a program to encourage companies to regularly contribute to open source (https://opensourcefriday.com/).

Jan 2015 – Jan 2016 · 1 yr · Remote

• After realizing I spent most of 2014 paying off debt from poorly managed open source projects, I shifted my attention to our own open source practices in order to turn GitHub into a shining example of corporate involvement in open source.
• I set out to systematize our internal processes around open source: drafting guidelines for managing our own projects, creating a process for releasing open source projects responsibly, sunsetting open source projects that were no longer actively maintained, and creating internal incentives for employee participation in open source. We created a strong internal community of people across the company who were passionate about open source, which led to the creation of several teams focused on supporting the open source community.

Dec 2011 – Jun 2015 · 3 yrs 6 mos · Remote

Jan 2011 – Dec 2011 · 11 mos

May 2006 – Jan 2011 · 4 yrs 8 mos

Jun 2002 – May 2006 · 3 yrs 11 mos