6 ms·

I can't answer your question, because I don't know the answer. However, I would recommend against relying on wereHamster's apparent mis-information... unless G

I can't answer your question, because I don't know the answer. However, I would recommend against relying on wereHamster's apparent mis-information... unless Google's policies are different in the jurisdiction that wereHamster is familiar with, in which case I apologize.

kuschku 10y ago
I think wereHamster’s text was satire, but the idea was repeated by many others: Anything related to your job you do is owned by Google. You can’t contribute to ejabberd when you work on Hangouts.
- wereHamster 10y ago
  What does it tell us if people don't recognise that as satire? Is it so close to reality to think that Google could claim rights on our cookie recipes? And if you really have to ask if such a clause applies to you, you haven't properly read your contract and/or you don't know your rights. People, please educate yourselves, don't let large corporations, even if they claim not to be evil, violate your rights.
  - kuschku 10y ago
    > And if you really have to ask if such a clause applies to you, you haven't properly read your contract and/or you don't know your rights. I’m not working at Google, but I’m a compsci student in Germany, and obviously interested in the situation in the job market. > What does it tell us if people don't recognise that as satire? Is it so close to reality to think that Google could claim rights on our cookie recipes? It’s certainly possible that some might expect that – from the standpoint of someone who only heard of German law, for example, a large part of US employment laws would sound just as crazy as being able to have the copyright of your employee’s cookie recipes.
- jsolson 10y ago
  > You can’t contribute to ejabberd when you work on Hangouts. As a Googler I suspect you could, you'd just need permission (possibly per patch). Googlers contribute to lots of open source projects. Google itself is fairly liberal in terms of what it's willing to share outside. Exceptions tend to be product specific code (you probably couldn't contribute the Hangouts UI and front-end code), particular technologies that are distinct competitive advantages (search ranking, etc.), or things that are Google specific (I work on Google Compute Engine -- there's a fair amount of code that is specific to Google's infrastructure).

kuschku 10y ago

I think wereHamster’s text was satire, but the idea was repeated by many others: Anything related to your job you do is owned by Google. You can’t contribute to ejabberd when you work on Hangouts.

wereHamster 10y ago
What does it tell us if people don't recognise that as satire? Is it so close to reality to think that Google could claim rights on our cookie recipes? And if you really have to ask if such a clause applies to you, you haven't properly read your contract and/or you don't know your rights. People, please educate yourselves, don't let large corporations, even if they claim not to be evil, violate your rights.
- kuschku 10y ago
  > And if you really have to ask if such a clause applies to you, you haven't properly read your contract and/or you don't know your rights. I’m not working at Google, but I’m a compsci student in Germany, and obviously interested in the situation in the job market. > What does it tell us if people don't recognise that as satire? Is it so close to reality to think that Google could claim rights on our cookie recipes? It’s certainly possible that some might expect that – from the standpoint of someone who only heard of German law, for example, a large part of US employment laws would sound just as crazy as being able to have the copyright of your employee’s cookie recipes.
jsolson 10y ago
> You can’t contribute to ejabberd when you work on Hangouts. As a Googler I suspect you could, you'd just need permission (possibly per patch). Googlers contribute to lots of open source projects. Google itself is fairly liberal in terms of what it's willing to share outside. Exceptions tend to be product specific code (you probably couldn't contribute the Hangouts UI and front-end code), particular technologies that are distinct competitive advantages (search ranking, etc.), or things that are Google specific (I work on Google Compute Engine -- there's a fair amount of code that is specific to Google's infrastructure).