3 ms·
It was actually significantly more ambiguous when I worked there (2009-2014), and presumably was even moreso in 2007. IARC didn't even exist until I think 2013
by nostrademons 10y ago
It was actually significantly more ambiguous when I worked there (2009-2014), and presumably was even moreso in 2007. IARC didn't even exist until I think 2013, and it wasn't an online form at the time I left - you emailed some contact person, they discussed it in a relatively opaque committee, and then got back to you after an inordinate length of time. They had the standard California IP contract at the time, i.e. company claims ownership over all IP except that done on your own time, using your own resources, on subjects unrelated to the company's lines of business.
That last clause was the source of all sorts of ambiguities, eg. Googlers who had written iPhone games were told (after the fact) that their work was owned by Google because Google+ might be getting into the games business. This was somewhat legally questionable on Google's part, and it was cases like this, probably combined with a few outright corporate theft cases like Lewandowski's, that led to the IARC process.
- jacquesm 10y ago> This was somewhat legally questionable on Google's part If it was as you describe it is at least despicable, whether it is legal or not is another matter but that's very very nasty.
- puzzle 10y agoWhen I was at Google, I kept hearing that California laws in particular are not employee-friendly and that you should ask for an opinion from a personal lawyer. As to why this hard stance, I always suspected that sweeping that kind of stuff under the rug would have opened the company to a bunch of annoying lawsuits from shareholders and/or ambulance chasers for something along the lines of "not enforcing the company's rights". All it would have taken was just one successful side project. Also note that, even if the stance was "Google owns it by default", lots of projects were assigned back (https://opensource.google.com/docs/iarc/ https://opensource.google.com/docs/iarc/). The IARC process leaves an electronic trail showing that a project was subject to at least some kind of due diligence (even if it later pockets the employee a lot of money that at some point Google or shareholders could have very hypothetically fought in court for). Or, conversely, the lack of an application might shift the legal burden onto the employee that didn't declare everything as required. Again, the above was just all speculation on my part.
- zaphar 10y agoThat's only ambiguous if you didn't contact IARC. I can't speak to before IARC was a thing. But after IARC you had a way to get an unambiguous answer as to how Google would view your side project. Whether by form or email that is still pretty easy.