3 ms·
This bit seems wrong (about private open source projects): > Technically, Google owns everything you write while you work there, even if it's on your own time
by ajross 14y ago
This bit seems wrong (about private open source projects):
> Technically, Google owns everything you write while you work there, even if it's on your own time and with your own equipment.
Google is a California employer, and that's directly counter to California law as I understand it. The only exceptions made are for product areas directly related to your work (not just the employer's business interests). Am I wrong about this?
- wpietri 14y agoI'm pretty sure you're correct. This is the relevant CA law: http://www.leginfo.ca.gov/cgi-bin/displaycode?section=lab&group=02001-03000&file=2870-2872 http://www.leginfo.ca.gov/cgi-bin/displaycode?section=lab... However, these things can have subtleties introduced by the courts, so anybody reading this should talk with a good lawyer before betting a lot on this point.
- d503 14y agoIt looks like that's true, "except for those inventions that ... Relate at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer." With a company like Google it would seem that quite a lot of things might fall into that category.
- ajross 14y agoTrue enough. But that's still a far cry from "all your codes are belong to us, get in line for the committee". I suspect this is an instance of policy getting ahead of legality. It makes sense for Google to want to review employee open source work (and they could even do things like fire people who don't honor the process). But if it was represented to him that he needed approval to legally release code, then I think someone lied to him.
- DannyBee 14y agoNobody represented that to him. Let me quote what I wrote in the thread we had on hackernews on this exact subject of spencer leaving yesterday (with the same title, no less :P), then let me explain something additional First, a quote "First, this is not the normal open sourcing process. He says "This uncertainty bothered me a lot, since I wasn't sure whether my project could be legally released as open source.". The normal open sourcing process takes about 3-7 days. If he really wanted certainty about releasing it as open source, he could have gone through that process and been done with it. The process he is talking about is the process of Google granting ownership of various IP rights that google would normally own, to the employee. For various reasons (ethics, patents, copyright, etc) this is more complicated, and takes longer. Google is one of the few large companies that even lets you do this, AFAIK. The humorous part of all this is that the page describing the process, states quite clearly it will take about 2 months to make a decision. So it's not like the 2 month wait was unexpected, either, and phrasing it like he does implies that there was some amount of uncertainty in the time period where he was being strung along, which is simply not the case." In addition to the above, let me add that at least in the case that took two months, Spencer wasn't asking the committee about open sourcing. He asked "If possible, I would like to own all IP (though Google can use it too, just not patent it) and possibly not release the results of this research to the open source community." This is the one that took 2 months to decide about. He had said "this is probably not related to what Google is doing", and I explicitly warned him the day he applied that what he wanted to get a release for was in an area google did care about, and was doing research in.
- jmillikin 14y ago> The humorous part of all this is that the page describing > the process, states quite clearly it will take about 2 > months to make a decision. I'm not on the corporate network right now, but if I remember correctly, the page actually says that the wait will be up a month and usually shorter. Two months would definitely be unexpected. Also, there seems to be something mildly broken somewhere in the process. After I submitted my project, I waited a month with no word before contacting cdibona privately -- he told me that my project had already been approved. A month after that, I received an approval email. So even if the process is fast from your perspective, it may seem very slow from the perspective of the applicant.
- haberman 14y agoGoogler here (though not a lawyer and I don't speak for the company). I agree that the OP's assessment that you quoted is incorrect in general, for the reasons you mentioned. The Google-internal process that OP is alluding to allows an employee to seek positive assurance from Google that the company will not attempt to claim ownership over the project. It's a way to get agreement up-front that both parties agree the project is unrelated to the business. You don't give up any rights by not going through the process, but you might discover later that Google believes the work is related to the business, and believes that it owns the IP. However, there is another completely separate process that allows you to open-source your code while having Google retain copyright. It's much easier to get through (turnaround is just a few days) and lets you release the code under a permissive license like BSD or Apache2. I write a lot of open-source code on the side, and I've used this process to get approval for all of it. It makes no difference to me whether Google technically owns the copyright. I would add that Google's open-source policies are a huge plus in my book. It's a night-and-day difference from Amazon where I used to work. Trying to get anything released as open-source at Amazon was like pulling teeth.
- cdibona 14y agoThanks for putting this up here :-) (I handle both processes) The copyright process usually takes around 6 weeks, but new open source projects can be released in days (and patches much faster)
- brlewis 14y agoThe open source thing I can understand. The part for non-open-source projects is hard for me as an outsider. I can't see how any employee can have a web-oriented side project that doesn't compete with some Google service. You have a social network, a blogging platform, photo sharing, video sharing, online music, PAAS, code hosting, etc., etc. What area are you not in?
- fpgeek 14y agoTo this outsider, your question sounds like exactly the reason Google needs this sort of process. Even if an employee were working in an area that was theoretically competitive with something, an official determination by Google should trump theoretical arguments - providing valuable certainty to both sides.
- DannyBee 14y agoAs a lawyer (IP, not employment), i can affirmatively state you are wrong about this, for reasons various folks mentioned below (the actual phrasing deals with relating to your company's business, not directly related to your work). Additionally, court interpretations of this statute are not as favorable as engineers like to believe (IMHO). Living in !California, from what I see, California is only theoretically different from most states. In practice, for technology companies, the law basically means your employer owns stuff on your free time, in the general case. (IE If you were working for a startup that does online home rentals, and you were making a video game, you may have an argument)
- ajross 14y agoSurely those court interpretations are situations where employees left to pursue products though, right? Is there really case law where a company sued to recover ownership of a free software project? That just seems lose-lose all around. Bad PR, bad karma, no deep pockets to sue, no damages to recover. Personally, I find this kind of bureaucratic nonsense infuriating. And I guess I thought Google was better about it, but it doesn't seem to be. My past employers have, for the most part, simply shrugged when told about open source work I've done. Honestly I have to think that if I really ran afoul of a rule like this I'd just call your bluff and see if you'd fire me over it (because as I mentioned, we both know you won't sue).
- DannyBee 14y agoThere is plenty of caselaw I can find where, for example, employees have not left, but refused to sign over patents on stuff done in spare time, and companies sued to recover them while the employee was still working there. I have yet to find one where the company lost. For open source work, if you go through the process, it's short and we're happy to approve it (patches take about 30 minutes, projects, 3-7 days). In the IP release process, it's longer. That is better than every company i have worked at. You seem to think it's not very important, and just nonsense in general. Knowing who the legal copyright owners of the source code in your open source project are is quite important (in the cases you posit where everyone is just saying "whatever", the owner is unclear) If you don't think so, I can tell you in the one important case in the US where an open source project had to defend itself, Jacobsen v. Katzer, that Victoria Hall (the lawyer) spent a very large amount of her time trying to get all this sorted after the fact, and it is only by luck that the 50+ contributors she had to wrangle were still around and accessible. This is probably 300k in legal fees that could have been saved by having done the right thing up front at a cost of about 30 minutes. Note that these legal fees were paid by the poor guy who was running the open source project, not by his contributors. If you want me to be blunt, no offense, I've met folks like you, who think all this is a waste of time, and you are generally not worth the eventual expense in legal fees to the open source projects you contribute to (IE when the open source project needs to actually defend its rights, or the company behind the OSS project gets sued). Shrugging and saying "whatever" also has a funny way of turning into "that was really mine and guess what, we want damages" when the company you worked for gets bought. It's great to want the world to be different. I support all efforts to make life better for engineers around owning stuff in their spare time. I also spend a lot of my life trying to help open source in general. But to be blunt some more: The world we live in right now is not a happy pretty place. The reality is if folks like me, and the companies we work for, tell you than when you release a new open source project we probably own, that you should spend 5 minutes filling out a 4 field form and waiting a day for some folks to click approve before you fly and be free, it's not because we are power tripping bureaucrats. It's because we're trying to save millions in legal fees when it matters, and make sure the open source project you want to release is not going to be in a bad place, at a cost of 5 minutes of time and a small amount of waiting. So my advice is if you think you really want to "call someone's bluff", I would instead think hard about whether you are really expert enough in this stuff to be able to say it's all nonsense, and stop to think about whether the people who are perpetuating "nonsense" may actually have your best interests at heart. That is, trying to save you from yourself. If you really think it's a great idea to have an awesome open source project used by 1 million people, when it's not clear who actually owns the code, then all i can say is that i pity those people.