3 ms·
It's probably a bit more true than that. You got the process right, but the problem is that Google is in so many lines of business that almost anything you do
by nostrademons 15y ago
It's probably a bit more true than that. You got the process right, but the problem is that Google is in so many lines of business that almost anything you do could be considered "along the lines of business of your employer".
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.
- pfedor 15y agoMy personal experience: I submitted two personal projects http://kartofel.jfedor.org/ http://kartofel.jfedor.org/ and https://market.android.com/details?id=org.jfedor.frozenbubble https://market.android.com/details?id=org.jfedor.frozenbubbl... last year (in July I believe) and both were rejected (i.e., the committee said that Google would not release copyright). However, recently (a month or two ago) I was told that the rules changed and now they were happy to release the copyright for both. In the meantime I tried to get my employment agreement altered to state that my personal projects belong to me, not to Google, but I found there was absolutely no room for negotiation there (despite the fact that my manager, an eng director, supported this). I was told by the legal department that the only person in the company who could approve such thing was Larry Page. 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.