Google on Open – mixed feelings

So Jonathan Rosenberg, Senior Vice President, Product Management, teaches us all on his understanding of “open” in various fields in this article over at the official Google Blog. I gather that he reflects a sort of canonical defintion that somehow is used or should be used inside Google.

It leaves me with mixed feelings.

It contains a lot of good stuff on open standards (yet fails to point to a proper definition), it tells us about Open Source and Google (and contains the typical claim that they are the “biggest contributor to open source” – a claim used inlfationary across all tech companies).

But it also contain stuff that really surprises me in negative ways. Let’s go through some stuff and you, dear reader, decide yourself:

If the GNU C compiler that I’m using has a bug, I can fix it since the compiler is open source. I don’t have to file a bug report and hope for a timely response.

Well – you should file a bug report and put your fix into that bug report so the whole community of GCC users and devs can have a better solution … private fixes == private fork == non-open …

If existing standards aren’t as good as they should be, work to improve them and make those improvements as simple and well documented as you can. Our top priorities should always be users and the industry at large and not just the good of Google, and you should work with standards committees to make our changes part of the accepted specification.

The problem here is a seemingly ignorant attitude towards “upstreaming” modifications. Just as with the GCC example, Mr. Rosenberg seems to favour private forks of standards to gain a competitive advantage and treat the upstreaming as a nice-to-do afterwards. In my world, you would *first* try to upstream your modifications (to make sure you get sustainable support) and *secondly* base your product on the modifications.

Today’s open source goes far beyond the “patent pooling” of the early auto manufacturers,

Patent-pooling creates a *closed* community – nothing open or competitive. See how GSM patents are used to deliberately hinder competitors to enter the market. Same with MPEG patents.

Also Open Source in general has *never* created a patent pool. Open Source has *always* opposed software patents.

“Others can take our open source code, modify it, close it up and ship
it as their own.”

So how is *that* open?

Don’t get me wrong, there are some good things in that article, but in general it leaves me with mixed feelings.

CC BY 4.0 This work is licensed under a Creative Commons Attribution 4.0 International License.

4 thoughts on “Google on Open – mixed feelings”

  1. Google’s philosophy means fuck all, just look at their actions;

    Android: forking java, Linux, ignoring the Linux ecosystem
    ChromeOS: fork of Ubuntu (which is itself a Debian fork)
    Chrome/Chromium: initially tons of embedded code copies and forks

    Google are (ab)users of free software, definitely not part of the free software community.

  2. These private forks are really starting to burn google. They realized after a while that out of band forks on the kernel were impossible to maintain and they payed the price for it. I guess that message never made it upstairs to management.

Comments are closed.