Now You Can Do Google Open Source with new website

Google releases new website for open source projects

Google = Open Source!

Or at least that is what their new website demonstrates showing off many of their contributed many technologies for public use but one has to wonder why a multi-billion dollar company would give out and consume essentially free software.

Today, Google took off the wraps of its new Google Open Source projects website to further demonstrate their efforts and to possible help some other companies and customers who are looking to move into open source development.

Google Open Source, opensource.google.com, brings together all its open-source initiatives including highlights, some new graphics and descriptions of its “2,000 projects and counting.”   Some of these were are already familiar with and have been working to integrate for internal development projects here at CWH.   For example, Kubernetes which we have been deploying across multiple infrastructure regions, as well as TensorFlow, Neuroglancer, Dart, and Blockly to name a few.   Of course the size and scope of these projects may vary but typically most of them have a purpose or a specific need that they were built for.  For example, Oppia which was built to show and demonstrate interactive educational activities.

As part of this project, Google is creating an easy to use listing of its open source projects including details on how and what Google uses them for including some interesting nuggets of information on how google actually runs its projects.

On the jus released website, you can visit this link to see and follow the process for releasing new open source projects that Google goes through including outlining patch submission processes, management of 3rd party open source code that it brings into its own projects and more importantly they provide some interesting details on the “how” of what they do they tell you “why.”   These details outline why Google only uses code under certain licenses or the need to require contributor license agreements for all patches they receive including one time and ongoing patch submissions.

I have to wonder why Google is trying to make a splash over their open source projects. Are they trying to appear more developer focused despite being an industry juggernaut?  Are they defining a “standards” methodology without explicitly saying so?   Is it related to the antitrust charges that Google is continuing to see including recent charges by the European Union?

Regardless of the reasons, I like the site and the information provided can in fact be very useful.

1 COMMENT

LEAVE A REPLY

Please enter your comment!
Please enter your name here