Sponsors

  • Microsoft
  • Nebula
  • Google
  • SugarCRM
  • Facebook
  • HP
  • Intel
  • Rackspace Hosting
  • WSO2
  • Alfresco
  • BlackBerry
  • CUBRID
  • Dell
  • eBay
  • Heroku
  • InfiniteGraph
  • JBoss
  • LeaseWeb
  • Liferay
  • Media Temple, Inc.
  • OpenShift
  • Oracle
  • Percona
  • Puppet Labs
  • Qualcomm Innovation Center, Inc.
  • Rentrak
  • Silicon Mechanics
  • SoftLayer Technologies, Inc.
  • SourceGear
  • Urban Airship
  • Vertica
  • VMware
  • (mt) Media Temple, Inc.

Sponsorship Opportunities

For information on exhibition and sponsorship opportunities at the convention, contact Sharon Cordesse at scordesse@oreilly.com

Download the OSCON Sponsor/Exhibitor Prospectus

Contact Us

View a complete list of OSCON contacts

Android Infrastructure, the Workings behind the Curtain

John Hawley (Red Hat), Shawn Pearce (Google)
Tools and Techniques
Location: Portland Ballroom
Average rating: ***..
(3.17, 6 ratings)

Pull back the metaphorical curtain of any popular open source project and you will find a support structure that is holding the whole thing together, often with duct tape, spit and chewing gum. This is particularly true of large projects that have grown rapidly, like Google’s Android project. It now encompasses an uncountable number of devices, from phones and tablets to microwaves. We aim to layout how the infrastructure works, what pain points have come up and try and get feedback from the community on what they might want more of or generally need.

Things covered
  • Git – The Source code
  • Repo – Why it’s needed, what it does and why it works
  • Gerrit Code Review
  • Gitweb
  • The hardware needed to serve thousands of worldwide developers
Photo of John Hawley

John Hawley

Red Hat

John ‘Warthog9’ Hawley was led the system administration team on kernel.org for nearly a decade leading a team including four other administrators. He specifically worked on system operations, the wikis and the kernel.org Gitweb. His other exploits include working on Syslinux, OpenSSI, a caching Gitweb, and patches to bind to enable GeoDNS. He’s the author of PXE Knife, a set of interfaces around common utilities and diagnostics tools needed by an average systems administrator. He currently works for Red Hat working on all things storage related within OpenShift. In his free time he enjoys cooking extravagant meals and watching bad movies.

Shawn Pearce

Google

Shawn Pearce is the second in command of the Git project. He has been actively involved in the project since early 2006, contributing more than 1300 changes in 3 years. Shawn is the author of git-gui, a Tk based graphical interface shipped with git, and git-fast-import, a stream based import system often used for converting projects to git. Besides being the primary author of both git-gui and git-fast-import, Shawn’s opinion, backed by his code, has influenced many key design decisions that form the modern git implementation.

In early 2006 Shawn also founded the JGit project, creating a 100% pure Java reimplementation of the Git version control system. The JGit library can often be found in Java based products that interact with Git, including plugins for Eclipse and NetBeans IDEs, the Hudson CI server, Apache Maven, and Gerrit Code Review, a peer code review system specially designed for Git. Today he continues to develop and maintain JGit, EGit, and Gerrit Code Review.

Comments on this page are now closed.

Comments

Picture of Benoit Sigoure
Benoit Sigoure
07/29/2011 12:29pm PDT

Quite surprised that the whole thing hasn’t been sharded yet. Maybe gitweb itself doesn’t lend itself to sharding easily. The Google way of solving this problem would be to use a whole bunch of little 1U boxes, each serving a subset of the repos, and dispatch requests to the appropriate boxes. Can’t Google dedicate some engineering time to solve this problem and build in the open-source a better, scalable way of serving tons of Git repositories to many people?

Mark Deason
07/29/2011 12:17pm PDT

truly behind the curtains, but cool anyway