A Perspective on Microsoft's Shared Source
Masa writes "ONLamp has an insightful article by Stephen R. Walli about Microsoft Shared Source Initiative and some thoughts, what it would really mean if Microsoft would open-source their operating system.
The article gives a nice perspective on the Shared Source Initiative and what it is meant to be. It also shows that even if it might look that Microsoft doesn't understand the value of open source, there actually are some projects under the OSI-approved licenses, for example the WiX Toolset, which is a good example of a successful open source project by Microsoft."
Perspectives on the Shared Source Initiative
by Stephen R. Walli
03/24/2005
Nat Torkington and I were discussing Microsoft's Shared Source Initiative not long ago. I left Microsoft in early December and had spent the last three years directly involved in various aspects of Shared Source work. The more we discussed his questions, the more we realized others probably shared the same questions. This article came from that realization.
Microsoft began pushing the idea of "shared source" a few years ago as a way to talk about source code sharing exercises they continue to develop in the face of open source software practices. The idea holds the premise that they will share the source code of their software appropriately with appropriate audiences. Free and open source software was happening all around them. They were certainly thinking about the phenomena all the way back to the original Halloween document in October 1998. After talking to many of their customers, they discovered that many Windows developers did want access to read code and debug against it, but not necessarily modify the code. There was even an early university program for academic access, but this early program was not particularly popular. By Spring 2001, Microsoft needed to have an active position on the open source phenomena, and thus launched the Shared Source Initiative.
I will not discuss the past executive miscommunication and misconception, or the marketing rhetoric, but will look at what Shared Source is and some of the challenges open source presents to a large publicly traded company.
First, recognize that Shared Source isn't one program with one license. Shared Source is an umbrella program for all source sharing programs from Microsoft. Any time Microsoft makes source code available through a program, it brands it as part of the Shared Source Initiative, the marketing machine has the message to deliver, and a new program ends up on the Microsoft Shared Source website. These licenses span the spectrum from very locked down, look-but-don't-touch licenses to licenses approved by the OSI, and everything in between.
Most people imagine Shared Source as an avenue to open sourcing Microsoft's key product assets and are disappointed when they see restrictive licenses and difficult eligibility requirements. It's easy to assume that clearly Microsoft doesn't "get it" with open source, or more deliberately is generating confusion in the marketplace. Microsoft has a breadth of software assets and artifacts. The sharing program eligibility and licensing reflects the value of the software asset to shareholders. On one end of this software spectrum are the narrow-eligibility, high-liability programs around the Windows and Office core revenue generating assets (e.g. Government Security Program, Enterprise Source License Program, etc.) There is tightly controlled access to the code, with restrictions on what people can do with it (often read or debug or limited modification without redistribution rights). The penalties for license breach are high.
These restricted "sharing" programs are tied to the core revenue generating products for the company. (Take a look at the recent quarterly SEC filing. Go to the last page on revenues. Add Client plus Server and Tools and compare that to the total.) The responsibility of the executives to shareholders kicks in pretty quickly. They must take a worst-case, conservative view of the risks (brand damage, legal, revenue stagnation, engineering costs). They must have some form of hard data to support the premise that the more they open the source code base then the more revenue will grow. With these key revenue generating software assets, the company is essentially caught between the shareholders and customer base.
Opening Windows
Related Reading
Understanding Open Source and Free Software Licensing
Understanding Open Source and Free Software Licensing
By Andrew M. St. Laurent
Table of Contents
Index
Sample Chapter
Read Online--Saf
Microsoft Open Sources Windows, its a sign of the antichrist coming.
The people at Microsoft aren't stupid. They completely understand open source. But, they also understand the value of a closed proprietary system. Microsoft earns 80% profit margins on Office and Windows. When Red Hat earns that kind of profit, then Microsoft might switch.
If someone says he and his monkey have nothing to hide, they almost certainly do.
I love how it mentions WiX. WiX has generated enormously good will for microsoft, at least with me.
I don't ever see them releasing all of windows open source, but just releasing small utilities like that open source for others to toy with is a HUGE step forward. Pretend that microsoft hadn't released WiX, and it stayed as time called it, insignificant. No one would have bothered with it except MCP's and others, and they would have used WinInstall LE or whatever.
But because microsoft released it free and OSS, an enormous buzz has been generated and an enormous amount of good will as well.
What I've imagined are thousands of developers worldwide working for years to cut bloat from the operating system eventually landing on a copy of Windows XP with all the relevant features that installs on a Pentium II with 64 megs of RAM on a 1 gig hard drive with plenty of room to spare.
Unfortunately there's a lot of effort and little to no profit to be had in reducing bloat; so for-profit companies rarely do it.
I'm a big tall mofo.
Why would Windows being open source make PCs less expensive? Open source != free.
New World monkeys or Old World monkeys?
It also shows that even if it might look that Microsoft doesn't understand the value of open source,
When you say "value", you mean "potential massive loss of revenue", right? Microsoft are there to make a profit. Expecting them to adopt open source is like expecting Ayn Rand to rise from the grave clutching a copy of Das Kapital.
Slashdot: News for Nerds, Stuff that matters only to them
I wonder if the code behind start.com/1 is shared source. It has a nice javascript RSS reader I'd like to copy *cought*
Look at your post.
If Windows became open source we would see £100 knock down on the price of every single PC.
This would then make more people buy PCs, which would help the whole industry except Microsoft.
Microsoft isn't going to do anything that won't help Microsoft. They have an obligation to shareholders to increase profits and market share (dominating as they are). Of course, this is only the case with their current business model.
Now, if they switched to a service contract type business model and open sourced Windows, things might be different. Think of those people that still have Windows 98. What if they had been paying, say, $10-$15 a year since then for support? Microsoft would have made more on them than the customer's initial purchase of Windows (assuming an OEM installed Windows, not Retail).
The customer doesn't have to get support, but lots of people pirate Windows anyway. Might as well release it to everyone and work on *really* good tech support.
Maybe I'm simplifying things too much. I'm sure someone will correct me.
Qualitas edurus commercium, nullus penitus net rimor, nullus deus beneficium
A tip... when posting on slashdot, do not watch porn... especially hardware porn...
Steve is a great guy, and he did some wonderful stuff for Microsoft, and for the rest of us as well. Interix makes all the difference for me... it's like a shoulder-length rubber glove between me and the Win32 subsystem.
But maybe he doesn't quite appreciate the damage Microsoft has done to their reputation by bundling together true open source programs and traditional restricted source releases to customers under a single banner. It's confusing, and they should at least downplay it... they should separate out the truly Open Source components and make it clear that they do Get It, if only in little bits here and there.
And if they'd open-source Interix, whooo... it'd be like attaching a Jato unit to their public relations problem...
Seriously, WiX is Windows-specific. They've just given you one more way to tie yourself to windows.
They currently have a fully documented MSI Windows Installer file format. This is problematic because it's binary and isn't amenable to change. By moving to XML, they aren't making things less transparent, they're just making things easier for them to upgrade with stylesheets. It's a no-brainer to open source because it was already open.
How would M$ make money at this? Before I get blasted the same kind of money they are making today. Open source is great, but aren't most of the posts anti establishment? Why is it bad to make money? If you don't like don't buy it. You can not ask a man who has been making money the same way for years to suddenly stop.
No this is nothing against Linux, I run Linux for certain applications and I run M$ for other applications. They are just tools. I always use the correct tool for the job.
My sigs offend the max # of people all over the world, regardless of race, religion, color, sex or creed. It's a gift.
Read that as "Open source is currently in, we need some of that".
I can't help thinking that someone considers WiX a casualty of war.
Do you see what I did there?
all this " feel-good-happy-sunshine day " stuff is fine, we can all envision our own utopias and see our children playing in wheat fields and whatnot, but the reality of the situation is that a marked paradigm shift would need to occur before microsoft truly embraces " open source " .
open source is not mutually exclusive to programmers and code . open source is the way of the future in terms of the thinking that it fosters: transparent, goal-oriented ( rather than profit-driven ) teamwork . nothing lasts forever, especially not behemoths the size of microsoft . eventually, a better path will be found .
Umm, no, actually it is you who seems to be confused.
Here's a summary (from the page linked above):
Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:
You are confusing Shared Source with Open Source. Shared Source means that you can peek at the source, if Microsoft likes you, you are willing to sign a NDA, etc.
Open Source also means that you can look at the source, but much more than that. You are also allowed to run the program for every purpose, modify it the way you want, and distribute the program and modified versions of the program. See the Open Source definition: http://www.opensource.org/docs/definition.php
Term "Open Source" is confusing, and Microsoft only adds to that confusing with their "Shared Source" (that wasn't on purpose of course). That's why I prefer talking about Free Software, which has a very nice definition at http://www.gnu.org/philosophy/free-sw.html and doesn't give the impression that being able to look at the source code would be enough.
The difference between Free Software and Open Source is of political nature and the question of what you want to emphasize (a good development model versus freedom). But if you talk about the licenses, they are very similar. I only know of 2 or 3 licenses which qualify as Open Source but not as Free Software.
it'd be like attaching a Jato unit to their public relations problem...
I understand what you were trying to say, but there are two small issues to consider:
JATO is an acronym for Jet Assisted Take Off and should be capitalized. It is used to help heavily loaded aircraft generate enough linear thrust (and thus lift) to take off on runways that would otherwise be too short. There is a neat picture here of a C-130 deploying a JATO.
Attaching an accelerating device to a problem just accelerates the problem (as in Interix's PR problem). No one likes a fast-moving problem. :-)
And just for fun, here is the link to the Snopes debunking of the alleged Darwin Award winner. The stories aren't true but perhaps they should be...
I want to drag this out as long as possible. Bring me my protractor.
Open Source is, from a legal point of view, practically identical to Free Software. The group of people who created the OSI intended the term be used to "sell" Free Software as a concept to businesses by extolling the virtues of a community development process enabled by licenses that gave developers free use of the code created.
While Open Source, in practice, is less about freedom and more about methodologies (sometimes to the detriment of freedom, unlike the FSF, the OSI doesn't urge developers to avoid licenses that are technically free but actually create genuine practical problems), you most certainly are granted more than just the right to see the code.
You are not alone. This is not normal. None of this is normal.
Microsoft has to file monthly reports with the SEC, detailing its profits and expenses. If the quarterly profit numbers change even a little bit, even if they are "lower than expected growth," the stock price can decline sharply.
If Bill Gates alone, or all the executives decided to switch to an open source model one day, I guarantee that even if the switch had yet to take place, the expense of starting such a project would have a large impact on profit, and may cause a stock price slip. Too large of a slip, and the board asks nasty questions. Don't forget, Microsoft only answers to Bill in the short term, anything longer than about three months puts the board and the stockholders in charge.
Stockholders like 80% profit margins.
Here's what I'd really like to see: Microsoft opening/sharing/whatever the source code to the NT kernel. Just enough to build NTOSKRNL.EXE, NTDLL.DLL, and a couple of HALs (one UP, one MP). This would provide device driver developers with an enormously valuable resource. I suspect this would eventually lead to greater driver stability, as many of the "magic incantations" currently required would start to make more sense.
Also, releasing the kernel source would not enable sudden flood of Windows-wannnabes. Just as in the Linux world, "kernel source does not a distribution make".
share1 Audio pronunciation of "shared" ( P ) Pronunciation Key (shâr)
................
n.
1. A part or portion belonging to, distributed to, contributed by, or owed by a person or group.
2. An equitable portion: do one's share of the work.
3. Any of the equal parts into which the capital stock of a corporation or company is divided.
v. shared, sharing, shares
v. tr.
1. To divide and parcel out in shares; apportion.
2. To participate in, use, enjoy, or experience jointly or in turns.
3. To relate (a secret or experience, for example) to another or others.
4. To accord a share in (something) to another or others: shared her chocolate bar with a friend.
Don't microsoft mean Displayed Source initiative, as your not allowed to use all of it , Yes some is under OSI aproved licenses, though some of it effectivly puts your anatomy in a vice if you want to work on certain projects in the future.
The only things certain in war are Propaganda and Death. You can never be sure which is which though
Because once making money goes above all other pursuits, it starts to damage the environment, the people, the animals, everyone.
Making money is not bad (it's a tool like anything else, a way to measure resources) but making it your god which justifies all means, that is bad.
Corporations have no soul and no social responsibility. If they could make lots of money by selling babies stolen from the birth ward and then beheaded, you can be 100% sure that's what would happen! "If you don't like, don't buy it" doesn't make a difference since the damage has already been done.
I'm sure these are among the reasons many people consider money and making money to be bad.
This is a sticking point that people in the Windows camp don't seem to be able to get around.
1. "Linux" is just the kernel. I think that's what this guy was trying to say when he said that the Windows tree is not the Linux tree.
2. A mainstream "GNU/Linux distribution" like Mandrake, RedHat, Fedora, Novell or Debian is more akin to Microsoft Windows Professional + Microsoft Office + Microsoft Plus Pack + Window Blinds + Norton Internet Security + Roxio + [insert any brand of CD/DVD ripping software here] + Development tools + IIS + Microsoft SQL + Abobe Photoshop or Paint Shop Pro + Outlook. At least for a start.
So, if you are going to compare Microsoft Windows to a mainstream GNU/Linux distribution, you quickly see that the GNU/Linux tree is not the Windows tree as there is a whole lot more source code that does into your average distro and a lot of it is very tightly integrated. This is why it is pretty amazing that all the distros are really good about not just updating the basic "OS" code, but all the bundled apps as well. If Microsoft really released a Windows distribution with all the same functionality as a typical GNU/Linux distro, I have a feeling they'd have an even harder time keeping up security wise. It's interesting to note that the supposed independent studies of Linux vs. Windows always harp on how many more security updates that GNU/Linux distros put out than Microsoft does for Windows. They attack that claiming that there are far more security holes in the OS but still equate Windows as offering the same services with fewer patches needed. However, it quickly becomes obvious that since Windows provides such a small amount of functionality when compared to a GNU/Linux distro, they do not offer the same services. It's highly likely that if they did, their patchlist would rival all GNU/Linux distro's patch lists combined. :)
-"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
Where are the 10 GHz CPUs we were supposed to have by now? What about a 5 GHz one? How long has the 3 GHz CPU been state-of-the-art?
You would find out how much linux is in windows.
The question is, what would Microsoft have to win or to loose from publishing part of its sources. And which part would they publish.
And if someone would like to distribute a modified version why not? You would still be required to have a license for Windows to run it.
Now, I would like to be able to change a few things in Windows (like everything except for the GUI). The actual core of the OS is not so great anyway.
(I wonder if ReiserFS is better than NTFS. Did anyone do any benchmarks? It might not be so easy to compare separate components of two OSes. I am inclined to think Reiser is better.)
(by the way, is it possible to change the FS of the partition Windows is booting from, even without having access to the source code? like studying the ddk and writing and replacing some dlls? )
Why don't they make sources public?
It's not like Windows works so well that everybody wanted to copy it.
I guess it's because once the sources become available there would be much easier to make a windows clone. WINE is getting closer anyway, but still has a lot to go.
And also, who would stop you from turning your Home edition into the Server one by replacing some components with third party ones (possibly free ones).
I think most people would buy and use the Official Windows Version anyway. It's a matter of psychology. Microsoft could then make agreements with third parties to include their changes in the official distribution. I think there are people that would contribute code for free only if they were given the chance to modify their windows.
about which parts they could open: It wouldn't make sense to publish the code for Office, but next to that I think the GUI they should be interested in keeping secret, because that's what they have best. They could make public the parts that don't really work well.
Various data are kept in an
dismay at what an obfuscated object model MS Word presents
admiration for the VBA enviornment for creating such a silk purse out of this sow's ear.
So, in addition to tidying the operating system (or at least producing well documented test cases showing WTF), we could also expect to see gradual creation of wrapper classes that would un-bork a lot of this ugliness. I'm envisioniong http://ms_office_space.sourceforge.net, or something, as an umbrella project for libraries that are as 'easy' to use as VBA, but are in a language we can use without negative impact to our self-esteem.
That will be enough wishful thinking for now, Chris; back to work.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
1) OEM licensed software, Microsoft doesn't support. The OEM is required by the software license. 2) Microsoft already charges for the limited support they do offer. At least phone support. Email support is free, but worthless. Having gone that route, I don't believe anyone actually reads the emails sent, but a computer analyzes it for keywords and sends a boilerplate message based on the keywords. Then in slaps a name on the message to make it look like a real person is responding. 3) Most consumers want to pay up front (or finance), not subscribe to a support service. And what's to keep a user from not subscribing until a problem comes up, getting a 1 yr support contract, and then canceling after the problem is fixed (possibly getting a proration)? 4) Corporations that purchase support, are already getting that support elsewhere. Granted its largely Microsoft rhetoric generated to dupe the masses and make themselves sleep better at night, but they insist that their current model is used to help OEM system builders sell value-added services. 5) On the point someone made earlier about hacking WinXP to get it to be usable on older/lesser hardware, it comes back to the point made earlier in this thread. Selling bloated software is good business for all tha hardware manufacturers whose products are being sold to run the new software. Look at gaming and video cards. New cards come out to better run new games and new games come out to better take advantage of the capabilities of new cards. WinXP isn't going to run well on my PII 233 with 64MB RAM work machine, so if my employer wanted to upgrade to XP, they'd have to buy new hardware. And that makes companies like Dell and HP, happy and supports their profit margins, marketshare, and shareholder dividends. 6) Win98 came out 7 yrs ago. At $10-$15/yr, that comes out to $70-$105. Thats just barely breaking even with the current distribution model. Are the shareholders going to be happy with a business model change that takes longer to see the same profit? 7) It's a good idea, unfortunatly, not grounded on enough reality. mofe) I just wanted to use the number invented in one of the newspaper comic strips. sorry.
Free MacMini
In your brain-dead model of processors and computers they are only on desktops.
Suppose the Government decides to place monitoring statins along the border with Mexico and they place, say, 10,000 of these at the cost of, say, 10,000 dollars a piece. So that is 100 million dollars.
and then a few years in to this some flaw is discovered in the code. The solution is to upgrade the operating systems of these nodes.
In your model they must replace the processors and motherboards.
Capital equipment and infrastructure must have an upgrade path. Also it should be expected to last more than ten years. Why? Otherwise it is just a big fat boondoggle.
M$ is a toy operating system and no serious captial equipment designer should even consider it. It is crap, insecure, and actually dangerous for our security. That is why there is such a push to not use it anymore.
But the M$ people have so much damn money that they get their stuff approved because so many people have thier stock.
hope you have that patched XP or else your machine is probably a drone owned by some eastern europoean script kiddie.
Oh, and by the way, the cost of computer is also the cost of installing and running the computer. So if we are talking about capital equipment we want an operating system that is easy to install and upgrade. That is not the M$ one.
I find it hard to see that Microsoft's license would be any more liberal than the one that Sun have used to open up Solaris 10.
"Sure you can look at it, but you can't use it without relicensing your code under our license. And if we find our code in any of your work we'll sue you. "