Is this true?
Is this true?
The obvious course of action is for developers to universally stop signing over their rights willingly like this. Nobody should ever have to sign these invention clauses to be employed.
If you're not working on something similar to what the employer is working on, it's not a problem. If you're working on something that will compete with what your employer is doing, there's a problem.
If you were running a sports team, you wouldn't let your employees run a betting parlor - they'd have too much incentive to throw a game and profit off it. In the same way, employers don't want their employees having situations where the company's goals and the employee's goals are at odds.
If you're not working on something similar to what the
employer is working on, it's not a problem.
Depends on the contract you sign. A lot of employers demand their employees automatically sign over all invention rights (past and future), and then have a process to (maybe) give your rights back -- and it sounds like this is how Google approaches it.The success of getting IP rights assigned to you personally is heavily dependent upon what you're doing. If it's just a Chrome extension for your favorite website or a webapp that caters to a niche interest you have, no problem. If it's a casual game (now that Google+ has launched) or a mobile app, it can be very, very difficult, as those are industries of pretty heavy strategic importance to Google.
It is true that Google has a very easy process to open-source your projects. One practical pain is that if you want to accept patches you have to get every contributor to sign Google's CLA.
Also, it's not a simple open-and-shut "yep, we own it" response. It takes ages, while you lose whatever enthusiasm you might have had going in to the idea.
edit: added "in my experience".