You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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.
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.
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.
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.
It seems Google largely catered to employees that contribute to specific projects repeatedly, and not people like me who just send random one-off patches. I'm good at fixing problems in unknown code, I don't go work on a single codebase for long periods of time.
Just contributing behind the scenes (like many Googlers) was all well and good, until the subject came up in an internal mailing list and I made the mistake of mentioning a Pulseaudio commit as an example of the kind of thing too trivial to bother going through the Process.
This is the 9-line patch: https://github.com/pulseaudio/pulseaudio/commit/4e5051db7297d8171d148ef7d15c2e06ebeff0ce … This was something I debugged for a few hours, then fixed at 2AM. At home. I just wanted to send it and forget about it. No way I was going to spend more of my time getting a release for a 9-line patch to a GPL/LGPL codebase.
I guess they've realized this was a dumb policy, because under the current rules what I did was totally fine.
Unfortunately, at the time, instead, what I got was a flamewar with @cdibona where he accused me of putting both Google and Pulseaudio in jeopardy. For a 9-line bugfix.
This proceeded with a bit of back and forth where I mentioned my bad experience with IARC. DiBona was having none of it, so instead he opted to *ban me from the IARC & open sourcing processes*. I was told to "go through employment legal" for any further issues.
It was at this point that I pulled up my Google employee contract, and looked *very* carefully at the IP ownership clause. As it turns out, I had missed a little detail. It was *obviously* modeled after CA labor code (even though I was in Ireland), but there was a difference.
CA labor code says, in pseudolegalese: You own THING you do on your own time without company equipment IF NOT ( THING relates to the company's business OR THING results from work you did for the company )
Since Google's business is basically everything technology, you do not own anything in practice. E.g. I was told that since Android has an audio server too, that the Pulseaudio patch was in scope and owned by Google.
However, my contract was worded differently: You own THING you do on your own time without company equipment IF ( NOT THING relates to the company's business OR NOT THING results from work you did for the company )
It is evident Google would do better to hire computer science graduates for lawyers, because whoever wrote that clearly didn't understand boolean logic and De Morgan's laws. This is wrong: ¬(𝑃 ∨ 𝑄) ⇎ (¬𝑃) ∨ (¬𝑄) The correct equivalence is: ¬(𝑃 ∨ 𝑄) ⇔ (¬𝑃) ∧ (¬𝑄)
And so, *as long as* whatever I did in my spare time and without using Google resources did not result from work I did for Google, it didn't matter one bit whether it "related to Google's business", which is the loophole they use to own everything you do.
And so I resolved to give zero shits from that point on about their IP ownership policies, and did whatever I wanted in my spare time. If you work for Google (Ireland especially) you should check your employment contract carefully. You might be able to do the same.
I hope Google's employees are able to unionize and this is one of the changes they should demand. No company should be able to own things you do in your spare time, especially if they don't relate at all to your job description (regardless of whether they do to someone else's).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
