Linked by Thom Holwerda on Wed 7th Aug 2013 19:14 UTC
Google Jean-Baptiste Queru, or JBQ for short, maintainer of the Android Open Source Project at Google, has announced that he's quitting his job.

Well, I see that people have figured out why I'm quitting AOSP.

There's no point being the maintainer of an Operating System that can't boot to the home screen on its flagship device for lack of GPU support, especially when I'm getting the blame for something that I don't have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.

By the way, in this context, 'to escalate' means handing something over to your superiors so they can handle it. I believe this definition of the word is uncommon outside of the US.

The issue here is exactly what it sounds like: there are currently no factory images/binaries available for the latest Nexus device, the new Nexus 7. The problem is that the GPU in the new Nexus 7 is made by Qualcomm, a company which is incredibly hostile towards the open source community. This isn't the first time Qualcomm has sabotaged an AOSP launch - all Nexus devices with Qualcomm chips, the Nexus 1, 4, and the new 7, faced these problems.

Because he is apparently very good at pattern recognition, JBQ states that he already anticipated this issue six months ago, but that it hasn't been solved. A recent tweet from him is quite telling:

That feeling when lawyers sabotage the launch you spent 6 months working on? I haz it. Sad sad sad sad sad sad.

This is bad news for Google, and bad news for Android. JBQ has done an amazing job on AOSP, and I'm very sad to see him leaving his post. As of this moment, it's not yet known whether he will leave Google entirely or not.

Thread beginning with comment 569096
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Google's problem
by gilboa on Thu 8th Aug 2013 04:38 UTC in reply to "Google's problem"
gilboa
Member since:
2005-07-06

AFAIK, the issue is not open source, but the lack of *binary* distribution rights.

I do agree that Google should have booted Qualcomm from the next Nexus device in return.

- Gilboa

Reply Parent Score: 6

RE[2]: Google's problem
by jared_wilkes on Thu 8th Aug 2013 11:40 in reply to "RE: Google's problem"
jared_wilkes Member since:
2011-04-25

Sure, but it doesn't change the problem. I was just stating it as simply as possible -- but in some audiences that just leads to problems.

Qualcomm has never pledged the the same things that Google has and it has no obligation to.

It's Google's obligation to use vendors who do support the same goals or who can be contractually persuaded or coerced into complying with their goals or risk looking like stupid hypocrites. (Of course, people like Thom will Cover Google's Ass for them, for free, and blame it on someone else).

Reply Parent Score: 1

RE[3]: Google's problem
by gilboa on Thu 8th Aug 2013 12:02 in reply to "RE[2]: Google's problem"
gilboa Member since:
2005-07-06

Sure, but it doesn't change the problem. I was just stating it as simply as possible -- but in some audiences that just leads to problems.

Qualcomm has never pledged the the same things that Google has and it has no obligation to.

It's Google's obligation to use vendors who do support the same goals or who can be contractually persuaded or coerced into complying with their goals or risk looking like stupid hypocrites. (Of course, people like Thom will Cover Google's Ass for them, for free, and blame it on someone else).


I wouldn't be quick to judge who's to blame without knowing all the details.

- Gilboa

Reply Parent Score: 3