What questions do you have for Microsoft's Shared-Source chief?

What questions do you have for Microsoft's Shared-Source chief?

Summary: On Monday, March 15 2005, I'm scheduled to do an in-person interview with Jason Matusow. Matusow is the director of Microsoft's Shared Source Program and is the company's top thought leader when it comes to Microsoft's go forward strategy on the open source front.

SHARE:
TOPICS: Open Source
25
On Monday, March 15 2005, I'm scheduled to do an in-person interview with Jason Matusow. Matusow is the director of Microsoft's Shared Source Program and is the company's top thought leader when it comes to Microsoft's go forward strategy on the open source front. The interview with Microsoft open source kingpin will be recorded and made available as an MP3 download and through the RSS feed for ZDNet's IT Matters series of podcasts (see: ZDNet's Podcasts: How to tune in).

In advance of the interview, I thought I would check with ZDNet's audience members to see what questions you'd like Matusow to answer. Unfortunately, I won't have him for the whole day so I won't be able to ask all of your questions, but I'll certainly try to ask the best and most thought provoking ones. If you'd like to submit a question, use the comments section below (please don't e-mail them to me). This way, Matusow can watch too. For the sake of disclosure, I sought approval from Matusow to post this blog entry in advance of our meeting (some people like to keep their schedules private). Before posting questions, a Microsoft spokesperson suggested that ZDNet's audience members might want to familiarize themselves with the company's Shared Source Program by visiting the program's homepage on Microsoft's Web site.

Topic: Open Source

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

25 comments
Log in or register to join the discussion
  • How about opening up the Word .doc format?

    Please ask him about Microsoft's stand on the ubiquitous .doc format. Microsoft dominates the world of desktop productivity software. Why make it difficult for other software vendors to work with this format? The world needs the Word .doc specs!
    sigmascape
    • Don't they have Word doc XML schema...

      ...which is publicly available?

      http://www.microsoft-watch.com/article2/0,1995,1388100,00.asp
      John Carroll
  • WINE

    Please ask him why Microsoft has decided to eliminate online MS Office updates for Linux users running WINE. This is one of the most recent decisions that MS has made about this form of oss.
    sigmascape
    • Some cheese with that wine

      ..Please ask him why Microsoft has decided to eliminate online MS Office updates for Linux users running WINE...

      Since they haven't done that it's a wasted question.

      Nice one FUDster.

      Joe
      seosamh_z
      • When is Windows going to be Open Source?

        and free (also free of viruses)?
        matrixdomain
        • Never I'd say.

          Don't even know why you're asking me.
          Try bill.gates@microsoft.com

          Good luck and let us all know the answer.

          Joe
          seosamh_z
      • Nice FUD

        "..Please ask him why Microsoft has decided to eliminate online MS Office updates for Linux users running WINE...

        Since they haven't done that it's a wasted question."

        See this link:

        http://news.zdnet.co.uk/software/windows/0,39020396,39189180,00.htm

        While they have not eliminated MS Office users under WINE from MS Office updates, they have attempted (have not seen any analysis on the success of this venture) to eliminate WINE users from MS Windows updates. Since MS hooks everything so inextricably to their OS, it is somewhere between concievable and likely that these users are missing functionality or fixes for MS Office that come out as MS Windows updates. As paying customers of MS, it seems strange to penalize them in this manner. OTOH, it is somewhat reasonable to try to exclude a competing OS from getting access to MS OS level code. This is a difficult conundrum to find a reasonable stance on. I see plenty of arguments on both sides.

        Your post increased, not decreased, the FUD level.
        Mack DaNife
        • Oh yeah....

          ..While they have not eliminated MS Office users under WINE...

          So you agree with me about Office Update but then start on about Windows Update

          ..it is somewhat reasonable to try to exclude a competing OS from getting access to MS OS...

          So where's the FUD dude?

          You're not making any sense.
          Good luck in the future.

          Joe
          seosamh_z
  • Open source VB 6?

    It's becoming apparent with the latest MVP uprising that this is clearly a problem that Microsoft hasn't a solid solution for. Has Microsoft considered opening up VB6? If VB.NET is the future for the company and the platform, it seems that opening up relevant VB6 pieces into it's own open-source-like fork would keep some customers happy without distracting Microsoft's own development resources. The VB6 community could at least maintain it's own minimal QFE/Sustained Engineering effort and keep existing apps breathing without dragging down the VB.NET brand and at a minimal cost. Knowing Microsoft opened up VB6 might even encourage them to try VB.NET since their is hope that when VB.NET has "expired", it too won't force an immediate upgrade. Just a thought.
    ssweens
    • Shared Source <> Open Source

      I can't see them Open Sourcing VB but they should allow someone/group to continue development.
      The .Net platform is not for everybody but they are trying to get the casual programmers back with the future Whidbey release.

      Joe
      seosamh_z
  • Scared source?

    Isn't it a little odd that MS is pushing into open source, when there are still proprietary hooks in the operating system for products like IE? How about publishing all interfaces between MS products, and make those interfaces publicly available? Some think that full disclosure of interfaces and MS together in a sentence constitutes an oxymoron.
    mannyack
    • Hope this helps

      ...How about publishing all interfaces between MS products, and make those interfaces publicly available?...

      http://msdn.microsoft.com

      Let me know if you have any problems with the concept.

      Joe
      seosamh_z
  • how does a company get access to the shared source program?

    This is a key question
    blewerg
  • If not everybody can see the code, how do we know we are seeing it all?

    For example, there was the case of Apple Quick Time failing because of a "fix" Microsoft put into its code.

    Do the organizations who can look at Windows get to see all of the "fixes" or is the shared code devoid of such things?
    George Jay
    • Additionally..

      ...If no one can see all of the code, how do we know that we are seeing all of the relevant parts?
      Mack DaNife
  • I was wondering...

    ...why MS places all of the major barriers to Shared Source by average individuals? As a company that originated with a couple of guys with a "better idea" that they were able to parlay into a multi-national company, I would think that they would have more affinity for the "little guy."
    Mack DaNife
    • Times change...

      I was once a ditch digger in my early days, I have no affinity to anyone digging ditches for a living. What's your point?
      No_Ax_to_Grind
  • Two questions *I* would like to hear.

    1. Why would anyone at MS grant an interview to an obvious MS basher?

    2. Given that no answer given will satisfy the MS bashers and the "software for nothing crowd", why waste the time?
    No_Ax_to_Grind
    • Microsoft has too many enemies and bashers

      it's hopeless for a company like Microsoft. M$ is simply bad business but fortunately there are better alternatives like Novell, Redhat and many others
      matrixdomain
      • Care to make a comment that's on topic?

        I mean I understand your deep meed to rant uselessly, it's something inbred in open source supporters. But what has it to do with my questions?
        No_Ax_to_Grind