opensource.google.com

Menu

Docs

Getting Approval

go/releasing/approval

(This is part of the process for releasing Google-owned code as open source. There are different processes for patches and personal projects.)

Like any release at Google, open source releases are managed through Ariane. After preparing your project and staging the code on an internal git-on-borg repo at go/gob-user, create an entry on the Open Source launch calendar (go/opensource-launchcal). This includes personal projects that have not gone through IARC, even for DevRel engineers. If you are in DevRel and want to release sample code for an already launched product, see DevRel Releasing.

  • Add your director as an approver for the Eng bit
  • Include a link to your code in the description field.
  • Ensure all reviewers have read access to your code.
  • Wait for approval.

During review, some of the major things we look for include:

  • doesn’t include anything linked to Google’s “secret sauce” (e.g. ranking, filtering, etc…)
  • sharing helps users, not just our competitors
  • any non-Google code is in a third_party directory
  • license compliance with any third-party dependencies
  • doesn’t violate a country’s laws
  • patent issues
  • privacy issues (see below)

A legal review will be required if your code collects any data about users and transmits it back to us or if it affects or transmits third-party content. We’ll add the right people to the launch calendar entry, but if you mention this in the description, it will help minimize delays.

We’ll use the launch calendar entry to ask questions and discuss any potential problems, but it’s generally a smooth process. Once you receive full approval, continue on to the next step in this process.

DevRel, Cloud DevRel, and Ads DevRel releasing

DevRel teams producing sample code and example applications directly related to a released Google product may go through the expedited approval process by writing “DEVREL” in the notes for the Eng bit and flipping the bit yourself. If a launch is not complete within 3 days of filing, please email emailremoved@ directly.

DevRel teams may use private GitHub repos to stage code related to I/O or marketing deadlines, but only after licensing and patents approval on the launch calendar. They must specify a fixed and reasonable deadline for deleting the repo or making it public.

Here’s some handy templates: go/dpe-launch, go/cloud-dpe-launch.

Additional instructions for DevRel teams can be found at go/dpe-oss and go/gcp-github.

Except as otherwise noted, the content of this page is licensed under CC-BY-4.0 license. Third-party product names and logos may be the trademarks of their respective owners.