Comment by catillac
5 years ago
> There is no reason to change his position on the subject of ex-employees making clones of the product.
Obviously I completely agree with this in a vacuum, but you seem to imply that that is what happened in this case. It was pretty clear from all the emails posted, assuming they were materially unaltered, that this isn’t what happened here. So your comment seems like a bit of a non sequitur, unless you’re saying that is what happened here?
I don’t see any reason why an ex-employee should expect a happy outcome when they create an open source “clone” of their employer’s product. Personally I have been in this situation as an ex-employee, where I was generally interested in the product field, and I avoided doing that to avoid any appearance of impropriety, and also to some degree, the copyright purity of the project would have been questionable and litigable.
A lot of people are very unclueful about this, especially young people, and maybe Mr. Masad could have had a gentler touch. But for the blogger to have cloned the product or part of it without (pinky swear!) actually taking any IP from the employer, that might in fact be legally true, but it’s a walk across a tightrope.
That you think “copyright purity” is the issue to litigate points out that you’re not very clueful either, I’m afraid. If I quit Google and write a clone search engine using none of their code but all of their technical architecture, in no way does that interact with Google’s copyrights. At all. You can’t copyright an indexing strategy nor a software architecture. You can, however, copyright a Visio diagram of the architecture. That’s a different thing.
This also applies to your nod toward “a novel fair use argument” in a sibling comment. Fair use has absolutely nothing to do with this or any hypothetical like it. You may as well have cited bird law.
Copyright isn’t the blanket IP concept people think would cover most disputes. These types of cases get into trade dress, patent law, and other legal concepts. The fundamental limits of copyright are why software techniques are patented in the first place and one reason among many why you sign assignment when you join a company.
IANAL and my comment is U.S. biased. At least in the U.S., the fixed and tangible aspects of copyright are bite-sized enough to understand without a J.D. Given how murky this entire field is when it comes to IP, it’s extremely important to understand these concepts for even a line engineer, as well.
Clean room design is a whole thing that people do, because of copyright. Maybe they don’t need to do that. If you want to quit the search team at Google and make your own search company, I’m not against that, but you should expect scrutiny like the kind Levandowski had.
9 replies →
Regarding this part of your comment:
> Fair use has absolutely nothing to do with this or any hypothetical like it.
Yes, it does. The commercial effect of the usage is a factor in determining fair use, and that might distinguish a “show and tell” project from a “production-ready” OSS project.
4 replies →
I appreciate your diplomacy, but from my POV, GP is definitely trying to suggest the intern's actions were equivalent to founding a competing company, and is interested in defending REPL.it's CEO.
It doesn’t matter whether it’s a competing company or open source when it comes to the question of whether IP got stolen, unless you want to make a novel fair use argument.
What IP was stolen? The idea of running code from a web editor? The _button placement_?
There’s nothing here that says he’s stolen code or any IP. The CEO doesn’t even claim that he’s stolen real IP. Everything that’s similar is public knowledge and the burden of proof is to point out what’s been stolen.
Which the CEO could! Because the work was open sourced. So he could reply and say, “hey, you implemented this part in a way that is in code you worked on. It’s also a pretty atypical solution to this problem, so it seems reasonable that you took that from us.”
He doesn’t.
Instead, he gets insecure that a kid implemented a similar product in a couple days and decides to rail on him, then offer a half-apology well after it has blown up.