Linked by Thom Holwerda on Tue 7th Nov 2006 22:56 UTC
Permalink for comment 180012
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2005-07-13
There is most decidedly no restriction on looking at the code & studying it.
For closed-source software companies, particularly one with as big a bullseye painted on them as Microsoft, there is a legitimate concern in that paid developers may inadvertently copy the code they are studying, tainting the product and opening them up to claims. OSS projects often employ a clean-room technique when reverse engineering or working on interoperability to eliminate possible claims of stolen or copied code. Even large linux developers like HP or IBM will seperate their OSS and proprietary developers, you can't mix and match without running the risk of code taint.
For Microsoft's sake it's safer and easier to let the OSS guys provide the information rather than try to dissect it themselves. That's about the only single part of this ridiculous agreement that makes sense.