| |||||||||||||
|
| |||||||||||||
How can McVoy enforce this kind of crap?How can McVoy enforce this kind of crap?Posted Oct 3, 2005 17:31 UTC (Mon) by dskoll (subscriber, #1630)In reply to: How can McVoy enforce this kind of crap? by southey Parent article: Mercurial loses a developer
Easy because is it probably part of the license agreement signed by Corporation Y and, thus, by all current employees of Corporation Y. Employees are parties to the agreement because the terms of their employment would have something about upholding the Corportations values, interests etc. that makes any employee party to anything the Corporation does. I doubt that. Employees are not parties to agreements made by their employer with suppliers. They may be bound by certain rules if they are spelled out in the agreement (eg, most Non-Disclosure agreements compel corporations to enforce certain employee behaviours), but this sounds way too broad.
(Log in to post comments)
How can McVoy enforce this kind of crap? Posted Oct 4, 2005 4:29 UTC (Tue) by aotheoverlord (guest, #3993) [Link] Actually, most employees sign an agreement with their employer that signs over all code written by said employee to the employer(*). It's the reason that many GNU projects require copyright assignments signed by a contributor's employer before they will accept code from that person.
Assuming such an agreement exists between this employee and his employer, then it would stand to reason that code contributed to Mercurial is actual "owned" by the employer which is therefore in violation of the BitKeeper license the company has with Larry.
(*) While I doubt this has been tested in the courts, this usually extends beyond code written by the employee expressly for the employer, and includes all code written, including that written in the persons spare time. Be careful what you sign the next time you take a new job!
|
|
||||||||||||