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 569109
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Google's problem
by lucas_maximus on Thu 8th Aug 2013 07:26 UTC in reply to "RE: Google's problem"
lucas_maximus
Member since:
2009-08-18

In a lot of orgs tend to never learn their lesson and normally the choice as we both know is rarely made by those that write the software as to whether to go with a particular company/tech.

Reply Parent Score: 4

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

Yes, and we also know a lot of people who write the software (or blog posts) will take it personally and blame the wrong party for completely selfish reasons as JBQ and Thom are attempting to do in this case, even though that's completely absurd.

Reply Parent Score: 3

RE[4]: Google's problem
by lucas_maximus on Thu 8th Aug 2013 18:09 in reply to "RE[3]: Google's problem"
lucas_maximus Member since:
2009-08-18

What happens a lot and a lot of bloggers won't admit it (including Thom), Is that when it comes to development software most of them have very little or no experience actually being in the development process.

This talk basically says a lot about what a lot of software engineers already know.

http://www.youtube.com/watch?v=6lONh2bHHjI

The scary thing is that this is the tip of the iceburg.

Edited 2013-08-08 18:10 UTC

Reply Parent Score: 2

RE[3]: Google's problem
by Soulbender on Thu 8th Aug 2013 16:01 in reply to "RE[2]: Google's problem"
Soulbender Member since:
2005-08-18

True but that still means it's Google's mistake and its not primarily Qualcomm's fault things didn't work out.

Reply Parent Score: 3

RE[4]: Google's problem
by lucas_maximus on Thu 8th Aug 2013 18:02 in reply to "RE[3]: Google's problem"
lucas_maximus Member since:
2009-08-18

Yes of course. I was expanding on what you said.

Reply Parent Score: 2