Slashdot Mirror


What Should Microsoft's Open Source Strategy Be?

JWinterboy asks: "I'm guessing that everyone here has a valid criticism of Microsoft's attacks on, and approach towards the Open Source model. To me, that begs the question of what we think would be an "appropriate" reaction from Microsoft towards the Open Source model. It doesn't have a service arm, so IBM's approach isn't really viable. At the same time, non-service related business models haven't fared very well. What would we like to see Microsoft do? How can it work with the Open Source community, leverage its resources, and still make a buck?"

7 of 759 comments (clear)

  1. one thing by ryusen · · Score: 4, Interesting

    why not open up the code for the stuff they don't make money on? heh open up IE, Messenger, etc. Don't allow anyone to distibute their own versions, but let people look and submit bug fixes etc. It would not be a huge step, but i'd be a step in gaining people's trust

    --

    I believe sex is highly over rated... unless it involves me
    1. Re:one thing by ender81b · · Score: 4, Interesting

      why not open up the code for the stuff they don't make money on? heh open up IE, Messenger, etc. Don't allow anyone to distibute their own versions, but let people look and submit bug fixes etc. It would not be a huge step, but i'd be a step in gaining people's trust

      Of course they make money on them - otherwise they wouldn't make the product. IE is designed to garner market share, to force people to use IE gives ms alot of 'pull' when it comes to the web - in particular designing proprietary protocols that only work with MS products like .Net and ActiveX. MS messenger I'm not to sure on other than this - it gets people a .Net passport which means it will be 'easier' to shove products down their throat - they already have a passport just buy! (same with hotmail).

      A more realistic approach would be for microsoft to realase 'old' code - stuff like MS-dos 5.0, or maybe 6.0. Windows 3.1 - products they no longer support. It would be interesting to see what would come of this.

  2. API's and documentation and consultation by electroniceric · · Score: 5, Interesting

    What MS should do to work well with Open Source:
    a) Document API's thoroughly, and keep the docs up to date
    b) Standards: Microsoft is frequently the first one to implement a standard or to make it mainstream. As an example, XSLT comes to mind. AFAIK, IE was the first browser to support XSLT. As the first big boys there, they usually claim the right to make modifications to a standard or to fill in details in the standard. They could win a lot of goodwill merely by consult other companies and open source developers before as they implement the standard. This will greatly reduce (though probably not eliminate) the feeling of railroading that we all feel when MS' software doesn't follow standards, and we all have to deal with it.
    c) Document and admit mistakes and bugs. One of the most infuriating things about Microsoft software, is that it either doesn't do what it says, as in undocumented behavior and bugs, or cryptic error messages saying things don't work unless the OS is configured right (which is true ipso facto, but somewhat accusatory, and certainly not helpful). I think this happens mostly because they can get away with it, and writing thorough documentation for your programs is not nearly as satisfying or financially rewarding as designing and writing the code itself. They could again improve goodwill if they were responsive to outside developer's questions about these bugs and behaviors, rather than being dismissive.

    I'm sure there are more, but these sure would make it easier for an outsider to like Microsoft.

  3. Actually, Microsoft could follow Apple's model by dmoen · · Score: 4, Interesting
    Besides, Darwin won't run on anything else *but* their hardware

    Darwin runs on x86 as well.

    The interesting thing about Apple is that MacOS X is *not* open source, although the Darwin kernel component is. The Quartz graphics engine, the Aqua gui layer, and all of the traditional MacOS apis, are not open source.

    Microsoft has a product called Interix, which consists of a Unix subsystem that plugs into the Windows 2000/XP kernel, plus a large set of Unix utilities. Microsoft has open sourced their versions of gcc, gdb, etc, because they have to, but they haven't open sourced the BSD based utilities that come with Interix, even though they'd lose little by doing so.

    If Microsoft open sourced the entire Interix product (utilities and subsystem), then their operating system would be like Apple's, with an open source Unix component, and a larger proprietary component containing all of the APIs that are special to Windows.

    Doug Moen

    --
    I have written a truly remarkable program which this sig is too small to contain.
  4. Isn't this moot? by Chris+Johnson · · Score: 5, Interesting
    Don't we already know what their open source strategy is?

    Embrace and extend. What else? Or were you wondering what their strategy should be if they did NOT want to dominate the whole freaking world? That's kind of academic.

    In fact, the strategy they have is a damned good one. It'll be even better if nobody clues to it in time, which is why I particularly delight in outing it here. This is my interpretation, and they may possibly phrase it differently- or not. Maybe in the NEXT antitrust fiasco this will come to light.

    MICROSOFT'S OPEN SOURCE STRATEGY

    • Come up with a license and call it an open source license
    • Release a bunch of source under this license
    • Have the license be VIRAL, in that it propagates a specific legal point that can't be removed, like the GPL propagates the ability to sublicense.
    • Instead of virally spreading ability to sublicense, have the viral-propagated clause be an admission that the developer remembers copyrighted information from the 'shared source', and an acknowledgement that the developer does not have rights to use the copyrighted information.
    • Further include a term that defuses the use of patent protection in self-defense.
    • Attempt to get this viral license adopted, and the code seen, by as many open source developers as possible.
    • Sue every open source project that's a threat, on the grounds that they are using 'shared source' in defiance of the terms of the licensing agreement, and are therefore in copyright/patent infringement.
    • Using the terms of the shared source license, establish that people who've agreed to it legally acknowledge that they are remembering concepts from shared source and are furthermore aware that they're not allowed to make use of them outside of shared source.
    • Using this acknowledgement, require the developers (of any major open source project) to prove their innocence of copyright/patent infringement from a presumption of guilt already established with the admission in the previous step.
    • Win, or draw, or just bankrupt the other side using these interesting complications, trying wherever possible to completely prohibit commercial or noncommercial use of the disputed open source code, on the grounds that it is pure thievery.
    • Now- after an initial waiting period during which you get the shared source seen and used by as many developers as possible, take all that and think big: sue EVERY open source project at once along these lines. Throw money at the problem and try to get pretty much all of the open source ground absolutely scorched so there's no chance of anyone freely cooperating to develop any such threat again..
    • Keep pumping Shared Source into the schools all the while, to guard against future outbreaks.

    This. Is. What. They. Are. Doing.

    Note that it plays to their strengths, including the strengths they've learned in the antitrust trial, of barratrous lawsuits and dragging things out endlessly, and note the brilliance of embracing and extending, not the openness of collaboration, but the concept of a viral license. This is brilliant conceptual work on their part, it really is.

    But it does not have to succeed- because they really need people who are KNOWN to have agreed to their license. They can't really go around suing everyone who writes open source and dragging them into court and saying, "You DID agree to the Shared Source license, didn't you? Everybody does! You had to have!". That won't fly- people who can legitimately say they've never agreed to that license are in a position of strength.

    However, people who have in fact agreed to their viral Shared Source license, EVER, are fucked. And can never be allowed to participate in open source or free software development- because of the legal exposure.

    Given this state of affairs, why would Microsoft ever need to find another open source strategy? This is unquestionably the best one for their goals. Yes, it's evil. And your point is?

  5. Re:Answer the question?!? by Malcontent · · Score: 4, Interesting

    "Mozilla will hopefully change the story, but it's YEARS too late in an industry that works on Internet time. "

    No it's not too late at all.

    Right now I prefer mozilla to IE on my windows box. It loads faster, it renders faster, it has more features then IE and it crashes less. No I am not kidding it's true. I honestly don't know how people get along without tabs and gestures they simply don't know what they are missing. Not only that but Moz does not cram advertising down my throat whenever I make a typo in the URL bar, it does not have crypic and misleading "options" like "enable profile assistant" and "show friendly HTTP messages". In other words it does not lie to me and try and fool me into giving up my privacy.

    All we have to do is to make this knowledge widespread. Tell everybody you know that mozilla is better, faster and safer then IE because it's the truth. IE and Mozilla are designed for different things. Mozilla is designed to deliver the best web browsing experience possible IE is designed to deliver advertising to people who use windows, to increase hit counts at MSN, to get people to sign up for hotmail, to get people to sign up for passport. Different products for different purposes.

    If you want to browse the web use mozilla if you want to receive adversing and help Bill Gates make more money use IE.

    --

    War is necrophilia.

  6. If I were Microsoft by Nailer · · Score: 4, Interesting
    Things Microsoft Aren't Doing
    • I would document every existing key in the default Windows registry in a publically avaliable format, included with the OS.
    • I'd allow all changes to a Windows server to be reversable and changable in time
    • I would perform every step in MS lockdown guides as aprt of the default Windows install
    • I would make every Windows service run in a filesystem and process jail by their default install.
    • I wouldn't have any ports listening on a Windows server install by default (without a firewall).
    • I'd make part of the `Designed to Work With Blackcomb' badge program include a provision that to install or update a piece of software, a reboot must not be required.
    • Again, for the `Designed to Work With Blackcomb' badge program, I'd specifiy that software installation must not require interactive operation, allowing Windows admins to install thousands of packages simultaneously.
    • In the subsequent release of Windows, I'd provide that software providing service to end users must not need to restart or to accept changes.
    • I'd include SMS for free in Windows.
    • I would improve Windows scripting, and make command line interfaces available to the most popular Windows libraries, and libraries available for most popular Widows programs, so you could, for example, write a simple backup script and SMS the systems administrator if the backup fails
    • I'd include *all* necessary security updates on Windows update. I would sign up admins to recieve security notices as part of the post install wizard for Windows.
    • I would integrate the Event viewer and Windows messaging in some fashion to make sure administrative emails are being read.
    • I'd give Unix administrators the tools they need to work with and feel comfortable with my OS
    • I'd make a very scalable version of Exchange / Sharepoint that used a real database as a backend, that was trustworthy enough to be put directly on the net.
    • I'd allow servers running this protocol to connect with each other directly over the internet, bypassing SMTP, with many benefits to administrators for doing so. Thus I would push admins to remove SMTP based mailers from their MS based networks.
    • I'd include a virus scanning engine in Windows and Exchange that worked reliably
    • I'd pay external consultants to audit Windows code. Not excluding a large chunk of the OS like a certain BSD flavor, but the entire thing.
    • I'd make sure everyone on the planet knew at least five things you could do with Windows that you couldn't with Linux.
    • I'd create a new certification for Windows consultants with an emphasis on security and lab based, instructor graded tests.
    • I'd find out real world things that piss off Linux administrators about Linux (not things that Windows administrators are unsure about Linux). Then I'd make sure that Windows solved that problem.
    • I'd make sure people knew that we were making these changes in response to their demands, and because we're a competitive company, rather than a simple and bright but technically substanceless software company.