Google Doorman: Global Distributed Client Side Rate Limiting

Re:Google Doorman: Global Distributed Client Side Rate Limiting by yegle on Saturday April 09, 2016 @10:48AM (#11461454)

This is a project whose author is a Googler thus Google has the copyright and all the CLA stuff. However Google is not directly involved in the project, in the sense of having employees solely work on the project and have an OKR on this project, or roadmap whatsoever.

Think about this: someone work for Google wrote a software and Google is kind enough to open source it.

Disclaimer: I work for Google but my interpretation could be wrong.

[ Parent | on HN ]

Re:Google Doorman: Global Distributed Client Side Rate Limiting by brunoqc on Saturday April 09, 2016 @03:51PM (#11462974)

Does Google also own code that you write in your spare time at home?

[ Parent | on HN ]

Re:Google Doorman: Global Distributed Client Side Rate Limiting by batbomb on Saturday April 09, 2016 @04:24PM (#11463129)

Usually (close to) universal answer is something like is: "If you've used any employing entity resources, even incidentally, your employing entity owns it, especially if the project is directly related to the business"

Some places will attempt to assert more ownership and some will not.

[ Parent | on HN ]

Re:Google Doorman: Global Distributed Client Side Rate Limiting by rixed on Sunday April 10, 2016 @12:32AM (#11464907)

They pretend to, as would many companies if asked. I don't know how that would hold in court though. They also, for instance, pretend it's illegal to discuss your salary while the opposite seams to be true, so...

[ Parent | on HN ]