WiX Project Lead Interviewed On CPL Licensing
comforteagle writes "After Microsoft released WiX (Windows Installer XML) under the CPL I found it odd that so many interviews following were with almost everyone but the project lead. So, for your Friday enjoyment I've posted an interview with Rob Mensching, Wix Project lead, who sheds a little light on what's going on behind the scenes at the Shared Source Initiative from the ground." Mensching explains: "My bosses were not involved in the decision which license should be used for the Windows Installer XML toolset. I worked with members of the Shared Source Initiative team who understand the details of the various licenses available to share source code. They listened to my requirements and found that the CPL seemed most appropriate for the toolset."
Next time, ask around to see what a name means in other languages before you choose it for an international project... You don't want to name your project "WiX" in Germany.
Has Microsoft ever done ANYTHING that /. has approved of?
/. would find some nefarious plot behind that too.
I sure if MS released the source code to Windows 2003 under the GPL tomorrow
-Cecil
For anyone wondering, this is basically an XML wrapper for the MSI.
MSI files are binary databases that you had to edit with a nasty tool called oracle. The whole thing was counter intuitive. I could never understand why the MSI wasn't XML based from the start. It was written when MS was XML mad, after all.
This is brilliant. You can now work with a text source file format for the MSI.
Mensching: "I am not well versed in all of the licenses used by the Shared Source Initiative. As I described above, I went to the Shared Source Initiative team with the goals of my project and we agreed that the CPL was an appropriate license for the Windows Installer XML toolset."
Other types of shared source license programs at Microsoft, and further links in the Shared Source Initiative.
MSI installation on windows is a huge step up from the old setup.exe situation, but it isn't that often used.
What I'd really love to see on windows is something where windows tracked the 'lineage' of every file (and reg key) on the system. So, when you want to get rid of a program, you're able to remove everything the program touched, save files you've copied over to another location.
It's easy to get software installed on windows, now they need to work on a method to get everything removed, especialy spyware...
autopr0n is like, down and stuff.
This is being handled by M$ in a most interesting way; most likely all be design. This is not (IMHO) a project that escaped from Redmond, they have a plan in mind. The question is - is this a "hip fake" to the OSS community to fool everyone while they finalize their master plan of world domination of all computers everywhere, or is it an example of M$ recognizing the value of OSS and using it when it makes sense?
but Orca
I know most /.'s will find this hard to believe but M$ has always provided a huge amount of source code in an open source fashion. Just visit MSDN and you'll see of examples of free sample code. Then go to the code center where you can find tons of free demonstration applications that you can use to build your own app. For example the company I work for has used User Interface Process Application Block for .NET and Exception Management Application Block for .NET from their patterns and practices site to form the basis of an Enterprise scale business application. Of course the code is generally sample applications for Business purposes. But code like this has been available from M$ since before the internet boom.
So you needed a license model that does NOT allow sharing between REAL open licenses but looks open enough.
The Open Source Initiative thinks the CPL is "open". It allows derivitive works, grants no-royalty patent licenses to recipients (although only specifically for the program they receive), and allows source redistribution. It doesn't require source redistribution, but then neither do several other "open" licenses.
So what's the problem?