Slashdot Mirror


Microsoft Wants Sit-Down With OSS Advocates

bonch writes "Microsoft is reaching out to the OSS community and wanting a sit-down to discuss how to better to interoperate with them. At a conference sponsored by the Association for Competitive Technology (ACT) in Cambridge, Md., Microsoft's Brad Smith extended an olive branch to its competitors, including the OSS community. 'We're going to have to figure out how to build some bridges between the various parts of our industry,' he said. Eric Raymond responds, saying the first steps Microsoft could do are to open their file formats and support open standards."

8 of 553 comments (clear)

  1. Publicity stunt by treff89 · · Score: 3, Informative

    This is nothing more than a marketing brainwave. Microsoft will never in their right mind help the OSS community, unless the OSS community helps them an exponentially greater amount. MS realises they are fast losing ground to FOSSS, and the lifejackets are out.

  2. Very Inaccurate Title by NatteringNabob · · Score: 5, Informative

    Well, I RTFA, and this is one of the most misleading titles I've seen in a long time. Microsoft explicitly states that they think their arsenal of software patents is a fine thing and they aren't willing to give up the right to sue. And if they aren't willing to give that up, what is there to discuss? In addition, there isn't anything that requires discussion. If Microsoft was really interested in wokring with the FOSS community, I'm sure there is somebody in their army of lawyers that could figure out how to write a royalty free non-discriminatory patent license that was compatible with the GPL. There is no need to discuss this with anybody, they can 'just do it'. The fact that they chose instead to have one of their lawyers give a content free, buzzword compliant speech tells us all we need to know about Microsoft's olive branch; the only thing they are interested in using it for is to poke people in the eye with it so they don't notice the sledgehammer they are holding in the other hand.

  3. Re:Just say Dr. No by bataras · · Score: 5, Informative

    wasn't that goldfinger?

  4. Re:Ho hum, again? by harvardian · · Score: 4, Informative
    one of the big selling points of their "new technology" (not what NT stands for, btw)

    It's not?
    Q. What does the word NT (in "Windows NT") stand for? Is it just a name that Microsoft conjured up from thin air or does it actually have a full name like "Networked Terminal"? Souvik Das, Ithaca, NY (souvik@oracorp.com)

    A. When we first released Windows NT in 1993, Sun said it stood for "Not There" and IBM said it stood for "Nice Try."

    Actually, the letters stood for "New Technology."

    But the letters have long since lost any specific meaning. Today, "NT" is just a designation for our high-end version of Windows.
  5. It's their second attempt by paj1234 · · Score: 4, Informative

    Here is a first-hand account of Microsoft's earlier effort in London, UK. Look for the great quote from Debian's Philip Hands at the end of the article.

    http://www.theregister.co.uk/2004/06/28/ms_mugs_th e_facts/

  6. what stallman sez will help by johnrpenner · · Score: 5, Informative

    --| Richard Stallman on How to Deal with Microsoft |-----

    The following is Mirrored from: http://linuxtoday.com/stories/4999.html

    Richard Stallman proposes three remedies that would help enable free
    software operating systems such as GNU/Linux compete technically while
    respecting users' freedom. These three remedies directly address the three
    biggest obstacles to development of free operating systems, and to giving
    them the capability of running programs written for Windows. They also
    directly address the methods Microsoft has said (in the "Halloween
    documents") it will use to obstruct free software. It would be most
    effective to use all three of these remedies together.

    1. Require Microsoft to publish complete documentation of all interfaces
    between software components, all communications protocols, and all file
    formats. This would block one of Microsoft's favourite tactics: secret and
    incompatible interfaces.

    To make this requirement really stick, Microsoft should not be allowed to
    use a nondisclosure agreement with some other organization to excuse
    implementing a secret interface. The rule must be: if they cannot publish
    the interface, they cannot release an implementation of it.

    It would, however, be acceptable to permit Microsoft to begin
    implementation of an interface before the publication of the interface
    specifications, provided that they release the specifications
    simultaneously with the implementation.

    Enforcement of this requirement would not be difficult. If other software
    developers complain that the published documentation fails to describe
    some aspect of the interface, or how to do a certain job, the court would
    direct Microsoft to answer questions about it. Any questions about
    interfaces (as distinguished from implementation techniques) would have to
    be answered.

    Similar terms were included in an agreement between IBM and the European
    Community in 1984, settling another antitrust dispute. See
    http://www.essential.org/antitrust/ibm/ibm1984ec.h tml.

    2. Require Microsoft to use its patents for defense only, in the field of
    software. (If they happen to own patents that apply to other fields, those
    other fields could be included in this requirement, or they could be
    exempt.) This would block the other tactic Microsoft mentioned in the
    Halloween documents: using patents to block development of free software.

    We should give Microsoft the option of using either self-defense or mutual
    defense. Self defense means offering to cross-license all patents at no
    charge with anyone who wishes to do so. Mutual defense means licensing all
    patents to a pool which anyone can join -- even people who have no patents
    of their own. The pool would license all members' patents to all members.

    It is crucial to address the issue of patents, because it does no good to
    have Microsoft publish an interface, if they have managed to work some
    patented wrinkle into it (or into the functionality it gives access to),
    such that the rest of us are not allowed to implement it.

    3. Require Microsoft not to certify any hardware as working with Microsoft
    software, unless the hardware's complete specifications have been
    published, so that any programmer can implement software to support the
    same hardware.

    Secret hardware specifications are not in general Microsoft's doing, but
    they are a significant obstacle for the development of the free operating
    systems that can provide competition for Windows. To remove this obstacle
    would be a great help. If a settlement is negotiated with Microsoft,
    including this sort of provision in it is not impossible -- it would be a
    matter of negotiation.

    This April, Microsoft's Ballmer announced a possible plan to release
    source code for some part of

  7. Re:Vlad the Impaler... by kbahey · · Score: 5, Informative

    A repeatable theme in history.

    A new founder of a dynasty will eliminate rivals from previous dynasties, so no throne claimant will emerge.

    One way of doing this, was to have a banquet, then no one leaves alive.

    One such occurance was Mehmet Ali Pasha of Egypt. He was sent by the Ottoman Sultan to Egypt (1805?), after the French Expedition there (1799?). He invited all the Mameluke commanders to a banquet, and then when they were in a passage, soldiers in muskets showered them with bullets. Only one Mameluke survived, after he jumped off the Citadel, his horse taking the shock.

    Also, when the Abbasid dynasty replaced the Umayyad dynasty in the early 700, Al Saffah (The Butcher), invited the dignitaries from the Umayyad clan to a banquet, and had them massacred. All who attended were killed. One scion of the Banu Umayya survived, after swimming across a river somewhere in the Levant. He fled to Iberia and established the Umayyad dynasty there.

    One other custom was for Ottoman sultans to have their brothers killed as the first act of succession to the throne. This fratricide was to ensure no rivalry will ensue as claimants to the throne would threaten civil war. This system was established after bitter civil wars caused ruin. One such war was between Bayazid II and Cem (late 1400s), both sons of Mehmet the Conqueror.

    Anyway, I digressed a lot. I am sure there are lots of other examples, but off the top of my head, the above are the ones that I remember offhand.

  8. Re:Vlad the Impaler... by m50d · · Score: 4, Informative

    As someone else said, slashdot's CMS (if such it is) is open source, there's a link to the system right there on the sidebar, and it's used by other sites, IIRC plastic.com runs on it or at least did.

    --
    I am trolling