6 ms·
Don't you think that this system is at least a little bit unfair? Why does Google automatically get claim on work that has no relation to Google, done without c
by cookiecaper 16y ago
Don't you think that this system is at least a little bit unfair? Why does Google automatically get claim on work that has no relation to Google, done without compensation from Google, and without any of Google's equipment or facilities? How come these people need Google permission to assert a claim on their own intellectual property that is entirely distinct from anything involving Google? It sounds like this was established simply so that Google can claim things that they have no real right to claim and misappropriate an employee's work as convenient.
How come you can't just say "All work on Google-owned software is copyright Google. All work directly assigned by Google management is copyright Google. All work performed wholly independently and separate from Google by Google employees is copyright its respective owners."? I don't get it.
- cdibona 16y agoThis is actually a big can of worms, what with it having so much to do with state, federal and international law and treaty (wipo, amongst others). It is often unfair. All I can act on from this fairness perspective is Google's interactions with Open Source, making it as easy as possible to release code under open source licenses, which I think we're doing a good job of.
- deleted 16y ago[deleted]
- cookiecaper 16y agoRight, as you stated in your first post, it's easy to open-source something as long as you let Google have the copyright. Well, that's not always a good option. We have a prominent example in the Sun/Oracle thing right now. A copyright owner can transfer or disavow its copyright. Even if state, federal, and international law allows you to steal your employees' work, you shouldn't do it. If something that should belong to employees belongs to Google due to an incongruency or other bad thing in the law and this becomes an issue in a court, Google can simply say, "We had nothing to do with this, we didn't pay for it, our facilities were not used in its creation, and therefore we transfer our copyright to employee X, who is the primary author." I can see how obtaining a pre-emptive declaration and/or copyright assignment can be beneficial, but I definitely don't think there's any need to act like it's a requirement and that an employee needs Google's permission to live as a free person and do things he wants that are entirely separate from Google, its facilities, and its businesses.
- bugsy 16y ago"what with it having so much to do with state, federal and international law and treaty" Would love to see specific citations showing that Google has no choice but to claim ownership of all its employee's projects during their own free time at home or elsewhere not at work. I thought slavery was banned in most countries, it's amazing to now hear that it is required under international treaty. Greatly looking forward to those specific citations of how specifically Google has no choice in this because of "state, federal and international law and treaty".
- deleted 16y ago[deleted]
- bugsy 16y agoHe's gone beyond saying it is a voluntary contract. He said the contract terms being discussed are required under state, federal and international law. Thanks for the downvote!
- lionhearted 16y agoFor the ridiculous slavery analogy. You've got a top Google legal person here explaining his thought process clearly and in honest, not-just-PC terms, and you're waving your arms around. I don't necessarily disagree with your points, but it's bad for discussion. Anyway, I deleted my comment since I didn't want to get into an argument here, it's not that important to me. I don't even 100% disagree with you, but clean up the tone a little bit and less handwaving? That kind of thing is what makes people want to brush off criticism instead of responding, which is really bad for discussion. I think it's really cool that a person on the Google legal team is explaining their thinking here reasonably and clearly.
- cookiecaper 16y agoI don't think cdibona is a lawyer or on Google Legal. Last I knew he was "director of open-source operations" or something like that. He is a developer I think. I also think he had some involvement with SourceForge back in the day but am not sure.
- state_machine 16y agoBecause it's probably not actually "wholly independent". Software developers are thought workers, and you don't get to just check your brain at the door when you clock out like you could your tools or a laptop. Thus, any similar* work you do on your own time cannot be done without your brain using some of what is in your head, which you learned/figured out on company time. * Now, this is the fun part. Where do you draw the similar line? Think about it: you hire someone to solve a problem. You pay them to figure it out and implement. Then they turn around and implement the same solution, which you paid them to think about, for someone else?
- andreyf 16y agoThink about it: you hire someone to solve a problem. You pay them to figure it out and implement. Then they turn around and implement the same solution, which you paid them to think about, for someone else? That's perfectly fine, and happening all the time. Google got the fastest JS interpreter among all the major browsers (Chrome's V8) by hiring the guy Sun paid a lot of money to do nothing but think about virtual machines for a couple of years. Just because Sun paid for the development of HotSpot doesn't give them any kind of ownership over the ideas, with one exception: for some ideas, they can get government enforced limited time monopolies for the sake of "promoting the Progress of Science and useful Arts" by filing patents for them. But how this applies to Google employees, I don't know: it would seem that Google ought not to be able to claim ownership of all of my ideas simply because I work there while having them. That said, I really can't imagine it being much of a problem if someone just stays honest about things (i.e. not work on a major competitor to their own project).
- cookiecaper 16y ago>Thus, any similar work you do on your own time cannot be done without your brain using some of what is in your head, which you learned/figured out on company time. Should I be writing all my past employers checks because I am using things I learned "on their time"? I had a job where we used CakePHP, and I learned much about the framework during this job; now, should all my future CakePHP work (of which there is hopefully very little) belong to the employer that first facilitated my learning of CakePHP? Should I write a past employer a check when the bad management practices I observed there are avoided due to my past experience? Do they own my wisdom on that subject now? I think you can see where we're going with this. I think that anything that is not performed in the course of your ordinary job duties, not directly related to the company or its primary businesses, and performed outside of company time and facilities blatantly belongs to its original author. >Think about it: you hire someone to solve a problem. You pay them to figure it out and implement. Then they turn around and implement the same solution, which you paid them to think about, for someone else? Uh, yeah, this happens all the time. That's what most consulting firms do. You think when you hire a web firm to build your e-commerce site they always start from scratch on the shopping cart program? The cart was written the first time they had an e-commerce job, and now they reuse it. This is good practice and totally kosher, and should be expected, unless you explicitly request a custom shopping cart program with copyright assignment.
- earl 16y agoFirst of all, as far as I am aware, Google has been a very friendly contributor to open source, releasing lots and lots of high quality code, including some really cool stuff that isn't available elsewhere such as GWT or Guice. I'm strongly inclined to give them the benefit of the doubt. Further, reread Chris' first sentence. This isn't just Google being jerks; their policy stems at least in part from CA law. So, under California law, which is probably the most liberal in the United States coving IP, you are prescribed from competing with your employer even on your own time or on your own equipment. This is reinforced in industry employment agreements, including Google's (my employer) Most employers take the position that everything you do in the space is logically competitive. Recognizing that, we, Google, make it very easy to get permission to open source things, but under Google copyright. That said, given their relationship with the web, it's hard to say that any web related tech doesn't compete with them in some fashion. I'd wait for G to actually be dicks before calling them out. Also, being allowed to use 20 percent time to work on this stuff is pretty amazing. I have a bunch of personal projects that I'd love to have a day a week to work on.
- kelnos 16y agoThat said, given their relationship with the web, it's hard to say that any web related tech doesn't compete with them in some fashion. ... which is really the problem. Google can claim that anything web-related that an employee of theirs does on their own time to be sufficiently related to their business as to assert ownership. And that's not cool. Just because a company has done good things for the community, it doesn't give them a free pass to do bad things to its employees.
- ori_b 16y agoAs stated above "We have a process for releasing under your own copyright, but it is not as flexible.". I think that's entirely fair - if you're a Google employee contributing to a project that might potentially compete with Google, I don't see a problem with Google asking you to get permission.
- rdtsc 16y agoBut isn't Google a "Don't be evil" company? Such a moral stance should clearly prompt them to either stop taking code ownership from their engineers' weekend projects (I call it stealing), or they should start paying overtime for that code. EDIT: Corrected the corporate motto from "Do no evil" to "Don't be evil".
- HiroshiSan 16y agoThis was how it was put in the book How To Get Rich.
- nostrademons 16y agoVery little of the work done on Google products is directly assigned by Google management. I just finished up a week-long demo that fixes a longstanding annoyance with the search results. I saw a need, made a quick 10-minute screenshot mock-up, gave a 3-minute presentation, recruited a few co-conspirators, and we built it. Management will be involved in the decision whether to productionize and launch it, but the demo was all done at the individual-contributor level. I've got a 20% project that, to my knowledge, my manager doesn't even know about. It grew out of my 80% project - we needed a library that doesn't seem to exist yet. When it gets to a semi-functional state, I'll open-source it through cdibona's office, with copyright assigned to Google. Why not? It'll end up exactly the same for end-users, with an Apache license, and it's much less of a bureaucratic hassle to just do it with a Google copyright.
- anthonyb 16y agoNone of that is related to cookiecaper's point though. Your project is obviously related to Google, used Google's resources and engineers, and was in response to a problem that Google had. The point is that Google will claim copyright of everything that you do. If you write a game about chickens in your spare time, for example, then Google owns the copyright, despite not having had any input into it. I fail to see how that's fair or reasonable, and I'd be very interested to see what laws apply - I suspect that cdibona is trying to blow smoke up our collective asses.
- jrockway 16y agoIn your case it makes sense; you wrote the library at work. Google paid you to sit in Google's building using Google's computers and networks to write the library. If they want to own it, it's not unreasonable at all. What is unreasonable is that if you did it at home, with no Google resources, that they would still ask you to assign them ownership. (I, fortunately, don't have this problem. Part of the official open-sourcing process involves deleting any reference to our company, even in the copyright, so that nobody sues them if it breaks. Example internal app that was open-sourced: http://openefs.org/ http://openefs.org/)
- nostrademons 16y ago
- DenisM 16y agoYou're arguing with the wolf that it's a little bit unfair to eat the stray sheep. The wolf retorts that only 25% of the sheep were eaten, and the entire 75% were allowed to safely return to the flock. That, and the system generally benefits everyone - wolfs and sheep. Don't you realize the futility of your argument? The wolf will continue to eat the sheep because that is what wolfs do, and they will come up with any requisite PR to make it look decent. The only answer is to stop being meaty while within the reach of a wolf, and stop being within the reach before you're about to grow some meat.