Untitled

Unless part of your access to the source involves signing some NDA, I would say you have nothing to worry about.

[Edited by - bakery2k1 on November 19, 2008 9:16:57 PM]

Quote:

Original post by bakery2k1 I don't imagine I personally will have to sign an NDA, but the company almost certainly has done so. I'll also probably have to agree to a click-through of some kind. I'm less worried about MS chasing me down for releasing the source however - I'm not about to do that. I'm worried that I won't be able to contribute to other software (either as a hobby or even at a future employer) because they'll think MS may see similarities between their software and Windows, realise they have someone who's seen the Windows source on the team, and then they'll be in trouble.

First of all, they won't ever know, and secondly, if you've looked at or even worked on some code for a company, there's nothing to prevent you from working in the same field elsewhere. Are circuit designers hired away by AMD from Intel not allowed to design circuits anymore? Of course not.

Microsoft would have to prove that you knowingly used their code (or ideas directly derived from it) in a project in order to cause you any harm.

If you are worried, talk to a lawyer.

MSN

Quote:

Original post by msn12b If you are worried, talk to a lawyer.

Seconded. Also read the licence very carefully and for heaven's sake do not copy their code or base derivative work on it (for the exact meaning of the latter better talk to an expert).

IANAL and I'm no Linux kernel developer, but I suspect that the kernel people would be averse to accepting contributions from someone who has had access to Windows source code—too much risk of accidental taint, certainly too much opportunity for Microsoft to make the accusation.

I'd suggest locating a kernel development FAQ, asking someone with real, relevant knowledge, or even sending off an email to the Linux kernel list to get a solid answer.