Wow! You really seem to believe that this could happen.
version control
.
Google know who wrote it. We know the software is called gslite (previously gstumbler) and we know the 8 lines or so of offending code. It was written to take the data collected by Kismet (Free open source software that you or I could use to sniff WiFi data) and discard useless information, write the rest into Google's filesystem.
Kismet doesn't discriminate data. It collects everything it hears, even encrypted data and when in drone mode (Like Google were using) pushes it all out to a listen server,
Gslite (The software written years ago as Gstumbler by a Google employee, re-purposed and renamed Gslite then used in StreetCar) is
meant to sift through all that incoming Kismet data, discard the useless bits like the encrypted data which would be jibberish, add the GPS location to the WiFi headers and write it to disk.
http://static.googleusercontent.com...pdfs/friedberg_sourcecode_analysis_060910.pdf
Above is the independent source code review of Gslite. It's a good read if you are technical. On page 8 you'll see a figure of how it was setup. Then the following code on 11.
Code:
DEFINE_bool(discard_encrypted_body, true, "Discard bodies of encrypted 802.11 frames");
DEFINE_bool(discard_control_frame, false, "Discard 802.11 control frames");
DEFINE_bool(discard_data_frame, false, "Discard all 802.11 data frames");
DEFINE_bool(discard_management_frame, false, "Discard all 802.11 management frames");
These are GSlite defaults. It discards packets identified as encrypted, does not discard anything else. However it is Google standard programming practice to control these options through scripts when the program launches, with the script option superseding the program default.
Now. Consider that the above code was not changed from when Gslite was Gstumbler
and that as above those options could be superseded from a launching script or program, which is Google's Standard Programming Practice. Don't change the code, manipulate it with outside scripts.
So what happened here is that for some reason Gslite launched with default options, writing everything but encrypted to disk.
One line of script could have stopped this from happening.
Now consider that Google segregated all the data, complied with deletion requests, created a new 'Privacy Advocate' job position, retrained staff and revised their code checking policy. All for one line of code, that might even exist it's just missing a semicolon or something and errors out.
It's a very, very costly mistake. But it's still a mistake. Perhaps they should have changed program defaults so it didn't happen, but Google point out that's not how they roll. Perhaps it should have been checked more thoroughly. Perhaps an engineer was running it that way to test it out and someone just stuck it into production. Perhaps the lead engineer hates his Job and deleted that bit of code. Who the hell knows.
The point is, Google never intended it to be that way. They have nothing to gain from that information but worldwide lawsuits and loss of money. There is no upside to having it and it's perfectly clear how it happened. That all points to accident in my book.