Recognizing the vital role that open source software plays at Google, we of the Open Source Programs Office are tasked with maintaining a healthy relationship with the open source software development community.
We do this by releasing Google-created code, providing vital infrastructure, supporting open source organizations, handling internal open source compliance, and by running student outreach programs such as Google Summer of Code and Google Code-in.
Explore the different ways we serve the open source community
through these sites on Google Code:
Google and Open Source
I'm a paragraph. Click here to add your own text and edit me. I’m a great place for you to tell a story and let your users know a little more about you.
Which projects are being released?
We've chosen 4 projects to start out. Perftools, sparsehashtable, coredumper and goopy/functional. Details can be found at http://code.google.com/projects.html.
Why did you choose these particular projects?
Well, several reasons, actually.
Google Engineers picked them.
You may have heard about 20% time, in which Google engineers are encouraged to work on a personal project one day out of the week. Open Source interests a lot of Google developers, so we thought taking advantage of this program was a good way to prepare code for release and maintenance.
They make future releases possible.
The programs we've chosen are all what we consider infrastructural programs. By releasing these tools, we will be able to release more software that relies on them later.
These are the ones that were ready first.
Are these programs still in active use at Google?
They aren't just in active use; they're in active development. These first projects are all current, actively maintained code straight out of our repositories, and as we improve them, those improvements will be merged into the free code base.
Who is their intended audience?
The code we're initially releasing is targeted at professional software development engineers who work with multi-threaded templated C++ code or who want functional features in python. We know that this is a somewhat limited audience; we made this decision specifically so we can work with a smaller community to iron out any bugs in our release and ongoing maintenance processes.