6 ms·
The policy was always crystal clear, but at the same time, tons of people found it confusing. "I wrote this at home on my personal computer in my free time? W
by dekhn 4mo ago
The policy was always crystal clear, but at the same time, tons of people found it confusing. "I wrote this at home on my personal computer in my free time? Why does google own it? how can that be legal" came up a lot. People would get into huge fights with OSPO over this.
- fg137 4mo ago> "I wrote this at home on my personal computer in my free time? Why does google own it? how can that be legal" Interesting. Did they read their contract before signing it?
- dekhn 4mo agoyes, many engineers (especially at google) are armchair lawyers and have all sorts of opinions about contracts and licenses.
- socalgal2 4mo agoWriting at home is irrelevant if what you're doing is related to the company's business. You can't be working for Google and making a browser, a document editor, a spreadsheet, a mapping site, etc... It doesn't matter if you do it on your own time. Yea, you can grow coffee and sell it at retail stores on your own time. No you can't complete directly with your employer. If it's some gray area then you either get permission first or wait for the courts if you get sued. This isn't unique to Google. It's basic common law. No contract needs to be signed. Competing with your employer is immoral. If you want to compete then quit and be a competitor. If you're taking their money as an employee then you have a "duty of loyalty"
- deleted 4mo ago[deleted]
- blitzar 4mo agoIts almost like the junior technofeudalists think the rules dont apply to them.
- userbinator 4mo agoKeeping a very strict "firewall" between your personal and corporate life is the best way to avoid such situations, but then again, these are Google employees we're talking about...
- dekhn 4mo agoI'm not 100% sure what your point is here, but the point I was making is that even in theory if you have a "firewall", your contract with Google (that you signed and agreed to) says that Google owns your code output even if it's done at home on your own time. It really comes down to (at least for Googlers in California) whether the work is related to Google's business (which often covers things like games, even if Google is not a game developer), and even then, you need to submit the work to the Googler lawyers and have them make the determination, before you get permission to publish the code on your own. I saw this play out repeatedly with OSPO and saw many people who believed they had set up firewalls to allow this, and I understood Google's position and appreciated that they made it fairly easy for most people to open source their code.