Microsoft will make a surprise announcement at the Nov. 1 launch of Windows CE 6.0, according to the Web's rumor-mill. In what would be its most substantial nod to the open-source movement, Microsoft is rumored to be opening up CE 6.0's entire kernel as 'shared source'. Update: It's official.
To read all comments associated with this story, please click here.
Member since:2005-08-26
Member since:2005-07-26
MS's shared source program is a look but dont touch and you have to jump through a lot of hurdles to see the code, sign agreements, etc. In the end, you can see the source, but you can't build your own kernel or submit modifications back to MS. It's 99% hype.
Microsoft has several "Shared Source" license types[1]:
Microsoft Permissive License (Ms-PL)
The Ms-PL is the least restrictive of the Microsoft source code licenses. It allows you to view, modify, and redistribute the source code for either commercial or non-commercial purposes. Under the Ms-PL, you may change the source code and share it with others. You may also charge a licensing fee for your modified work if you wish. This license is most commonly used for developer tools, applications, and components.
Microsoft Community License (Ms-CL)
The Ms-CL is a license that is best used for collaborative development projects. This type of license is commonly referred to as a reciprocal source code license and carries specific requirements if you choose to combine Ms-CL code with your own code. The Ms-CL allows for both non-commercial and commercial modification and redistribution of licensed software and carries a per-file reciprocal term.
Microsoft Reference License (Ms-RL)
The Ms-RL is a reference-only license that allows licensees to view source code in order to gain a deeper understanding of the inner workings of a Microsoft technology. It does not allow for modification or redistribution. This license is used primarily for technologies such as development libraries.
I think you are thinking only of the last one.
[1] http://www.windowsfordevices.com/articles/AT3157033949.html
Member since:2005-10-02
Member since:2005-08-11
Member since:
2005-07-06
MS's shared source program is a look but dont touch and you have to jump through a lot of hurdles to see the code, sign agreements, etc. In the end, you can see the source, but you can't build your own kernel or submit modifications back to MS. It's 99% hype.
And in the embedded space, seeing the kernel source isn't a big deal. If you pay money and demonstrate a need, QSSL will let you see the source to QNX's kernel.