Google launches Open source project rollup site

This is a creation in Article, where the information may have evolved or changed.

Free open source software has always been part of Google's technology and organization base. From the server running the Linux kernel to the internal culture of repairing arbitrary team code, open source is also part of Google's work. In return, Google released millions of lines of open source code, launched Google Summer of code, Google code-in and other programs, and through Software Freedom Conservancy, Apache software Fou Ndation, as well as many other organizations, has sponsored open source projects and communities.

Today, Google launches opensource.google.com, a new website for Google Open Source, which integrates information about Google's Open source projects and describes how Google uses, publishes, and supports open source.

Help you find interesting open source code

One of the principles of Google's release of open source code is that "much is good" and helps the team to publish code as much as possible. As a result, Google launched thousands of projects, including TensorFlow, Go, Kubernetes and other large products, including light My Piano, Neuroglancer, Periph.io and other small projects. A number of projects have been fully supported, and some are experimental or entertaining. Because these open source projects involve more than 100 GitHub organizations and Google's Git services, it is sometimes difficult to grasp the scope and scale of these open source projects.

To provide a more holistic view, Google launched a summary of its open source projects, which will continue to enrich over time. On top of that, we've also added some information about how these projects are used within Google. In the future, Google wants to add more information about the project lifecycle, maturity, and more.

How to do open source

Open source is about more than just code, it's about communities and processes. In 2014, Google pushed for the creation of the TODO Group, which provides a forum where promising open-source companies work together to share best practices. Based on a number of discussions over the years. Google has published internal documents on how to do open source.

These documents describe the process by which Google launches new Open source projects, submits patches to other projects, and how Google manages open source code that is introduced within the company. In addition to "How to do", these files describe what Google "does", such as why it only uses code under a specific license or why it is required to provide a Contributor license agreement for all patches that Google receives.

Google's policies and procedures benefit from the experience gained over the years. These approaches to open source may not be suitable for everyone, and there is more than one way to do open source. Google wants to inspire people by thinking about open source projects.