This document summarizes Google's use of open source software and participation in open source projects. It discusses how Google uses open source for its infrastructure and as building blocks. It also outlines Google's open source programs like Summer of Code and releasing over 23 million lines of open source code. The document also briefly discusses NASA's reasons for and against using open source, including potential benefits like speed of implementation but also risks around contractor copyright and export rules.

1. Google, NASA and Open Source Chris DiBona Tuesday, March 29, 2011

2. Who Am I? Open Source Programs Manager, Google Inc. License Compliance Code Release The Summer of Code & Google Code-In Protocol, specification and API Licensing Public Sector: Google Moderator Polling Locations API Education Commons (Rwanda/CARTA) Also and Formerly: Slashdot, Co-Editor Open Sources & Open Source 2.0,Floss Weekly Podcast, TechTV, Cranky Geeks. Google Confidential

3. Agenda Google Confidential

4. Me

5. A Bit About Open Source Google Confidential

6. License Use Across 31m Crawled Files FLOSS License De Duped Files Percentage GPL 14,851,615 47.06% LGPL 7,145,795 22.64% BSD 4,245,335 13.45% Apache 1,778,692 5.64% MIT 1,565,673 4.96% Mozilla 567,604 1.80% Perl 333,829 1.06% QPL 206,085 0.65% Artistic 150,555 0.48% CPL 144,128 0.46%

7. Amounting to >2 billion lines of code….

8. Open Source Software Use at Google Google Confidential

14. What is ‘ Google ’ In-house rack design PC-class motherboards Low-end, large size storage and networking hardware Running Linux + in-house software

15. How does Google use Open Source ? As Infrastructure Linux kernel Many Apache Project Tools SSH, and other system management tools The Languages and compilers that we use. Engineers and others running Linux (Goobuntu) As building blocks Our repositories have hundreds of libraries used in Google software

16. But Why does Google use Open Source Control and Ownership Maintain our independence from external software companies Adaptability and Flexibility We can drill down to repair and enhance our services If we want to do something out of the ordinary, we can do so without showing our hand No one is incentivized to hurt us Roots Appeals to the Google ethic

17. How does Google take part?

18. Google’s Open Source Programs Patching and Code Release Internal License Discipline API/Protocol License Discipline Open Source Infrastructure & Leadership Summer of Code Donations/Funding Industry Trade Group Participation

19. We release open source code We Patch into hundreds of projects each month Strategically important Helps the internet grow fairly. ~900 projects to date.* API Examples Dev Tools Linker Build/test Memory and thread management Plugins for eclipse DVCS patches. Infrastructure Approximately 23m lines of code released with the above and major projects like Android, GWT, WebM, Chromium and others. *See Label:Google on http://code.google.com/p

20. What About NASA?

21. NASA and open source, why? Increase speed of procurement Technology Transfer to (and from) aerospace Earth & Computer Science improvements Speed of implementation can be improved when more source is shared amongst NASA missions and with the outside world.

22. NASA and open source, why not? Contractor copyright hoarding Existing tech transfer budget justifications ITAR and export rules Public Domain vs Licensing issues And Finally…

23. Mission Risk Are missions endangered when source is shared? Then why is so much oss used in aerospace? Unmanned flights can be more risky.

24. The End [email_address] http://code.google.com/opensource