Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Microsoft Treating "Windows-Only" As Open Source

Posted by Soulskill on Sat Oct 04, 2008 12:22 PM
from the a-rose-v0.092-BETA-by-any-other-name dept.
mjasay writes "The Register is reporting that Microsoft is hosting Windows-only projects on its 'open source project hosting site,' CodePlex. Miguel de Icaza caught and criticized Microsoft for doing this with its Microsoft Extensibility Framework (MEF), licensing it under the Microsoft Limited Permissive License (Ms-LPL), which restricts use of the code to Windows. Microsoft has changed the license for MEF to an OSI-approved license, the Microsoft Public License, but it continues to host a range of other projects under the Ms-LPL. If CodePlex wasn't an 'open source project hosting site,' this wouldn't be a problem. But when Microsoft invokes the 'open source' label, it has a duty to live up to associated expectations and ensure that the code it releases on CodePlex is actually open source. If it doesn't want to do this — if it doesn't want to abide by this most basic principle of open source — then call CodePlex something else and we'll all move on."
+ -

Related Stories

[+] Your Rights Online: OSI Asks Microsoft to Change the MS-PL 169 comments
Xenographic writes "The OSI has identified two significant flaws in the Microsoft Permissive License, and is unlikely to approve it as an OSI license in its current state. Specifically, the OSI is worried about the way the MS-PL is incompatible with so many other OSI-approved licenses and how misleading that makes the term 'permissive' in the license's name. Now the ball is in Microsoft's court and they can choose to amend or withdraw it from consideration. From the article: 'The MPL is also particularly restrictive, and is uniquely incompatible with the maximum number of other open-source licenses, [president of OSI Michael Tiemann] said, noting that in its examination of license proliferation, the OSI had encouraged experimentation with license terms to encourage new ones to be written that were better than what currently existed.'"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by MindlessAutomata (1282944) on Saturday October 04 2008, @12:25PM (#25256331)

    This is most likely a tactic to try to get people to associate "open source" with Microsoft and not Linux.

    • I think mostly they'd like to dilute "Open Source" to mean any code with source code. This is important to them because it's the rights connected to Open Source that scare Microsoft (and others). If you can call it Open Source when there isn't even the right to compile the code, or to use the information you get from reading it, customers don't have a reason to ask for it any longer.

      Their publicity agencies are here on Slashdot pumping that angle every day.

      Bruce

      • by domatic (1128127) on Saturday October 04 2008, @12:34PM (#25256387)

        It is not a matter of ownership. Words have a particular meaning and this is a case of MS trying to throw its weight around to change the popular understanding of the meaning of "Open Source" to something that is favorable for them. Last time I checked, "Open Source" does NOT mean "something that is only legal to use on Windows".

        • by lastchance_000 (847415) on Saturday October 04 2008, @12:39PM (#25256411)

          Or Linux-only, or Mac-only, or Plan9-only. The point is that if someone wants to modify the code so it runs on an Atari 800, they're legally free to do so. Publishing the code, and saying, "You may do this, only, and no more", is certainly within their rights, but it ain't open.

            • by EvilRyry (1025309) on Saturday October 04 2008, @01:25PM (#25256727) Journal

              The big difference in this case is that it affects how you *use* the software.

              Many OSI approved licenses affect how you may redistribute the software, but none of them AFAIK limit how you may use or alter it.

            • by lysergic.acid (845423) on Saturday October 04 2008, @01:36PM (#25256781) Homepage

              technically you are right about what licenses are. but what open source licenses all have in common is that they aim to make the software source code the most freely available to others, thus maximizing its utility, with the minimal licensing restrictions to achieve this goal.

              Microsoft's use of "open source" not only goes against the spirit of FOSS, but also violates the basic definition of "Open Source" [wikipedia.org] used by the OSI:

              5. No Discrimination Against Persons or Groups - The license must not discriminate against any person or group of persons.

              6. No Discrimination Against Fields of Endeavor - The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

              8. License Must Not Be Specific to a Product - The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.

              9. License Must Not Restrict Other Software - The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.

              in the end, what "open source" means is defined by the community. it is what the community finds acceptable and conducive to the goals of the Open Source movement. if they decide that they are willing to accept Microsoft's definition of "open source" then the Ms-LPL can be called a genuinely open source license. however, that would require changing the current accepted definition of open source. but not only would that require arriving at a new consensus, but it would likely destroy the open source movement by undermining its original aim of fostering open collaboration and combat the increasingly restrictive IP laws and cultural attitudes.

                • Number 6, about fields of endeavor, covers restrictions on distribution with fur coats.

                  The OSD is related to what people had tried to do with licenses at the time. For example, there was Alladin Ghostscript, which prohibited its distribution on the same medium with software that wasn't freely distributable. And there was the Berkeley Spice License, for their electrical engineering software, which prohibited the use of the software by the Police of South Africa, and still did a decade after apartheid was over.

                  I was trying to define what was Free Software for Debian's social contract. FSF didn't promote a definition of Free Software at the time, although they'd published one in their newsletter a long time before. RMS even said in a personal email that he liked my definition.

                  Then 7 or 8 months after this was all written and in use by Debian, Eric Raymond brought me the news of the meeting where a bunch of people had decided to promote Free Software as Open Source, and asked me to work on that. So, I filed off the Debian references and it became the Open Source Definition, and I announced Open Source to the world, including here on Slashdot (and that announcement still survives online today). That announcement was the first real use of "Open Source" to the public.

                  Bruce

          • by vishbar (862440) on Saturday October 04 2008, @01:05PM (#25256567)

            The problem isn't that the code is built solely for Windows...there are lots of projects that are considered open source that are built for a single operating system. The issue is that the license expressly forbids developers to port the code to any other OS.

            Call it what you will, but that ain't open source.

            • by Macthorpe (960048) on Saturday October 04 2008, @01:14PM (#25256639) Journal

              A real open source license wouldn't do that

              That's your opinion. As far as I'm concerned, open source means exactly that - the source is open. People seem to be intent on tacking on a whole load of 'moral' obligations that someone has to follow to qualify to use 'open source', when nothing could be further from the truth.

              Definitely a very liberal sprinkling of "Open Source is our phrase, you can't use it" going around the comments on this article.

              • By your definition, the latest feature films are "open" as well. After all, you can look at them. You can't copy them, distribute them, compile them, or anything else.

                It's the rights that are important. You're missing that entirely.

                Bruce

                  • One of the plus points of open source as I'm led to understand is that others can review the code to increase trust in that code, many eyes and all that.

                    We need more than you think for something to be open even by your over-restrictive definition of "open". Consider that the report on the security of Sequoia voting machines has been supressed by the court [freedom-to-tinker.com]. In that case, the software was trade secret and all rights reserved. But what if it had been source code that was disclosed but still "all rights reserved"? Since that prohibits compilation and use, it would be difficult for security testers to legally do their work at all. Since it prevents derivative works and redistribution, we'd be unable to include code snippets in any report. We would be legally unable to modify the software for the purpose of testing bug fixes. And we'd be unable to distribute fixes.

                    The rights are a lot more important than you think. Even to have a kind of code that is disclosed mainly for the purpose of increasing trust, we'd have to design a license to convey significant rights, if the examiners were not to be placed at legal risk.

                    Bruce

                    • by Macthorpe (960048) on Saturday October 04 2008, @02:51PM (#25257333) Journal

                      My point was really that "open source" already conveys something far more simple than what you want people to read into it, and it's the simple definition that Microsoft are very obviously meeting.

                      Even with your more complex definition for the purposes of the OSI, the MS-LPL only fails on one count of 10, which is regarding being technology-neutral. We could further argue on how important to the issue that is but I think we'd be digressing even further from what I'm trying to say.

                    • Even with your more complex definition for the purposes of the OSI, the MS-LPL only fails on one count of 10, which is regarding being technology-neutral.

                      As if that one count of 10 wasn't important.

                      At one point or another, my main coding platform was an Apple II, Commodore Vic-20, Commodore 64, PDP-11, VAX, Sun, SGI, PC Clone, and I've had a number of secondary coding platforms, including CHAP (something Pixar made), 6809, PIC, AVR, and so on. And all of the various operating systems for those things.

                      Any code that I have been given with platform restrictions, during that entire time, for various employers, is dead code today. No users, probably can't even be built if someone could find it, and I can't use it either.

                      In contrast, essentially all of the work I've done under an Open Source license is still living and has a vibrant user community.

                      You really need to think about this rights thing more.

                      Bruce

                    • There is no affirmative fair use right in copyright law. Go look for it in the copyright title, it's not there. Fair use is a defense in copyright case law. And it has been substantially eroded, and continues to be. If we're talking about books, a number of software manuals place substantial restrictions on the use of the information in their licenses. For example, the Java manuals from Sun restrict use of the knowledge to create an incompatible implementation. There is some dispute regarding whether these things can be enforced, but not enough.
          • There was no "open source", capitals or not, regarding software until the Open Source Definition. If you look through past material, you can only find a few uses of the words together regarding software at all, with no consistent meaning.

            Open Source is what is defined by the Open Source Definition.

            A number of microsoft dweebs and/or campaigners would like to have it otherwise. But then Microsoft would like to have a lot of things. It's called corporate totalitarianism.

            Bruce

          • by mysidia (191772) on Saturday October 04 2008, @01:07PM (#25256579)

            They weren't bastardizing the concept. They were working with the community to provide a definition big companies like IBM, Sun, or Microsoft, and lawyers could understand.

            And in the past they even registered "open source" as a service mark for protection of the thriving community against dilution by people who wanted to twist the concept of open source.

            To protect against companies who want to just make the source visible without actually opening it for others to use or change without undue restrictions protective corporate lawyers would normally demand upon (things like written approval).

  • Nothing new here. (Score:3, Insightful)

    by Sir_Lewk (967686) <{sirlewk} {at} {gmail.com}> on Saturday October 04 2008, @12:26PM (#25256337)
    Honestly, I don't see anything new here. This is just yet another example of Microsoft attempting to muddy the waters. It's classical embrace and extend.
      • quickly corrected (Score:5, Informative)

        by erlehmann (1045500) on Saturday October 04 2008, @01:08PM (#25256597)

        From http://www.opensource.org [opensource.org]

        Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria: [...]

        Emphasis mine.

          • Re:Nothing new here. (Score:5, Informative)

            by Bruce Perens (3872) * <(bruce) (at) (perens.com)> on Saturday October 04 2008, @01:07PM (#25256583) Homepage Journal
            Code with source-code available but without the particular set of rights defined in the OSD is called "Disclosed Source Code". It is possible to have disclosed source code with "All Rights Reserved", such that nobody would ever have rights to compile the code. Thus, it makes sense to have a name that is specific to the rights attached, not just the fact that there is source code. That's what "open source" and "Open Source" mean. The capital letters are not significant, if it says it's open source it has to have the rights specified by the OSD.
          • Re:Nothing new here. (Score:4, Interesting)

            by Fancia (710007) on Saturday October 04 2008, @01:22PM (#25256705)

            "must"? As in, it's illegal if it doesn't?

            (honest question)

            OSI tried to register "open source" as a trademark, but didn't receive it. I don't think companies are legally bound to follow OSI's principles when describing something as "open source."

            If they're using the OSI trademark or something along those lines, which Microsoft doesn't seem to be, it's a different situation.

  • by Locutus (9039) on Saturday October 04 2008, @07:25PM (#25259683)

    come on, are people really surprised that Microsoft is not only taking MS .Net to the world of Windows-only but also making sure anyone who uses their sites/services are Windows-only partners too?

    Get real folks. With out a monopoly hold on the pre-load computer market, Microsoft would be dead meat. They know they need to make sure their customers do not have a choice to try another OS because they will not put their software on another OS. Remember, without Windows they are dead meat. Outside of one package, MS Office for Mac, they have never put their software on another OS with the intention of making a business profit from it. They put Internet Explorer on Solaris to kill off all the Win32-UNIX licensees and keep anti-trust judges from nailing them for it. When Palm had 80% marketshare and WinCE was less than 5% IBM, Sybase, and other dbase vendors released lite versions for the PalmOS. Microsoft released MS Access-lite for WindowsCE.

    Miguel is an idiot for kissing Microsoft's ass every time they expose it to him. MS .Net was created to stop Java from taking Microsoft developers over to a cross platform API and software stack plain and simple. Anything "open" about it is a trick/game/hoax/etc because they own the spec.

    Microsoft's business is to own/control all software development and make sure it is all done on Windows. This is a fact. Everything they do must first protect the Windows marketshare. This is reality. Open source is a threat to Microsoft when it runs on anything other than or along with Windows. Another fact. So cry all you want Miguel, you're an idiot for following Microsoft and playing the Pied Piper to those too naive to understand. IMO.

    LoB

    • Re:haha (Score:5, Funny)

      I don't think it is fair that you got first post, I wish I had got first post, my first post was going to be quite good. Someone (perhaps the shashdot editors should fix this). Maybe in retrospect I should have realised that an Anonymous Coward by nature would try to get first post, but I didn't, my hope was that the Anonymous Coward would change his behaviour this time so that everyone would get to read my post - but I guess the Anonymous Coward can't be trusted to do the right thing after all. Its a shame though. I really hope that from this chastisement Anonymous Coward will get message and change his spots. Irrelevant first posts are selfish and spoil things for everyone.