Like many Googlers, I had projects I worked on in my spare time. Some of those I carried over from before joining. I also upstream random open source contributions. Google, like most tech companies, tries to appropriate any and all rights to everything you do in your spare time.
-
Show this thread
-
This is, of course, completely ridiculous, but has become standard practice. Google's policy is based on CA Labor Code § 2870, which gives them ownership over anything that "relates to Google's business". SInce Google does everything, they get to claim everything.
4 replies 48 retweets 275 likesShow this thread -
Since understandably a lot of people aren't happy having to slap a "copyright Google" on everything and anything they do after joining the company, Google has an IARC process that lets you reclaim your own rights (that this is necessary is ridiculous).https://opensource.google/docs/iarc/
5 replies 23 retweets 203 likesShow this thread -
When I joined, I submitted two projects that I was actively working on at the time, largely just maintaining: AsbestOS (yes, those were the PS3 Linux days) and usbmuxd (iPhone USB comms daemon, you probably have it if you have Ubuntu!).
1 reply 8 retweets 157 likesShow this thread -
A long wait later, AsbestOS was approved with a "we don't want to have anything to do with this project" disclaimer. usbmuxd was rejected without an explanation. My follow-up email asking for clarification was ignored. I ended up having to hand over maintainership of usbmuxd.
2 replies 15 retweets 170 likesShow this thread -
At that point I concluded that the IARC process was broken. It seemed there was no real recourse if you get rejected, and no explanation. So I just resolved to quietly work on whatever I want, which seems to be what most Googlers do anyway.
1 reply 11 retweets 203 likesShow this thread -
Although Google may *legally* be able to claim practically anything you do under some "we have a related product" technicality, in *practice* their lawyers aren't going to go after you for pet projects or random commits. It's not safe, but it's *probably* okay.
1 reply 13 retweets 160 likesShow this thread -
Google also has a process for OSS patching (https://opensource.google/docs/patching/ ), which I never tried after the IARC experience. This workflow has changed a *lot*; it was nowhere near as permissive during my time there as it is now. It was way too much friction for random one-off commits.
3 replies 7 retweets 115 likesShow this thread -
Replying to @marcan42
This is a disaster the other way too - I wanted to contribute a one line fix to Tensorflow and in order to have it accepted Google wanted me to: Register a Google account Tie my Github account to that account in some way Sign over copyright to them through web form So I didn’t.
1 reply 0 retweets 1 like -
Replying to @owainkenway @marcan42
I genuinely didn’t care about the copyright part, it was the process that was too annoying to bother with.
1 reply 0 retweets 0 likes
*After* I left Google I debugged a Golang bug that had been open for months. It took me 2 afternoons to find and fix the bug. It took a month to get through the CLA and code review process. Even they thought that was too slow :-)pic.twitter.com/rnoC9La4NG
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.