So, answering the question opened in another thread, if FreeDOS developers read the code, they risk making Microsoft the owner of their future contributions.
> You may not use or distribute this Software or any derivative works in any form for commercial purposes.
Examples of commercial purposes would be running business operations, licensing, leasing, or selling the Software,
distributing the Software for use with commercial products, using the Software in the creation
or use of commercial products or any other activity which purpose is to procure a commercial gain to you or others.
If you're in academia and getting a stipend and you look at it as part of your research, Microsoft could argue that that is a commercial gain to you. If FreeDOS has ever been used to make a commercial product (this is very different from the GPL which explicitly delineates derivative works from works produced by the software!), then its developers risk breaking the terms of the license agreement if they taint their thought processes with Microsoft's code. So yes, I'd probably say you're right.
> So, answering the question opened in another thread, if FreeDOS developers read the code, they risk making Microsoft the owner of their future contributions.
This is a really serious issue, because we can be reasonably certain that Microsoft wants to release a new version of DOS in the reasonably near future and so this is a sinister plot to get a nonexclusive license to FreeDOS so they can charge licensing fees. Quite ingenious.....
I would think Microsoft takes the FAT module of the Linux kernel very seriously. The way to store long file names as multiple directory entries is one of the patents Microsoft uses as its main mobile revenue driver (they get more money out of Android licenses than they get from Windows Phone sales).
