3 ms·
> If the employer owns the rights, the copyright assignment is illegal and void - the employee never had the right to do it Is that actually true though? Supp
by skissane 5y ago
> If the employer owns the rights, the copyright assignment is illegal and void - the employee never had the right to do it
Is that actually true though?
Suppose Alice has a full-time job with HyperSuperMegaSoft. Alice writes a patch to IndependentSoftwareFoundation's FooBolCompiler. When Alice submits the patch to IndependentSoftwareFoundation, she warrants to IndependentSoftwareFoundation that she has the right to do so. Years later, HyperSuperMegaSoft decides to sue IndependentSoftwareFoundation for including Alice's patch in their FooBolCompiler, because they claim Alice never got proper internal approval (under HyperSuperMegaSoft's internal policies and procedures) to submit the patch. Is a court going to invalidate Alice's agreement with IndependentSoftwareFoundation because Alice didn't follow the right internal procedures with her employer? Or will the court decide that IndependentSoftwareFoundation shouldn't be punished for Alice's mistake, that HyperSuperMegaSoft is bound by Alice's actions as their employee even if they didn't approve of them, that IndependentSoftwareFoundation has the right to use the software under the agreement, and that HyperSuperMegaSoft can't successfully sue IndependentSoftwareFoundation (or FooBolCompiler's end-users)–they may still be able to successfully sue Alice for violating her employment contract (although that probably is far less an attractive proposition to HyperSuperMegaSoft than suing IndependentSoftwareFoundation is.)
IANAL so I don't know what the right answer is. (The right answer probably depends on the jurisdiction.) But I get the impression some people assume that HyperSuperMegaSoft would automatically win against IndependentSoftwareFoundation, possibly without having good justification for that assumption.
- viraptor 5y ago> invalidate Alice's agreement with IndependentSoftwareFoundation because Alice didn't follow the right internal procedures with her employer? Internal procedures are not the law. The contacts are. If the contract says her software belongs to the company, then it does. (Unless the country law says otherwise of course) In the same way I can't legally sell you a copy of Windows license that I totally promise I've got an agreement with MS about. It's not a license I have rights to.
- skissane 5y agoSuppose Alice has signed two contracts, one with her employer assigning them copyright in whatever she develops, and another with IndependentSoftwareFoundation assigning them copyright in something particular she develops. Why automatically assume the former contract legally trumps the later? Also, employees can act as agents for their employers. Suppose Alice falsely warrants to IndependentSoftwareFoundation that she has her employer's approval to submit the code in question. If an employee makes an unauthorised agreement with IndependentSoftwareFoundation, I don't think a court will necessarily automatically invalidate that agreement just because the employee wasn't properly authorised. It depends on the circumstances. It is like the case of the employee who buys an expensive dinner on the corporate credit card, and then the employer rejects the expense claim as violating policy. The employer can't refuse to pay the credit card company, or the restaurant, because the employee violated policy. The most the employer can do is fire the employee and sue them for damages. The employee entered into a contract with the restaurant on behalf of their employer, and the employer is bound by the contract even if the employee wasn't authorised to enter into it. > In the same way I can't legally sell you a copy of Windows license that I totally promise I've got an agreement with MS about. It's not a license I have rights to. Different situation in a couple of ways. Firstly, you didn't have anything to do with developing Windows. Suppose a Windows developer writes some code and puts it in Windows (under their Microsoft employee copyright assignment) then puts the same code in some open source project (under some other copyright assignment they sign without Microsoft's knowledge or consent). That's the scenario I'm talking about here which is rather different from the scenario you are talking about. Secondly, Microsoft Windows is famous and if some random person (with no apparent association with Microsoft) tries to sell you a license to it you have good reason to suspect the license is invalid. Some random piece of code a developer writes isn't famous and so someone who receives it doesn't have the same grounds for suspecting it. Courts tend to have more sympathy for people who make reasonable good faith assumptions than for people who assume things that a reasonable person should know are unlikely to be true. As I said, I'm not a lawyer and I'm not claiming any particular answer here is necessarily the right one. I think it likely depends on the jurisdiction and the specific details of each particular case. I just don't think it is as clearcut as some other people (including yourself) seem to think it is.