opensource.google.com

Menu

Docs

Releasing and Publicizing

go/releasing/publishing

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

Cryptography compliance

go/releasing-crypto

The regulations surrounding cryptographic software are notoriously complex, so we have people who specialize in complying with them.

You do not need to contact the export compliance team if your project only provides encryption functions relating to authentication and digital signatures. However, if your project performs or uses data encryption — such as providing crypto libraries or using https, OpenSSL, OpenVPN, or other encryption protocols to make a secure communication — then email emailremoved@ on the day that your code is made public with the following information:

  • Google project owner name(s)
  • Google product name (e.g., Google AdWords API)
  • The URL where the source code will be published.

If you have any questions about this specific topic, please email emailremoved@.

Required disclaimer

Unless your project is an official Google product, you must state “This is not an official Google product.” in an appropriate location such as the project’s README file.

Discussion forum

GitHub does not provide any kind of discussion group for your project; for that you’ll need to create a public one on Google Groups.

  • Group name and email address should both be set to your project’s name
  • In “Basic Permissions”, allow the public to both view and post messages

Make sure you advertise the group’s existence on your project’s home page. You can also use the embeddable Groups widget if you’d like.

Publishing apps in Google Play

If you’ve released code for an Android project, you’ll likely want to share a build of it somewhere end users can find it. Google has official accounts in the Google Play Store which are used to publish apps we want to keep associated with Google’s brand. Send an email to emailremoved@ and ask them if your app should be released via one of those accounts. If so, they will provide directions on how to proceed.

Publishing apps in the Chrome Web Store

If you want to get a Chrome App or Extension released as officially “by Google”, please see the Chrome Web Store team’s instructions. Most open source Chrome Apps and Extensions won’t be published as “by Google” and you may publish them in the store using your personal developer account after completing all previous steps of this go/releasing process.

Telling the world

Here are some ideas for stirring up interest in your project. We recommend getting these ready before making the project visible to the public and posting them on your launch day.

  • Add your project to the Open Source Project Database.
  • Post to any mailing lists or forums where an announcement of your project would be on-topic
  • If you have a personal blog, blog about your project.
  • Write a post for the Google Open Source Blog – we love to feature new projects or major updates.
  • Use the Corp Comms Social Toolkit at sites/social-toolkit
  • Speak at conferences about your project; please see the Corp Comms Speaker Center at go/speakercenter for details

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.