Linked by Thom Holwerda on Fri 21st Oct 2011 23:17 UTC, submitted by jello
Thread beginning with comment 494398
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-06-09
Well, the Mach 2.0/2.5/3.0 code under licence, written *AT* Carnegie Mellon (aka using its resources, human and technical) is own by CMU. As such, the people who worked on it don't own any copyright on it.
As so, claiming that one individual can get the credit for the whole is clearly misleading.
And?
You said Apple deserve the credit for Mach kernel. Now you're saying that Avie deserve it (while is only one of the student working on it then), trying to link that hiring a student make you the new owner of what he could have wrote before, himself doing under the umbrella of another organisation!
By this definition, my own employer should be credited for all the code I wrote on my own up to my contract start date.
Or for a better analogy, it's like claiming current Linus Towarld's employer deserves credit for Linux kernel.
That's plenty silly.
Indeed:
http://www.cs.cmu.edu/afs/cs/project/mach/public/www/people-former....