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 569127
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Google's problem
by gilboa on Thu 8th Aug 2013 12:02 UTC in reply to "RE[2]: Google's problem"
Member since:

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

RE[4]: Google's problem
by jared_wilkes on Thu 8th Aug 2013 12:24 in reply to "RE[3]: Google's problem"
jared_wilkes Member since:

I haven't blamed anyone. I've said it's Google's problem, and only Google's problem. Not Qualcomm.

However, Thom has BLAMED Qualcomm.

I don't blame Google for selecting the superior tech that everyone else is also choosing. I would make the same choice because I think the ideological values have little value. But I think we should get through the bullshit of Google's hypocrisy, trying to blame everyone else but Google (or worse, claiming there is no way to know if Google, one of the most powerful companies on the planet, can be considered responsible for their own claims and actions or if it's someone else...) for not getting what they would want and/or needing to compromise their ideological goals that get them geek love, and try to state it like it is: Google is unable to deliver on the goals of AOSP in a timely fashion because practical matters will frequently take precedent over ideological values.

Edited 2013-08-08 12:28 UTC

Reply Parent Score: 3

RE[5]: Google's problem
by JAlexoid on Thu 8th Aug 2013 15:46 in reply to "RE[4]: Google's problem"
JAlexoid Member since:

Being at fault/blamed and being the "problem owner" are not necessarily get assigned to the same entity.

If I cock your leg, the pain is your problem but I would be at fault/to blame.

Reply Parent Score: 4

RE[5]: Google's problem
by gilboa on Sat 10th Aug 2013 21:13 in reply to "RE[4]: Google's problem"
gilboa Member since:

I didn't see Google blame Qualacomm for anything. Care to share the source of your information?

- Gilboa

Reply Parent Score: 2