Slashdot Mirror


Slides Of Microsoft Anti-GPL Advocacy

An anonymous reader links to these slides outlining Microsoft's position on Free software licenses, in particular the GPL, writing "Regarding the latest memo from MSFT, the current politics is to be against 'copyleft' type licensing... Protecting freedom is fundamental for Free Software and MSFT knows that. They don't want licenses that protect our freedom." Makes an interesting companion piece to the anti-OSS memo mentioned the other day.

25 of 423 comments (clear)

  1. It's a bunch of freakin jpg's by t0qer · · Score: 5, Insightful

    What good is this to my lynx browser?

    Kidding aside..

    It's just a bunch of jpg's on a non MS site. Just pointing out the obvious, what verification do we have these came from M$?

    Please tell me and don't mod down, I think I have a very valid question here.

    1. Re:It's a bunch of freakin jpg's by Maxwell'sSilverLART · · Score: 5, Funny

      Verification? If you can't trust something you read on Slashdot, posted by an Anonymous Coward, then who can you trust?

      (</joke>, for the sake of the moderators)

      --
      Moderate drunk! It's more fun that way!
  2. From Academia to Consumer by very · · Score: 5, Interesting

    A lot of time, softwares are developed by the Academia and heading straight to the consumer. And those software are usually distributed freely for non-commercial use (sometimes they are free for all).

    Apparently the Industry (a.k.a. Micro$oft) want the finding and development to go through the industry first.

    One motive: MONEY

  3. Good slides by Bjarne+Bula · · Score: 4, Insightful

    It seems someone at Microsoft has sat down and thought long and hard about this. I'm certainly not one of MS bigger fans, but I think they pretty much got this one right.

    Naturally, they don't like the fact that they can't take something under the GPL and integrate into their own products, like they have with BSD-licensed code. And, on some level, they have a very good point about products of research that are released under the GPL. The only value they have to any company working on a closed-source product is as an example, while a BSD-style license would have allowed them to take the existing code and adapt it.

    In this aspect, the GPL actually harms interoperability and if the purpose was to give the research results a wide impact, releasing them under the GPL would be counterproductive.

    I live under no illusions that all software will one day be open source, and perhaps it would be a good thing for people to think an extra time about the consequences of their choice of license.

    For standalone programs, the GPL makes a lot of sense, but perhaps BSD-style licenses are more appropriate for prototypes and example implementations. Perhaps also the operating systems themselves, but that's a harder call.

    1. Re:Good slides by Todd+Knarr · · Score: 5, Insightful

      Actually the GPL doesn't prevent companies from using the covered IP in their products. What it does do is force them to negotiate a suitable license from the original author of the covered IP (if they don't want to give away their own IP, that is). The big advantage to companies of the BSD license is that they can use the covered IP without negotiating with the original author and probably having to pay for the IP they use. That's the heart of MS's position: they want to be able to use everybody else's IP for free while still forcing everyone else to pay to use MS IP.

    2. Re:Good slides by Todd+Knarr · · Score: 5, Insightful

      Why is it a different story? The taxpayers paid for it, precisely why should a business be allowed to profit from it without paying royalties back in one form or another? What MS is asking is to be allowed to reap the profits while letting the taxpayers foot the bill. Sorry, that's not kosher in my book. And yes, we did lose something when MS used software developed by the DoD and NASA without paying: we lost the funds that went into developing it and that aren't being recouped.

      And it still comes back to, if the stuff was put out under the GPL, the company can go back to the agency that did the work and negotiate a license other than the GPL.

      Personally I think something along the lines of the LGPL, or a modified BSD license which requires that the software being used and any modifications/enhancements to it be made available under the terms the original software was gotten under, would be more appropriate than the GPL. It still boils down to, a private company should not be able to take taxpayer-funded property and use it to make a profit without some of that profit going back to the taxpayers in some way.

  4. first 4 slides: Source Licensing & SoftwareInd by ubiquitin · · Score: 4, Informative
    Let's transcribe this thing! Here are the first four slides, from the first two images (two slides per image). I'd love it if somebody transcribed the whole presentation, as there seems to be a lot to think about in there in terms of Redmond strategy.

    Slide 1: Title of the presentation with Microsoft logo

    Slide 2: The Software Ecosystem
    The flow of shared knowledge goes in a circle.
    Diagram shows customers to government to academia to industry and back to customers.

    Slide 3: The Business of Software
    subtitle: Source Code Licensing
    another diagram showing the interactions between source code - Core IP on the left and business model with usage rights and binaries on the right. Arrows showing development, support, deployment, and audit connect the two.

    Slide 4: The Open Source Software Model:

    complex mix of elements

    has produced some great software

    has both benefits and drawbacks like any model
    Diagram showing "development model" surrounded by "philosophy", "business model" and "licensing"

    Finally, somebody please mirror these images, the bandwidth on that site is getting sucked dry.

    --
    http://tinyurl.com/4ny52
  5. you don't get it by SweetAndSourJesus · · Score: 5, Funny

    See, Microsoft is a Big Evil Company. Their interest isn't making money, it's robbing people of their freedom. Withness the Internet Explorer debacle. Microsoft knew that I wasn't going to make them a nickel, but they released it for free so that they could take away our right to someone else's browser. Shit howdy, man, they don't care if they lose every nickel they've got so long as they get to keep robbing us of our rights!

    Don't you see, man? They're eeeeevil. So evil that anyone who alleges that they did something evil is automatically right. So evil that when they release good software we must overlook the fact that the software is good and instead focus on how they are bad.

    Microsoft operates the world's largest kitten and puppy grinding facility! Fact!

    --

    --
    the strongest word is still the word "free"
  6. Mirror by infolib · · Score: 4, Informative

    here

    Bandwidth sponsored by danish research funding...

    --
    Any sufficiently advanced libertarian utopia is indistinguishable from government.
  7. Imposing the GPL is like imposing free speech by argoff · · Score: 5, Insightful

    I'm glad some people finally understand that the battle isn't about markets or choosing a software license, but freedom. All to often people think that free markets are about markets, and not freedom. But just the opposite is true, when a society has healthy freedoms - the markets tend to take care of themselves.

    There is an old saying, a nation can't be half slave and half free - but only all slave or all free. Unfortunately, alot of people don't understand this about copyright controlls. They think that choosing a software license is like going to the store and choosing between pears and apples or between painting your room yellow or pink - that it's just about preference. Well, it is not, and it is so fusterating to see how people refuse to consider the long term consequences of their own belief systems.

    The simple truth is copyright controlls are untenable without massive free speech restrictions like the DMC0A (and beyond), and information is so easy to manuipulate and change form - that it can't be controlled unless all of it is controlled.

    1. Re:Imposing the GPL is like imposing free speech by Squarewav · · Score: 5, Insightful

      the funny thing about free speech is that people are free to chose how they express them selfs, is linux free as in speech, yes but so is microsoft, microsoft chose to keep thier speech closed and thats thier right. In fact I think it would be unconstitutional to force MS to OSS

      sorry about my spell'n

  8. Re:Nonsense by weave · · Score: 5, Interesting
    There was a long period in which Microsoft did not suck.

    Read the interview with a former microsoft developer on kuro5hin for an insight into maybe why this is so.

    Executive summary: Microsoft employees are arrogant assholes. (insert sweeping generalization disclaimer here)

    Quote from interview: Microsoft constructed an enabling environment for socially obnoxious behavior: it was welcomed and rationalized into positives. If you were late for meetings it meant you were busy doing important work, if you were extremely confrontational it meant you were passionate about your job, if you required subordinates to work long hours it meant you were committed to the product, if you turned down everyone you interviewed it meant you weren't soft, and so on. ... And some of that behavior trickled out into meetings with customers and partners, where they were correctly seen as negatives and helped foster the anti-Microsoft attitude. But since Microsoft kept hiring and promoting obnoxious people, they kept being obnoxious.

    Now this is just one former employee's opinion. But in sales meetings I have had with Microsoft, (I'm an IT manager for a 13,000 user college), I've seen the same attitudes.

  9. Re:Note that Free != freedom by Col.+Klink+(retired) · · Score: 4, Insightful

    > ...you don't really have much more freedom than with closed software, infact, in many cases you have much less.

    How is this possible? Closed source software never allows you to even see their source code, much less modify or redistribute it. Further, more and more closed source license even limit how you can USE the software. They often don't allow you to even install the program on more than one machine at a time.

    The GPL places NO restrictions on how you can use the program. As long as you don't redistribute, you have complete freedom to make any changes to the program to suit your needs. You can make unlimited personal copies and run on all of own machines.

    Only when you decide to redistribute a GPL'd program does it limit your freedom. Commercial software never allows you to redistribute it.

    So please tell me one instance where a closed source application has even a single freedom that the GPL doesn't already give you.

    --

    -- Don't Tase me, bro!

  10. Re:Note that Free != freedom by Selanit · · Score: 5, Insightful
    Stop equal Free Software with freedom, you don't really have much more freedom than with closed software, infact, in many cases you have much less.

    Okay, maybe I'm dense, but how does your line of reasoning go? The only restrictions I see in the GPL are that 1) You have to make your source available under the GPL if you make a modified version and you choose to distribute that version to the public, and 2) programs that use GPL'ed code fall under the GPL.

    That's it. You can use the program on as many machines as you want, give copies to your friends, all legally. You can even make modifications and keep the source to yourself, so long as you also keep the binaries to yourself. There is nothing in there to prevent you from being selfish. Heck, for most purposes you don't even have to accept the license. You can decline the GPL and still use the program all you want, you just can't legally modify it.

    Compare this to Microsoft's licensing policies. Let's take a specific example: Windows 98 OEM version. That Windows disc that came with your computer can only be used legally on your computer. If you replace, say, the motherboard, it's not the same computer anymore, and you no longer have the right to use that copy of Windows 98 on any computer at all. Similarly, if you sell the computer that the disc came with and build a new one, you cannot use it on the new computer, even if you wiped the old one clean before you sold it. And there are lots of other restrictions, too -- read through a Microsoft EULA some time. If you actually take the time to understand it, you will find that there are about a zillion restrictions on how you can use the program. And of course you are not allowed to modify it, and couldn't if you wanted to, unless you are a wizardly programmer who can read binaries and reconstruct the original source code from them.

    Compare this to the GPL, where there are only those two restrictions, and they only apply to developers. And the GPL is probably the most restrictive open-source license: others, like BSD-style-licenses, or the Zlib license, place effectively no restrictions at all on your use of the program. So, please explain to me: how is it that you have less freedom with open software than with closed?

    I must conclude that this AC is a troll. Dang. Oh, well, I've got karma to burn.

  11. The GPL, it is all about me ... by codepunk · · Score: 5, Interesting

    First off the number of software companies vs other sectors is really small. I work as a porogrammer / sysadmin at a manufacturing plant. Do we really care if it is bad for microsoft when we use GPL software. No we care about reducing overhead thus lowering the cost of manufacturing thus allowing us to take bigger price cuts on our products while maintaining the same level of profit. Linux makes us competitive in our industry and this is why we use it, religion is not the issue but simple economics is. Furthermore do I want to sit at home each night and write some code for MS so that they might be able to sell it back to me and or overcharge my company for it. No thanks I will choose the GPL!

    --


    Got Code?
  12. The GPL protects the developer ... by codepunk · · Score: 5, Informative

    No the GPL ensures that some slug is not going to compile in my library and try to sell me back my own code. The GPL is my reward in knowing that I not going to be taken advantage of.

    --


    Got Code?
  13. Viral license?? by Selanit · · Score: 5, Insightful

    In the sixth slide, it says that the GPL is 'Known in the OSS community as a "viral" license.'

    Totally regardless of whether or not the GPL is viral, isn't this the description that Microsoft came up with?

    I'm confused. Who first described the GPL as viral? MS? RMS? Somebody else?

    1. Re:Viral license?? by Gerry+Gleason · · Score: 4, Informative

      No, the term viral dates from the earliest GPL debates, long before MS even knew it existed.

    2. Re:Viral license?? by Metrol · · Score: 4, Interesting

      Who cares who first described the GPL as "viral"? The fact of the matter is it IS viral, and was designed to be viral, regardless of whether or not you think that is a good thing.

      I know what you're trying to say, but the metaphor is lacking in a number of key points. First off, the very word "viral" brings to mind illness, disease, and a variety of other unpleasentries. This is why MS decided to describe the GPL in this way. Welcome to marketing 101.

      A virus is some foriegn invader to a system that lives off the host, and thus weakening it. Rarely is a virus invited in, as it's method for propogating is to be hidden in some other form unrecognized by the host.

      Software that exists under the GPL does not hide what it is. It can't find its way into proprietary code unless it is specifically invited into it. It is its own host, not requiring another for its survival. Certainly the code is trapped within the license once placed there, but so is proprietary licensed code. The primary difference is that one is trapped in the public domain, the other in the corporate.

      I don't have a better metaphor to contradict the whole "viral" thing. I do know that the GPL does not in any way exhibit what we would think of as viral though. Just like with proprietary software, if you want to utilize it within your own code there is a cost attached. To use Microsoft software, you'd pay a licensing fee. With the GPL you pay with providing your efforts back to the community you got it from.

      The only purpose behind calling the GPL a "viral license" is to attempt to put a negative spin on it. The term is but one salvo from the MS marketing arsenal designed to attack that which makes us strong. Allowing the term to stick to any OSS license would be suicidal from a public relations standpoint.

      --
      The line must be drawn here. This far. No further.
  14. Re:My Thoughts by qwijibrumm · · Score: 4, Funny
    We all know MS is bad and they are hard at work on Evil Master Plan v1.0
    Are you kidding, they've been artificially inflating their product numbers for years. Seriously how much of an improvement was "Evil Master Plan Me(TM)" over "Evil Master Plan 98SE(TM)"? I think they're working on "Evil Master Plan Zt(TM)" right now.

    Man, I remember when computing was easy and they only had "Hey, I Think Being A Little Evil Can Make Us Money 5.2(TM)"

    I guess it just shows, version numbers don't sell. Year numbers don't sell. But cool letters equal cash!

    --
    I wish there was some there was some way that I could be outside playing basketball, in the rain, and not get wet.
  15. MS wants even more freebies from the gov. by g4dget · · Score: 4, Interesting
    Microsoft seems to be saying that they don't like the GPL used for government sponsored research because they then can't just take that software and re-sell it. Instead, what they want is that government sponsored researchers develop enhancements to Microsoft's products under shared source agreements, enhancements that will be of no commercial value to anybody but Microsoft. Seems to me Microsoft wants an extra-sweet deal from the government.

    I'm quite open to the idea that governments should consider creating software under X11/BSD-style licenses. But I think working with software under Microsoft/Sun-style "shared source licenses" is completely unacceptable because those kinds of licenses favor a single vendor; this should not only be discouraged, it should be made illegal: no government sponsored researcher should be permitted to create software under such agreements. The GPL may not allow commercial use of software developed by researchers, but it is equitable and fair to all commercial competitors.

  16. TCP/IP Slide by jdeisenberg · · Score: 5, Insightful

    For me, the most interesting slide was the bottom half of img_0224r.jpg, (Areas of Concern) where it says: "Primary research results placed under the GPL are precluded from commercial use: TCP/IP example".

    I'm wondering if this translates to "We are concerned, because we can't charge people royalties for every packet they send." I would have loved to have heard the commentary that went with that slide.

  17. Why not $un or Net$cape as well? by mgkimsal2 · · Score: 4, Insightful

    I've always HATED the stupid "M$" text that people use when talking about Microsoft. They want to make money - good for them. HOW they go about it has proven problematic/wrong/illegal/whatever, but the motive is the same for all companies - make money.

    No one is suggesting propping up a company at the expense of another - certainly not in this thread.

    Please lose the $, or use it evenly:

    $un
    Net$cape
    $ear$
    $BC
    $pirit
    $am$ Club
    $heraton

    etc

    1. Re:Why not $un or Net$cape as well? by dvdeug · · Score: 4, Insightful

      Cancerous is a somewhat loaded term, but it most certainly is viral.

      Why is viral any less loaded than cancerous? The GPL certainly does not behave as a virus, considering it only comes in when it's invited.

  18. Microsoft and Sun are much more "viral" by g4dget · · Score: 5, Insightful
    If you look at Microsoft's and Sun's licenses for their source code, they are much worse than the GPL in terms of "infecting" you.

    You can look at the GPL and write your own proprietary implementation. But a lot of source code from companies like Microsoft and Sun software is licensed under agreements that "contaminate" you; that is, you can't develop a competing implementation because the presumption will be that you copied stuff from their source code. They also contain lots of other clauses that "infect you", like with an indefinite possibility of getting dragged into a law suit between Microsoft or Sun and a third party.