opensource.google.com

Menu

Docs

Blog

go/opensourceblog

The Google Open Source Blog is our online voice in the community. We post on a variety of open source topics, including:

  • new open source releases by Google, including 20% projects
  • notable new features or releases of our existing open source projects
  • updates on student programs we run
  • news about upcoming conferences Googlers will be speaking at
  • write-ups of events and talks hosted at Google
  • cross-posts from Google blogs of interest to the open source community

We invite all Googlers to author a post for our blog when they have relevant updates to share with our community. We’re proud that Google shares so much code with the community, so we especially want to post your announcements of new open source releases.

Our publishing process

First, make sure your topic is appropriate for our blog and its audience. If in doubt, email emailremoved@. Make a copy of our request template at go/osposocialtemplate and draft your post. Please include links to relevant sites and, if possible, an image or video to go with the post.

Next, review our checklist at go/osposocial then submit your request at go/osposocialrequest with all the necessary details including when you’d like to publish the post. If you’re flexible, we’ll try to schedule it for a time when it can be our “top story” for a couple of days. We will do an initial review and work with you to produce a final draft. We’ll send that final draft to the rest of the OSPO team for final review.

Ensure emailremoved@ has permission to edit your Doc. We’ll make trivial changes (fixing typos, grammar, etc) and leave comments where we have questions or suggestions. You can always use the document revision history to see any changes made. Please allow two business days for the team to review your post. We can only review complete posts, not diffs or partial drafts.

Please address any review comments left in the Doc. This can be done by implementing a reviewer’s suggestion, answering their question, or explaining why you disagree with a suggestion. Only resolve a comment after taking an action to address it.

Once the reviewers LGTM the post, it will be copied into Blogger and queued for publishing. We’ll notify the author when the post goes live. Once published, we only change posts in exceptional circumstances.

Writing guidelines

Grammar

Please see the Google Style Guide for guidance. Of special importance to this blog, we never hyphenate open source, even when used as a verb. Open source is also meant to be lowercase as it is not a proper noun.

Voice

Posts should be short, to the point and informative. They frequently link to external sites that contain additional details. The tone is consistent with the overall Google voice, but can be more technical in nature given our audience. Posts with technical details tend to attract more readership.

Images and videos

A few pictures or illustrations can turn a good post into a great one. Videos can communicate inspiring stories and demos. We can embed them in blog posts as long as we have the legal right to use them.

This means at least one of these must be satisfied:

  • we created it ourselves (It’s owned by Google)
  • it’s under a Creative Commons license that does not restrict commercial use
  • we have written permission from the copyright holder to use it in this way

and:

  • we have permission from everyone in the picture to post their image

Always give proper attribution to content we didn’t create ourselves, generally as a caption under the embedded content.

We often use screenshots, charts, photos of team members, event photos and product logos in posts. The first image in a post will be used as a thumbnail in the Blogger interface and on social media, so make it a good one. (A post with no images has no thumbnail. Please try to find a suitable image.)

Permissions

If your blog post includes the name or photo of anyone who is not a Googler, we will need written consent to publish the post. An email will suffice. However, we need a special release form signed if the person is a minor.

Byline

Blog posts are signed {Name}, {Team}. We generally don’t list roles or titles. Some examples:

  • Stephanie Texas, Open Source Programs Office
  • Brian Freedom, Chicago Engineering Team
  • Michael Serious, Site Reliability Engineering Team

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.