Slashdot Mirror


Lawyer Thinks Microsoft Can Evade GPL 3

rs232 writes with a link about a disheartening observation on the GPLv3. Unless there's something more specific in the Novell agreement that would fall within the new version of the GPL, Microsoft should have no trouble slipping free of it. Silicon.com has a piece speaking with a leading intellectual property lawyer from Australia. She says, "'I would be very surprised to see this upheld. It was a nice try on the part of (the FSF), but at this stage, I'd say it's not going to be an effective strategy. It will be tough to hold up in court.' In this case, she said, Microsoft never acted — never 'entered' into the agreement, and the terms and conditions can only apply to new actions by Microsoft, not older ones. She said: 'Their actions so far are not enough to say that they are bound.'"

266 comments

  1. A lawywer will tell you anything is possible. by cs02rm0 · · Score: 3, Informative

    For a fee

    1. Re:A lawywer will tell you anything is possible. by Anonymous Coward · · Score: 0

      I read this article a while ago. Its bullshit! Here's why. Suppose my friend and I agree not to be bound by microsofts eula. Then we buy it. We actively made an agreement before we bought. Are we bound? Of course. Now microsoft is trying to push GPLv.3 software. Are they bound? Of course! By distributing the software, they 'entered into the agreement'. The license covers terms of distribution and terms of use. Its a smoke-and-mirrors parlor trick to try and argue otherwise. The folks at M$ might argue 'we never signed the license', and they would be correct. I've never seen anyone sign a microsoft eula either. Are they bound to it? YOU BETCHA! Short answer: even if microsoft distributes GPLv.3 software, they are bound to it, even if only one program of thousands on a disk is GPLv.3, they are bound to it.

  2. Legal advice from a convict by Bastard+of+Subhumani · · Score: 0, Offtopic

    Gehickgehickgehick. Canyatelllwotitisyet?

    --
    Only three things are certain; death, taxes, and apocryphal quotations - Ben Franklin.
    1. Re:Legal advice from a convict by Anonymous Coward · · Score: 0

      Are you fucking retarded?
      Maybe the next time we here from a US lawyer we should say "Legal advice from a murdering drug-addict?" or if we hear from a German lawyer we should say "Legal advice from Nazi scum" or if we hear from a Turkish lawyer we should say 'Legal advice from an Islamic psycho?"

      You're a dipshit. %96 of the OZ population have no "convict" ancestry what-so-ever. Anyway, the only reason they were sent to OZ in the first place was that they couldn't send them to the Americas anymore.

      Fucktard.

    2. Re:Legal advice from a convict by Anonymous Coward · · Score: 0

      "Whatsoever" is one word. Now go rattle your ball and chain somehere else, preferably near deep water.

  3. Beancounters do not consult court verdicts by jkrise · · Score: 2, Interesting

    And so while Microsoft might well get away in a court battle, the market has already made up it's mind when MS made it clear they will have nothing to do with GPL3. While existing customers might not implicate MS into GPL3 obligations; they may not have ANY future customers. And so, it is still a win for the FSF, without any need to go in to court.

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Beancounters do not consult court verdicts by jellomizer · · Score: 1, Interesting

      Unless Customers generally don't like GPL 3. Like a lot of people myself included GPL 3 is moving less away from general freedom to more of a dictatorship control where in order to join the FSF club you will need to follow more and more demands. The GPL 3 is a move away from Freedom and a step closer to Anti-Capitalism.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Beancounters do not consult court verdicts by Simon80 · · Score: 1

      Ignoring that what you just said is barely coherent, if you look at the motivation behind every new part of the GPL v3, it has to do with ensuring that software users get the four freedoms that define free software, and nothing to do with giving the FSF control over anything. Even the parts of it specifically designed to prevent deals like the MS/Novell one are there to protect software from becoming free for only _some_ people, or from getting treated as such by people who spread FUD.

    3. Re:Beancounters do not consult court verdicts by gowen · · Score: 1

      Software Freedom (in the FSF sense) has always been anti-capitalist. It's central tenet is sharing. The central tenet of capitalism is not sharing. Now you can like that or you can dislike it (and I couldn't care less), but don't pretend this is something new.

      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    4. Re:Beancounters do not consult court verdicts by alex_ndc · · Score: 1

      Unless Customers generally don't like GPL 3. The GPL is a copyright license that doesn't restrict usage of the software in any way.
      If by "customers" you mean end-users, why should they have anything against it ?

      The license affects you only if you are a distributor of GPL software.

      In GPL ver.2 there's an implicit patent license to make sure that the company which provided you with a copy won't sue you, or the people you redistribute copies to.
      GPL ver.3 extends that to not allow deals like the one by Microsoft-Novell to happen ... and it is in the same exact spirit ... if you want to protect customers, you'd better protect all of them or none.

      The other thing that was added was the Tivoization clause ... which only applies for hardware built for end-users, not businesses, btw.

      Some people argue that a copyright license shouldn't dictate how hardware is built.
      But other people, including myself, argue that the difference between hardware and software is blurry and that nothing should restrict end-users freedoms to modify that GPL software.

      The GPL 3 is a move away from Freedom and a step closer to Anti-Capitalism. Please define "freedom".
      Is Freedom the right to kill your neighbor ?

      "Anti-Capitalism" ? Puh-lease ... its as capitalist as it gets ... want to use GPL software, you must pay the price of giving your customers the same freedoms that your received.
      Otherwise don't use it ... nobody is forcing you otherwise.
    5. Re:Beancounters do not consult court verdicts by sumdumass · · Score: 1

      I would agree. I am one of those people who don't like the GPLv3 too. Although I have a few more reasons then you state.

      There are some serious problems left in the GPLv3 that will hamper this idea of people wanting to use free software over proprietary. Maybe in a fantasy world, but up till now, real life has shown more support for proprietary software then GPLed works.

    6. Re:Beancounters do not consult court verdicts by doom · · Score: 1

      gowen wrote:

      Software Freedom (in the FSF sense) has always been anti-capitalist. It's central tenet is sharing. The central tenet of capitalism is not sharing. Now you can like that or you can dislike it (and I couldn't care less), but don't pretend this is something new.

      Will they kick you out of the United States if you share something?

      If Company A cuts a deal with Company B to split the costs on something and share the resource, does that mean they've ceased to be capitalists?

      If I share the Xerox machine with the guys in the next office, have I become a dirty communist?

      Really: The GPL was carefully designed to be orthogonal to "capitalism". It does not prohibit you from being in business, or from making money... it does prohibit some things you're allowed to do with someone else's code.

      And it sure as hell is something new under the sun, or people with 5-digit slashids wouldn't need to have the basics recited to them over-and-over again.

    7. Re:Beancounters do not consult court verdicts by gowen · · Score: 1

      If Company A cuts a deal with Company B to split the costs on something and share the resource, does that mean they've ceased to be capitalists?
      That's not sharing. That's commercial co-operation. Sharing is when someone gives something to someone without getting anything in return. Everything else is just commerce.

      And no, you don't get kicked out of the US for not being a capitalist, no-one ever said you would. There are plenty of altruistic charities and non-profits to prove that. Same as you won't get kicked out of Sweden for not being on the centre-left.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    8. Re:Beancounters do not consult court verdicts by yada21 · · Score: 1

      Sharing is when someone gives something to someone without getting anything in return.
      Isn't that called giving?
      --
      I will have a sig when the market demands it.
    9. Re:Beancounters do not consult court verdicts by Ohreally_factor · · Score: 1

      Some people argue that a copyright license shouldn't dictate how hardware is built.
      But other people, including myself, argue that the difference between hardware and software is blurry and that nothing should restrict end-users freedoms to modify that GPL software. GPL 3's anti-hardware provision wasn't necessary for this. Tivo always made the source code available, so you could modify it to your heart's content. You just couldn't easily reinstall your modified code onto the device. There was nothing to stop you from hacking the hardware, however. What GPL 3 does do is protect the freedom of users who are too lazy to figure out how to hack their hardware and want the hardware maker to provide them with an easy way, even if doing so would put the hardware maker into a legal or contractual bind that would drive it out of business.

      So, the 99% of users that couldn't care less that the hardware was easily hackable have lost a bit of freedom in favor of the 1%'s convenience. The 1%'s freedom wasn't at stake. Merely their convenience.

      There is a means of rejecting Tivo hardware under the GPL 2. It's called not buying it, and buying hardware that supports installing user modified software, like the neuros. Or even better, developing software for the neuros, so that it becomes the better choice for the great unwashed masses.
      --
      It's not offtopic, dumbass. It's orthogonal.
    10. Re:Beancounters do not consult court verdicts by alex_ndc · · Score: 1

      What GPL 3 does do is protect the freedom of users who are too lazy to figure out how to hack their hardware and want the hardware maker to provide them with an easy way ... If we are talking about DRM and Trusted Computing, and we are ;) , under the Digital Millennium Copyright Act it is illegal to circumvent access control to copyrighted works, even if there is no infringement of copyright itself.

      That means it is illegal to hack Tivo to allow new versions of the software in it ... and besides, you'd make a mistake if you made a distinction between hardware and software.

      ... even if doing so would put the hardware maker into a legal or contractual bind that would drive it out of business. That hardware maker should have thought about the consequences of using other people's work.
      Tivo should have respected the spirit of the GPL, and should have given its customers the same freedoms Tivo received.

      Here's a prediction ... what if in the future all hardware will be tivoized, including PCs ?
      How are you going to vote with your wallet then.

      Here's another awkward situation ... you're the developer of a useful GPL application and upon buying a Tivo you notice that your application is used by it. But surprise, you can't upgrade to a newer version that has a lot of bug fixes, even if you're the developer of that application and even if the Tivo is your property.

      If hardware makers want more freedom, there's always *BSD.
    11. Re:Beancounters do not consult court verdicts by gowen · · Score: 1

      Yes, yes it is. Unlike computer programming languages, human languages frequently have many words for the same concept.

      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    12. Re:Beancounters do not consult court verdicts by RightSaidFred99 · · Score: 1

      Haha, yeah - that's going to happen. Delusions of grandeur much?

    13. Re:Beancounters do not consult court verdicts by grahammm · · Score: 1

      If we are talking about DRM and Trusted Computing, and we are ;) , under the Digital Millennium Copyright Act it is illegal to circumvent access control to copyrighted works, even if there is no infringement of copyright itself.

      That means it is illegal to hack Tivo to allow new versions of the software in it ... and besides, you'd make a mistake if you made a distinction between hardware and software. I am neither a lawyer nor in the USA, but does the DMCA not state you may not circumvent without the permission of the copyright holder? So is GPL3 not in effect stating that as a condition of licensing the software under GPL-3 the copyright owner MUST give permission (or provide a mechanism) for anyone to circumvent, for the purpose of installing and running a modified version of the software licensed under GPL-3, any access control 'protecting' the software licensed under GPL-3?

    14. Re:Beancounters do not consult court verdicts by Ohreally_factor · · Score: 1

      Tivo should have respected the spirit of the GPL, and should have given its customers the same freedoms Tivo received. I keep hearing about this nebulous "Spirit of the GPL", which in the Tivo case, seems to be nothing more than the FSF intruding where it has no business. The "intent" of the GPL 2 is explicit in the language of the GPL 2, and in the case of Linux, matches the intent of developers. To make claims that Tivo is somehow evading the intent of the license, unethically and in bad faith, is to show total disrespect for the developers. You're in effect saying that you or the FSF know what's best for the developers, as if they are not adults capable of making decisions for themselves.

      The war on Tivo is a made up conflict being used by the FSF to further its agenda to control software. When they control the software thru their licensing (I can't wait to see what's in GPL 4, 5, and 6), they'll control the user. And if they think they know what's best for the developer, you can be damn sure they think they know what's best for the user.

      Bottom line is that Tivo did give its users the same rights it received under the GPL 2. It complied completely with the GPL 2. Suggesting otherwise is dishonest.

      If we are talking about DRM and Trusted Computing, and we are ;) , under the Digital Millennium Copyright Act it is illegal to circumvent access control to copyrighted works, even if there is no infringement of copyright itself.

      That means it is illegal to hack Tivo to allow new versions of the software in it ... and besides, you'd make a mistake if you made a distinction between hardware and software.


      If you're worried about the law, change the law. However, there is an active culture of Tivo hardware hackers that don't seem to let this stop them. And again, there are devices such as the neuros that have no such potential encumbrances.

      Here's a prediction ... what if in the future all hardware will be tivoized, including PCs ?
      How are you going to vote with your wallet then. This is a FSF scare tactic that just seems silly when you examine it rationally. Is this really the reason for the anti-DRM provisions? It's laughable.
      --
      It's not offtopic, dumbass. It's orthogonal.
    15. Re:Beancounters do not consult court verdicts by alex_ndc · · Score: 1

      I keep hearing about this nebulous "Spirit of the GPL", which in the Tivo case, seems to be nothing more than the FSF intruding where it has no business. The GPL ver.2 was written by the FSF, so I think they pretty much have a business here.

      The intent of the GPL ver.2 is to give end-users the 4 freedoms ... to use for any purpose, to redistribute, to modify, to redistribute changes.
      In Tivo's case, the freedom to modify the software is taken away.

      You may say that the source code is available ... but what's the point if I can't run it on my Tivo ?
      Should I invent my own Tivo clone just to run the modifications I make ?

      The "intent" of the GPL 2 is explicit in the language of the GPL 2, and in the case of Linux, matches the intent of developers. And nobody is forcing the Linux developers to switch.
      In fact, nobody is forcing you or anybody else to use GPL ver. 3.
      There are other licenses out there more suited for the various types of products out there ... MIT, BSD, MPL, CDDL, ASF ... all licenses approved by FSF and OSI.

      GPL ver.3 respects the 4 freedoms that Free Software licenses must respect, and it is also compatible with the OSI definition of open source and with the Debian Free Software Guidelines.
      Nobody is complaining as much about the Microsoft's Shared Source initiative ... which makes me think ... how many FSF opponents are not corporate shills ?

      This is a FSF scare tactic that just seems silly when you examine it rationally. Hardware functionality is replaced by software all the time, and vice-versa ... that's why it is not silly.
      The Trusted Computing initiative is public, is transparent and it's for real.

      And why are you so angry about it ?
      You don't have to agree with it you know ... the GPL license explicitly states that, as long as you are not redistributing ;)
    16. Re:Beancounters do not consult court verdicts by doom · · Score: 1

      Yes, yes it is. Unlike computer programming languages, human languages frequently have many words for the same concept.

      And if we don't use the ones you specify, we're cheating.

    17. Re:Beancounters do not consult court verdicts by Ohreally_factor · · Score: 1

      I keep hearing about this nebulous "Spirit of the GPL", which in the Tivo case, seems to be nothing more than the FSF intruding where it has no business.

      The GPL ver.2 was written by the FSF, so I think they pretty much have a business here.

      The intent of the GPL ver.2 is to give end-users the 4 freedoms ... to use for any purpose, to redistribute, to modify, to redistribute changes.
      In Tivo's case, the freedom to modify the software is taken away.

      You may say that the source code is available ... but what's the point if I can't run it on my Tivo ?
      Should I invent my own Tivo clone just to run the modifications I make ? I'm well aware that the FSF wrote the GPL 2. That doesn't give them rights to interfere between a licensor and a licensee. Your contention that the FSF has any business interfering is FALSE.

      You are changing the language of the GPL 2 by appending "end" to users. The actual text of the GPL 2 reads: the GNU General Public
      License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.
      You (and the FSF) are reframing the debate by changing the language and covering up this maneuver with "spirit of the GPL" hand waving. If you want to be honest, you need to change the language to read some users and not all users.

      Again, your ability to modify the software is fully present. To represent otherwise repeatedly is dishonest. Repetition of a falsehood does not make it true.

      You may say that the source code is available ... but what's the point if I can't run it on my Tivo ?
      Should I invent my own Tivo clone just to run the modifications I make ?

      I don't say it's available. It is available. Again, you are manipulating the debate to cast fear, uncertainty, and doubt on Tivo, rather than forthrightly framing your objections.

      Designing and developing your own hardware would be an admirable solution to the question of what to do with modified Tivo source code. You could even create an open source design of your own, which would further technological development in general. Instead, you seem to be arguing that if I hardware designer wants to use open source software, then he should be forced to design hardware to your liking. There is already a mechanism to "force" a manufacturer to design hardware that suits the user. That mechanism is called the free market.

      Perhaps you don't trust the concept of the free market. Perhaps you don't trust users ability to choose what is best for themselves. It would then make sense that you would wish to protect the user from himself. I don't know about you, but I love the idea of the FSF protecting me from myself. I'll happily give up my freedoms to the safekeeping of the FSF. We can trust them because they say they're defending my freedom.

      nobody is forcing the Linux developers to switch

      Well, they're certainly putting a lot of pressure on the developers to switch, including trolling the LKML, engaging in character assassination, making factual misrepresentations about others, shifting definitions to suit today's agenda, etc.

      GPL ver.3 respects the 4 freedoms that Free Software licenses must respect

      I disagree. GPL 3 carves away some of Freedom 0 that was present in GPL 2, as I've stated multiple times.

      Nobody is complaining as much about the Microsoft's Shared Source initiative ... which makes me think ... how many FSF opponents are not corporate shills ?

      Please don't try this tactic with me. Do you really believe that anyone who disagrees with the FSF is a corporate shill? And you wonder why I get angry? I get angered by intellectual dishonesty. I don't like it when someone pees on my leg and then tells me it's raining. I'll get to the o

      --
      It's not offtopic, dumbass. It's orthogonal.
  4. Uhhh... so? by Anonymous Coward · · Score: 3, Informative

    Pretty sure I've read that the FSFs intention was to address future deals, not this specific existing one (though some have tried to think of ways it could apply anyhow. You know, non-expiring vouchers and what not)

    1. Re:Uhhh... so? by physicsnick · · Score: 4, Insightful

      Exactly. The point was not to punish Novell and MS, but to stop it from happening again. It would be very chilling for the spread of the GPLv3 if the FSF set a precedent of retroactively damaging companies who fully abide by the letter of the GPL, but do things the FSF considers to be immoral.

    2. Re:Uhhh... so? by sumdumass · · Score: 1

      No, the point was to punish novell. This is clear with the public statements made at the time it was happening by RMS and people around him including Perrens and such. There was even a discussion at the FSF involved in letting the community decide whether to exclude Novell or not by changing the effective dates.

      And it is interesting that you think "It would be very chilling for the spread of the GPLv3 if the FSF set a precedent of retroactively damaging companies who fully abide by the letter of the GPL, but do things the FSF considers to be immoral."

      The entire anti-Tivo clauses was motivated specifically by this.

  5. This may betray some sort of ignorance on my part by weak* · · Score: 1

    but I really don't understand why we're all so hung up on the GPL3 vs. Microsoft thing. For now and in the near future, anything that happens of any significance in the desktop or corporate IT world will have to suffer MS putting their nose in. It's just a fact of life. Will there always be companies selling linux distros that will be willing to sleep with the devil (speaking very figuratively; please don't flame me)? Yeah, probably, and I don't see anything wrong with it--they are within the rules of business, rules for which we are responsible. If you believe in the linux cause, you have to admit that it does more good for the OS and its philosophy to spend your time contributing to linux (vis-a-vis cash, development, or intelligent discourse) than to whine about the bully who wants his cut.

    --
    The Schwartz space ain't from Spaceballs.
  6. Car Analogy by An+Anonymous+Coward · · Score: 5, Funny

    She said: "An easy analogy is a car park with a sign that says you are bound to a given contract if you enter into that car park. Anybody can enter, but you have to accept the terms, and the signal of you accepting those terms is when you enter. You have to do something positive to accept the terms - you have to act."
    That lawyer obviously reads Slashdot, she went straight for the largely irrelevant car analogy.
    1. Re:Car Analogy by noidentity · · Score: 1

      Agreed. What's the point of an analogy if you can just explain the actual situation directly? It's not like "The law says that you may not distribute without license from author. Author gives you a license. If you violate license, you've given up your only means of legal distribution." It doesn't take a quantum mechanic to understand that! (rocket scientists are outdated)

    2. Re:Car Analogy by aichpvee · · Score: 1

      Well it's sort of complicated to explain. Perhaps I have a good car analogy to demonstrate why just explaining something is too difficult...

      --
      The Farewell Tour II
    3. Re:Car Analogy by sumdumass · · Score: 1

      Well, this situation isn't like that at all. MS isn't directly distributing anything or doing anything that they would need a copyright license to do. They are conveying which is a new term in the PGLv3 that includes attempting to distribute or whatever. The problem is, you would have to accept that portion of the license in order to have it cover you. Otherwise, you aren't bound by it outside what copyright law would require. MS giving support for a third party software interacting with their doesn't need copyright permissions and them controling access to servers hosted and provided by another entity entirely doesn't violate any copyright. It might violate the GPLv3 license terms but MS hasn't done anything to accept those terms, even if they continue to offer access to Novells servers or support the products being used together with their software.

      Now, with MS controlling the keys to Novell's servers for some of Novell's users, and those servers are giving updates and which are controlled by Novell (not MS), MS just isn't distributing anything. They haven't subjected themselves to anything Novell does with GPLv3 software. Further more, Novell could simply keep the stuff separated and it would never touch Ms at all, In spirit or fact. There is also nothing stopping Novell from excluding GPLv3 software to products covered under the MS deal. And we all know that you cannot get GPLv3 covered updated to GPLv2 products.

    4. Re:Car Analogy by jZnat · · Score: 1

      BitTorrent sites don't directly distribute copyrighted material, yet for some reason they're still committing copyright infringement...

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    5. Re:Car Analogy by jbengt · · Score: 1

      The term "distribution" used in the GPL2 is a US law term of art. There is a very good chance that the deal Micrsoft made with Novell makes them a distributor subject to the terms of the GPL2, at least in the US. If so, Microsoft may have already waived their right to sue Gnu/Linux users for patent infringement. Don't expect Microsoft to test this in court, FUD is more valuable than the chance of suing free software users over patents that may or may not be valid.

    6. Re:Car Analogy by sumdumass · · Score: 1

      Umm not really. They are only involved in copyright infringement because someone else is which is different then copyright infringement but under the same laws as copyright infringement. The reason they are illegal in some cases is only because they are helping you break a law.

      So to consider MS subject to the copyright of a third party when something is used by another third party, there would have to be a primary infringement for the secondary infringement to happen. But, this doesn't mean they are subject to the license requirements of whatever is being legally distributed. They are two separate acts. Novell would have to infringe on the copyright and then MS would have to help you get to Novell's site in order for them to be subjected to that infringement.

    7. Re:Car Analogy by sumdumass · · Score: 1

      I don't think this would be the case at all. Book store owners aren't liable or obligated to conditions to the copyright of the books they sell unless the publisher conveys that to them before offering the book. And this would be especially the case if it is a used book like the GPL covered work would be.

      This entire "they might be covered" argument is thin at best. It would take a very liberal and probably unique interpretation of the facts and the law. But what isn't thin is the amount of FUD that MS can generate around this. And it isn't going to be good. I expect to see a patent case against a user who cannot or will not be able to defend themselves after the majority of GPLed software goes GPLv3. I also see MS making a deal that lets them off with a warning but in turn spreads a lot more FUD.

      Now I also see MS using the GPLv3 license against itself. I can see MS putting an agreement with anything they sell that makes everyone using their products a little Novell and the GPLv3 stopping them from contributing to GPLv3 projects or distributing GPLv3 covered works. This might be fine that every company who buys a MS product cannot contribute to GPLv3 covered works by this also keeps everything stale and hacker oriented. The GPLv3 just doesn't do what it attempts to do, it is poorly worded in a lot of areas and just like your MS is already subject, you have to stretch everything to make it work. You can live the lie, welcome the FUD, you can do a lot of things, but you cannot pin MS to the terms of the GPLv3 unless it does something on it's own to be subjected to it.

    8. Re:Car Analogy by jbengt · · Score: 1

      "Book store owners aren't liable or obligated to conditions to the copyright of the books they sell unless the publisher conveys that to them before offering the book."

      Book stores are obligated by the copyrights of the books they sell, but book stores don't make copies. A book store buys a physical copy of the book, and the doctrine of first sale gives them the right to do whatever they want with those phyisical copies (unless they contracted otherwise). Also, books bought by or sold at a book store don't typically come with EULAs. A more apt analogy would be an e-book that requires a copy to be made in order to distribute it.

      I do, though, agree with the points you make about FUD in your post.

    9. Re:Car Analogy by obeythefist · · Score: 1

      Oh? An action like, say, redistributing GPL protected software (with very valuable indemnity vouchers)?

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
  7. Microsoft didn't enter into an agreement... by Anonymous Coward · · Score: 1, Insightful

    but the Linux distributors who have an agreement with Microsoft must abide by the GPLv3.

  8. A legal arms race? by Statecraftsman · · Score: 1

    Seems to me this is a lot like the software security situation. Virus makers make a virus. It gets fingerprinted and blocked. The virus maker evolves the virus around the AV software and the game continues indefinitely.

    Since the legal code is really just like software for running courts, the same sort of evolution will continue indefinitely between free software and proprietary software vendors. What happens in this situation is the lawyers will profit greatly.

    The most effective tool in this battle is publicity. Get the word out about free software and why people should care that the software they run is free. An event is coming up for this purpose...software freedom day. Why not participate? Join or start a team at http://softwarefreedomday.org/

  9. what am I missing here? by Anonymous Coward · · Score: 0

    This lawyer just seems to be restating what was already known to anyone who's actually been following the GPLv3 story - that the new patent clause isn't retroactive, it's only supposed to prevent future deals like the one between MS and Novell.

    1. Re:what am I missing here? by jedidiah · · Score: 1

      The "deal" isn't what's relevant. The fact that Microsoft may distribute FSF "property" is. This distribution would come as a reult of them entering into an agreement with someone that creates derivatives of FSF "property". Every time Microsoft chooses to distribute (or indirectly distribute or whatever) an FSF derivative, that is a itself a new act that can trigger new obligations. The fact that Microsoft was under contract to do so really has nothing to do with it.

      The real question is one of wheteher or not what Microsoft is/has been doing can be construed as distribution under the copyright act. The related contract is is just a side show and a red herring.

      Microsoft's option is pretty simple really: break it's contract with Novell. In the grand scheme of Microsoft shenanigans, it's not such a big thing for them.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  10. Did any of you actually believe they would be ? by jfclavette · · Score: 4, Insightful

    Please. It would be a horrible, horrible legal precedent for a party to be bound by a license which was changed after the agreement, even if there's the 'or any later version' bit in the text of said license. I mean, could the FSF just add "The blood of their first born child should also be splattered over a paper copy of the source code." ?

    1. Re:Did any of you actually believe they would be ? by tokul · · Score: 1

      Please. It would be a horrible, horrible legal precedent for a party to be bound by a license which was changed after the agreement, even if there's the 'or any later version' bit in the text of said license. I mean, could the FSF just add "The blood of their first born child should also be splattered over a paper copy of the source code." ?

      GPL v.2 or later. If you don't like "later", you still have "v.2". If "later" does not exists, you usually accept versions that actually exists.

      Some software does not use "later" clauses. It is just GPL v.2.

      Software authors are not bound to own license terms. They own the software and can use it under other license.

      If authors don't like GPL v.4 and have "GPL v.2 or later" or "GPL v.3 or later", they can relicense to GPL v.2 or GPL v.3.

    2. Re:Did any of you actually believe they would be ? by neomunk · · Score: 1

      Oh, no. See, you're forgetting something.... Many of you are actually...

      The GPLv2 has a clause in it (a clause AGREED to apparently) that lets the author upgrade the license at will to a greater version of the GPL, like, say, some GPLv3 that might come along some day.

      It's in the license they agreed to, there's nothing 'retroactive' about this switch to GPLv3, it's stated right in the text, this isn't some inference from some archaic legal concept.

      They are UNDENIABLY bound to the GPLv2, even the part that binds them to the GPLv3 if the author so chooses.

    3. Re:Did any of you actually believe they would be ? by sir99 · · Score: 1

      No. The recommended license notice for GPL2 is in part:

      "This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version."

      The "your option" text means the receiver of the software chooses which license to abide by, not the author(s).

      --
      The ocean parts and the meteors come down
      Laid out in amber, baby.
    4. Re:Did any of you actually believe they would be ? by slashqwerty · · Score: 2, Informative
      Microsoft entered into a contract with Novell. They allowed Novell to distribute software that utilizes Microsoft patents and to do so with software licensed under the GPL. This included software licensed under GPLv2 or any later version. Microsoft had already had access to draft versions of GPLv3 which clearly had patent restrictions on it. They were well aware of what GPLv3 had in store.

      The Microsoft-Novell contract has not been made public so I don't know exactly what it says. However, Eben Moglan (lawyer and one of the key architects of the GPL) has read it and he says Microsoft is bound by GPLv3.

      Perhaps Australian law differs on some details but in the United States it looks like Microsoft has granted the Free Software community the rights to utilize Microsoft patents in GPLv3 code.

    5. Re:Did any of you actually believe they would be ? by sumdumass · · Score: 1

      owever, Eben Moglan (lawyer and one of the key architects of the GPL) has read it and he says Microsoft is bound by GPLv3.
      I'm not sure I would put all that much stock into what he says. Besides the fact that he is biased and pushing a particular point of view, you can see some of his work in the GPLv3 and frankly it is sketchy at best.

      The GPLv3 license doesn't do what ti claims to do except in a very limited set if circumstances. In most cases, it doesn't do much more then the GPLv2 did yet it attempts to be portrayed as if it does more then it can. This is both scary and plainly careless. The Anti Tivo parts don't actually stop Tivo, expressly makes an exception if the product's intended audience is commercial or business oriented, leaves loop holes open that will forbid people from distributing GPLv3 covered works when some unrelated third party software vendor includes language in their software license that creates a mini-novel deal (can we say MS anyone).

      And probably worse of all, this all inclusive patent clause places liability on people who contribute code that later gets patented by unrelated entities and which was the same problem as the GPLv2 covered works. I'm sure he would have had to seen these problems, I can see them and I don't understand why they weren't fixed outside incompetence. If this is an example of his work, Then I wouldn't take anything he says for the undeniable truth. It might be a good intended opinion but it doesn't look to be a competent one.
    6. Re:Did any of you actually believe they would be ? by mce · · Score: 2, Insightful

      Sorry, but you need to go back to law school (or to reading comprehension class). They are bound to v2, but v2 does not at all imply v3. If they don't like v3, they just keep using v2. If a package author changes his or her distribution license to v3 (or later), this does not affect copies previousy distributed under other licneses in any way. Not even if there is not a single other change in the package.

    7. Re:Did any of you actually believe they would be ? by Dan+Ost · · Score: 1

      I think you've got the right idea, but I wanted to make it clearer.

      The entity that distributes the software gets to choose which license uses to distribute under.

      The recipient doesn't have to abide by anything unless they decide to distribute the software to someone else. In that case, they get to choose what license to distribute under (and their decision is independent of the decision made by the entity that gave them the software).

      --

      *sigh* back to work...
    8. Re:Did any of you actually believe they would be ? by sir99 · · Score: 1

      I agree, that's a more accurate summary.

      --
      The ocean parts and the meteors come down
      Laid out in amber, baby.
    9. Re:Did any of you actually believe they would be ? by kgp · · Score: 2, Insightful

      Please keep up at the back.

      The license will apply to GPL v3 licensed components of (say) Linux (like the GNU utils or tools) that will be caused to be conveyed by Microsoft because they issued these coupons that don't have a expiry date. However that gives people like Novell the choice of either forking and duplicating a lot of work on keeping the GPL v2 bugfixed and working. Or distributing the newer GPL v3 components that everyone else is using.

      It doesn't apply to current GPL v2 software.

      The GPL v3 distribution license will apply to distributed and MSFT will be dragged into this because they are paying someone else to distrbute the bits. Eben Moglen and his collegues are not idiots (strangely enough)

    10. Re:Did any of you actually believe they would be ? by neomunk · · Score: 1

      Yes, that's right, except that I thought that once it was changed in the backchannels BEHIND you that you were stuck with the version they applied or a later one, but you couldn't revert to an older version.

    11. Re:Did any of you actually believe they would be ? by neomunk · · Score: 1

      right, but any and all further versions (and all new code therein) are bound by the NEW license, right? So no updates without a license update, right? Or am I mistaken...

      I think I might be wrong in my assumption about MS's problem here. I know that GPL2 code doesn't automagically turn into GPL3 code until it's redistributed as such, I though the problem was with new GPL3 code being implemented, like in package updates.

    12. Re:Did any of you actually believe they would be ? by Anonymous Coward · · Score: 0

      Microsoft sold something they did not own. Copyleft is not public domain. The owners of what they sold have placed a legal condition on the distribution of their copyleft copyrighted property that Microsoft rejects. Microsoft therefore says that they will not fullfill the obligations of their sale. But Novell says they will honor it anyway; accepting the new legal conditions. Sham or not? Only a court case can tell.

    13. Re:Did any of you actually believe they would be ? by ignavus · · Score: 1

      Rubbish.

      Let me you give an example without either cars or software.

      I own a block of land with a view. I put up a notice: "anyone can picnic on this land without paying a fee provided they wear a pink raincoat the whole time". I rather like the idea of little groups of pink-clad picnickers on my land...

      A bus company decides to sell tickets (including advance tickets) to people to be driven to my land and issued with tiny pink raincoats that they wear as a lapel badge, while they picnic and admire the wonderful view. The bus company figures that they are keeping my licence terms, and at the same time they don't have to ask their customers to wear a full size pink raincoat (which they think will turn off many prospective customers for some reason...) They promise their customers a picnic with my view, and that they will provide all necessary equipment for the picnic (food, umbrellas, rugs, etc).

      Now I, meanwhile, notice that there are hordes of picnickers on my land apparently without any pink raincoats. I investigate, and find that they are all wearing tiny lapel-badge-size pink raincoats. This contravenes my original desire to see picnickers in full sized pink raincoats. So I immediately change my sign: "anyone can picnic on this land provided they wear a full-size pink raincoat the whole time". Naturally, I see a lawyer who alters this to reflect my precise wishes in water-tight terms (pun ... oh, who cares).

      Now what does the bus company do with all the advance tickets they have sold? I have no obligation to the bus company. They either follow my licence or stay off my land. But they have an obligation to their paid-up customers. They have to issue full-size raincoats to their customers if they are to fulfil their contract of a picnic with a view from my land.

      See. I *can* change the conditions on my licence. It is my licence, and I owe the bus company nothing. It is their problem.

      --
      I am anarch of all I survey.
    14. Re:Did any of you actually believe they would be ? by ozphx · · Score: 2, Funny

      too long didnt read. buses are cars too.

      actually i did read, and you are correct.

      Microsoft is like the the supplier of the little pink lapel badges. After you change your license all the people on Slashcoat are posting around saying "HAHA! Now Microsoft has to give out full sized raincoats! PWNZORED!"

      Bullshit. The bus company (Novell) is fucked. Balls in their court.

      --
      3laws: No freebies, no backsies, GTFO.
    15. Re:Did any of you actually believe they would be ? by Louis+Guerin · · Score: 1

      `Sumdumass' on slashdot claiming that the Professor of Law and Legal History at Colombia University is `incompetent' when it comes to drafting legislation in the field of law he is largely responsible for founding.

      Mod funny.

      L

  11. Courts will reject ambush tactics by Courageous · · Score: 2, Insightful

    I find the whole "Look at all these clever circumstances in our new GPL3 situation that means that we've fucked M$ good an proper" just to be amusing. The Courts uniformly reject these sorts of attempts to ambush someone by contract into unintended consequences. Will never be upheld. The idea fails on not just one but many doctrines of contract interpretation. You can forget it.

    C//

    1. Re:Courts will reject ambush tactics by Anonymous Coward · · Score: 0
      1. The GPL is not a contract
      2. Microsoft attempted to ambush the GPL


      Laugh harder!
    2. Re:Courts will reject ambush tactics by Anonymous Coward · · Score: 0

      The point of GPLv3 was never to fuck MS over, it was actually to avoid the situation with Tivo. It's not like MS can change Linux, Linux is developed by the community and used by the community, MS isn't involved anywhere. There is nothing proprietary in Linux. The only area affected by MS is compatibility between Linux and MS products... and if you're only using OSS or non-proprietary software than there is no problem.

  12. Good try? by Trillan · · Score: 1

    Most slashdot readers would agree that evil lawyering is... well, evil. It's bad to get people bound to something they didn't actually agree to. Frequently we hear about scummy cellphone or cable operators pulling something like this.

    But when the FSF tries it, we moan. It's even "a nice try." Because, you know, it's the FSF and it's Microsoft. The particular situation doesn't matter as much as the companies involved. Situational ethics.

    Instead of bemoaning this, we should be cheering. I expect the FSF itself has little problem with this, since the evil lawyering was intended to prevent future deals, not retroactively change existing ones. Poisoning a well doesn't mean hunting down everyone who's drunk from it and shooting them.

    (For extra points, guess what the EFF's response would be.)

    1. Re:Good try? by WalksOnDirt · · Score: 1

      I agree that GPLv3 applying to Microsoft's past actions is a perverse legal theory, and from what I've seen I think the majority /. posters do as well. Where this has a lot of support is Groklaw, where PJ herself is the chief cheerleader. People there with arguments similar to the ones in the article are labeled as MS shills.

      The power of wishful thinking is stronger than I ever imagined.

      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    2. Re:Good try? by NorQue · · Score: 1

      Why would the GPL apply to *any* of Microsofts actions? As long as they don't use GPL'd code everything is fine and dandy, isn't it? And why would MS want to use code released under GPL, anyways?

    3. Re:Good try? by mrchaotica · · Score: 2, Insightful

      And why would MS want to use code released under GPL, anyways?
      • Because MS is obligated to by the agreement with Novell.
      • Because MS would like people to use the version it controls, instead of some hippie distro like Ubuntu.
      • Because MS would like to surreptitiously insert patented algorithms into GPL'd code, in hopes of extracting license fees (or better yet, preventing use of the code altogether, since developers could no longer legally share it with each other) while still being able to claim to ignorant PHBs that it "supports open source"
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    4. Re:Good try? by professionalfurryele · · Score: 1

      I really don't get this position of yours. The FSF hasn't done anything to Microsoft. Novell has. Microsoft entered into a deal with Novell which in light of recent license changes is clearly unfair. Microsoft can renegotiate the deal with Novell.
      The deal with Novell was that Microsoft would distribute and indemnify Novells customers in return for cash + a other less relevant terms. Now the contract effectively stipulates that Microsoft must give away licenses to their patents. The Novell-Microsoft deal is therefore now unfair and the consequences of the deal disproportionate. Microsoft has three options:
      1. Stick with the (obviously unfair and would never now hold in arbitration) deal and give out the patent licenses.
      2. Renegotiate the deal.
      3. Welch on the deal entirely and take the resulting legal consequences.
      The FSF has nothing to do with any of this because Microsoft has not entered into any agreement with the FSF save GPL 2. If the distribute software under GPL 3 then they enter into a new deal with the FSF. Both of these deals are seperate from the Novell deal.
      That is why it is different from your examples. The code that is GPL 2 is still GPL 2. It is not like a cable company changing the rules at the drop of a hat because you are free to still play by the old rules if you want to. You just have to maintain the code yourself.

    5. Re:Good try? by Trillan · · Score: 1

      Yes, I think I allowed the submitter's spin on the story to color my perception of other peoples' reactions.

    6. Re:Good try? by NorQue · · Score: 1

      Excuse me, but I still don't understand the issue. When MS releases code under the GPL v3 it is pretty much *bound* to the license text as it stands there. When it's patented and they have the rights, who cares, now it's free. Doesn't have anything to do with Novell. What does Novell have to do with MS using the GPL v3?

    7. Re:Good try? by sumdumass · · Score: 1

      When did MS ever use the GPLv2 or v3?

      We have a group of people acting like this has already happened, when and where has it happened? And according to Novell, it's deal was to make new products to be used with GPLed products so I don't think there is anything stopping Novell was using MS patents with GPLv2 only licenses.

      I still don't see where MS was used the GPL.

    8. Re:Good try? by init100 · · Score: 1

      When did MS ever use the GPLv2 or v3?

      When they released Services For Unix. This package among others include GCC, which is a well known GPL-licensed program.

    9. Re:Good try? by sumdumass · · Score: 1

      I wasn't aware they were distributing that. I thought they used a package from softway called Interix that had their own compiler and tools. I remember information in it that sent you to other places to download some GNU software if it was needed.

      I have checked and it does appear that MS purchased softway around 2000 or so and they do include the GPLv2 versions of GCC now. I stand corrected. The more I look at it, It seems that interix used GNU tools too.

    10. Re:Good try? by mrchaotica · · Score: 1

      What does Novell have to do with MS using the GPL v3?

      Novell is involved because MS attempted to use clever trickery to avoid technically "distributing" the software itself. Instead, MS issued vouchers redeemable for the software, and the entity doing the redeeming is Novell. But the clever trickery fails because the new version of the GPL covers "conveyance" in addition to "distribution," and (at least according to the FSF) "conveyance" includes the voucher scheme too.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    11. Re:Good try? by houghi · · Score: 1

      Uhm. All that MS has agreed with is to distribut SUSE Linux Enterprise Server vouchers. It does not actualy distributes Linux. It gives away a code that enables you to download for one year the updates for SLES.

      I have such a code and if I desire to do so, I can give it to anybody else, without actualy giving out any OSS.

      In the worst case MS is distributing Novell CDs. Furthermore it is a contract between Novell and MS, not between Novell and myself or MS and myself. Even without the agreement between the two, MS could try to enter code into the kernel, but then it would be GPLv2 (for now) right away.

      The only thing I see is anti-MS behaviour, instead of pro-OSS behaviour.

      So please let them put in as much patented and copyrighted material into the source, because that would mean it would be GPLed right away. MS won't do that, because they might be assholes they are not stupid.

      As a matter of fact each and every person who put something in the kernel did so with their copright (Berne convention) and then put it iunder GPL. MS (just like any other individual or company) must do the same or it won't be accepted.

      --
      Don't fight for your country, if your country does not fight for you.
  13. Wording is also a problem by paulpach · · Score: 1
    From the GPLv3, the wording meant to stop Microsoft-Novel deals is:

    ...You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work...

    So all Microsoft has to do is give the patents to a proxy company that is not in the business of distributing software, ie. a patent troll, and the proxy company can do the Proxy-Novel deals for them, even over GPLv3 software, without Novel being in violation of the GPLv3.

    And if you are thinking of removing the "that is in the business of distributing software" part for your project, think again. Your license would have additional restrictions not present in vanilla GPLv3. Your modified GPLv3 would not be GPLv3 compatible and your code would no longer be able to link to GPLv3 code. You would not be able to accept patches to your code under GPLv3.

  14. how odd... by d34thm0nk3y · · Score: 3, Insightful

    I can't even figure out what they are trying to say with this article.

    Microsoft doesn't distribute GPL software so of course they will not be bound by the GPL.

    And secondly, I though the MS Novell deal was grandfathered in anyway. The only reference I can find for that though is this line: "Among other things, the released version grandfathers in the Novell deal so that Microsoft's SLES coupons will undermine their patent threats" from the GPL ver. 3 release posting. link

    1. Re:how odd... by kryten_nl · · Score: 1
      She (Kay Lam-Beattie, principal with intellectual property lawyers Idealaw) comes to the same conclusion:

      In this case, she said, Microsoft never acted - never 'entered' into the agreement, and the terms and conditions can only apply to new actions by Microsoft, not older ones. She said: "Their actions so far are not enough to say that they are bound."
      The original ZDNet article is here: http://www.zdnet.com.au/news/software/soa/Microsof t-is-not-bound-by-GPLv3-Lawyer/0,130061733,3392804 77,00.htm?referral=dynamicbusiness

      Ms. Lam-Bettie made her statements on AusCERT 2007, which was held from the 20th to the 25th of _May_ 2007.
      Apparently here statements where in reaction to Free Software Foundation's Brett Smith, who appears to have said:

      [Under GPLv3,] if you arrange to provide patent protection to some of the people who get the software from you, that protection is automatically extended to everyone who receives the software, (...) This means that the patent protection Microsoft has extended to Novell's customers would be extended to everyone who uses any software Novell distributes under GPLv3, ... Emphasis mine.

      To make a long story short: It's the middle of July and Brett Winterford didn't have anything written, but he did have a dead-line.

      --
      For the perfect anti-Unix, write an OS that thinks it knows what you're doing better than you do and let it be wrong.
    2. Re:how odd... by tialaramex · · Score: 1

      Microsoft does distribute and will presumably continue to distribute GPL'd software. They provide their customers with the GNU toolchain among other things.

      They've been very good Free Software citizens all things considered, of course they're not a Free Software company like Red Hat, but they use, and abide by the terms of the GNU GPL, they provide the source code for the covered software on an open FTP site for anyone to download and they've always been very open about it. Of course the Microsoft VPs talking to the press are always going to say "Free Software is cancer" and such nonsense, but that's the same as when an Pharamaceutical Executive is saying "We need these high prices to pay for R&D". They're not actually stupid enough to believe this spin, and you shouldn't be either.

      The Big Pharmaceutical company aren't evil, despite telling some half-truths about the relationship between prices and R&D costs (hint: marketing is also expensive, but unlike R&D it isn't actually saving lives) and Microsoft isn't evil, despite maybe giving people the impression that Free Software is bad, or at least unnecessary, rather than being just as much a part of Microsoft's strategy as anyone else's.

  15. Exactly. by khasim · · Score: 5, Informative

    IANAL ... but the GPLv3 is a LICENSE not a CONTRACT.

    If Microsoft does not follow the LICENSE then Microsoft cannot LEGALLY re-distribute the software. Doing so would put Microsoft in violation of basic copyright laws.

    Which is why Microsoft quickly distanced itself from the GPLv3.

    1. Re:Exactly. by Anonymous Coward · · Score: 0

      If people stops developing GPLv2 code and starts developing GPLv3 code then:
      * Novell can't maintain itself of releasing recent GPLv3 projects.
      * Suse (buyed by Novell) can't maintain itself of releasing recent GPLv3 projects.

      If Microsoft did agree some agreement of patents with Novell or Suse that did release GPLv3 projects then Microsoft that was the client of GPLv3 has to refuse the uses of GPLv3 projects if doesn't want to have many problems.

      If Microsoft did lose its reason then its EULA is invalid, bla, bla, bla.

    2. Re:Exactly. by Anonymous Coward · · Score: 0

      IANAL ... but the GPLv3 is a LICENSE not a CONTRACT

      M$'s EULA ("End User License Agreement") is a LICENSE not a CONTRACT too.

      But, why the enterprises or third parties have to buy licenses if they are not contracts?

      They are stupids!

    3. Re:Exactly. by sumdumass · · Score: 3, Insightful

      The problem isn't with GPLv3 covered works or SuSE using it. The problem is that when MS entered into the arrangement the GPLv3 wasn't involved and the restrictions it imposes wasn't involved. So, if anything, the GPLv3 frustrates the deals and MS would likely only be obligated to what was around when the deals were made.

      If Novel takes an action independent of MS that subjects them to the GPLv3 license, MS can claim a separability from that. And because of the differences in the GPLv3, MS's obligations would become frustrated and they likely wouldn't be held to obligations that were frustrated if they didn't take any actions to cause the frustration. What would happen is that you would have to sue them and they would win. If they sued you and you used the GPLv3 as a defense, MS could claims the frustration, cite a few specific article where people have claimed they were going to manipulate the GPL to trick MS out of rights and that defense would likely be lost real fast.

      Further more, there are some question about the entire trapping them into being subject to the GPLv3 in the first place. It isn't as if once you distribute a GPLv3 covered work that you can never make a claim over IP or patents in a covered work, your limits only go to the work you distributed. So lets, say MS distributed GCC, They would have to both know that something was in it and violated their claims and distribute it after knowing this in order to not be able to go after patent claims on it. And this would have nothing to save Samba or any other project so if they avoid what that have issues and claims over, it still doesn't matter.

    4. Re:Exactly. by Nero+Nimbus · · Score: 1

      That's never been so much as a speed bump Microsoft before, so why would it matter to them now?

    5. Re:Exactly. by mrchaotica · · Score: 4, Insightful

      So, if anything, the GPLv3 frustrates the deals and MS would likely only be obligated to what was around when the deals were made.

      Right. In other words, Microsoft is only obligated to distribute GPL version 2 software.

      What would happen is that you would have to sue them and they would win. If they sued you and you used the GPLv3 as a defense, MS could claims the frustration, cite a few specific article where people have claimed they were going to manipulate the GPL to trick MS out of rights and that defense would likely be lost real fast.

      Hold on there, buddy! What you seem to be implying is that MS could distribute GPL version 3 software with impunity (otherwise, how would it make sense to "[use] the GPLv3 as a defense"?). That doesn't make sense, because all Microsoft ever promised to do was distribute the software that existed at the time the agreement was made -- GPL version 2 software.

      Nothing about the agreement gave (or even could give) the ability for Microsoft to ignore the license of code produced in the future, any more than the GPLv3 could give the ability to the FSF to condemn actions taken in the past!

      It isn't as if once you distribute a GPLv3 covered work that you can never make a claim over IP or patents in a covered work, your limits only go to the work you distributed. So lets, say MS distributed GCC, They would have to both know that something was in it and violated their claims and distribute it after knowing this in order to not be able to go after patent claims on it.

      Uh, no. All MS would have to do is willfully distribute it, whether it knew about patent violations or not.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    6. Re:Exactly. by Spazmania · · Score: 1

      Clearly YANAL. If you were, you'd know that a software license (like GPLv3) is a type of contract.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    7. Re:Exactly. by sumdumass · · Score: 2, Insightful

      Right. In other words, Microsoft is only obligated to distribute GPL version 2 software

      The problem is that MS isn't distributing anything. They are getting pulled into the coverage of the GPLv3 license by specific wording of the GPLv3 that includes conveying as well as distribution. This inclusion is not by any act of Microsoft but a change in an ancillary operations of a intentful license.

      Lets put this into some more relative terms, If you are supporting your product and how a third party uses an unrelated product that happens to be conflicting with your product, are you now bound by the license requirements of that third party software? That answer is no unless you received a copy of the software and installed it agreeing to the license and all that jazz. Now, ask yourself if you are subject to the terms of a license by telling the person having problems to goto the companies web page and get the updates and installing them? The answer there is no too. It doesn't matter what that license says or attempts to do, you aren't subjected to it. So, are you in copyright violation if you do any of the above without the express permission of the people who own the copyright on the third party software that is having problems with your program? Again the answer is no.

      So, MS isn't distributing anything, Novell is. Now that a license attempts to impose restrictions that weren't there when the deal was made, MS can only be held for the obligations it agreed to and that were present under the circumstances when the deal was made. SO yes, their agreement would only cover GPLv2 works and when Novell distributes GPLv3 covered works, MS isn't part of that. It is independent of their deal even if some aspects appear to overlap.

      Hold on there, buddy! What you seem to be implying is that MS could distribute GPL version 3 software with impunity (otherwise, how would it make sense to "[use] the GPLv3 as a defense"?). That doesn't make sense, because all Microsoft ever promised to do was distribute the software that existed at the time the agreement was made -- GPL version 2 software.

      No, What I am talking about is that MS isn't actually distributing covered works and because the GPLv3 license says so doesn't make them a party to that license just because they made a deal under conditions of another license. Novell can act independent of MS and use GPLv3 covered code but that doesn't obligate MS to the terms of it. MS would have to make an action on it's own to become covered by the GPLv3 license. The deal isn't enough to be this action.

      Nothing about the agreement gave (or even could give) the ability for Microsoft to ignore the license of code produced in the future, any more than the GPLv3 could give the ability to the FSF to condemn actions taken in the past!

      It doesn't need the ability. All it takes to frustrate a deal is to impose restrictions that a person or company cannot agree to after the fact. Suppose we had a deal where I supplied you with parts for your device for $1 a piece under the condition you only purchase your parts from me. My manufacturing plant burns down and I cannot build a new one soon nor can I supply you with the needed parts for another year. The deal is now frustrated and I cannot hold you to only getting parts from me.

      Now suppose the parts are patented by a third party who carried a term in the license that says if you use a sweatshop, you have to pay an additions $5 per unit produced. He heard I was going to china to open a factory to continue making the part and included that provision after our deal was made. When I went to China to make your parts, the new plant is considered a sweat shop and your product now costs $6. Are you liable for the extra $5 or just the $1 per part that our agreement was over? That answer is you are only obligated for the $1 dollar. Now, I cannot take a $4 dollar loss so our deal is frustrated and we cannot enf

    8. Re:Exactly. by jbengt · · Score: 1

      The use of the words "conveying" and "propagating" was meant to clear up international differences in legal definitions of terms. In the US, "distribution" includes many forms of "making available to the public" or "communicating to the public", so, GPL2 or GPL3, MS may already be obligated by a waiver to not sue Gnu/Linux users for any patents that might be infringed by the software. I doubt they'll ever take the chance to test this in court, so I don't fear them suing me for patents that might cover GPL2 software that I use.

    9. Re:Exactly. by Anonymous Coward · · Score: 0

      Where did doug get his legal training? His mother's basement?

      1) Only REAL ESTATE contracts *must* be signed to be enforceable, to satisfy the Statute of Frauds. All other contracts can be executed however the parties so choose to execute the contracts, be it signing, shaking, dancing, or any other (legal) activity. (Contracts cant' require the performance of illegal acts.)

      2) A license is a contract. Because a contract is just an agreement where both sides agree to do something for the purposes of getting the other side to do something.

      3) WTF? Copyright law? Are you high?

      4) Parties aren't bound by contracts OR LICENSES they did not agree to. That's been the law of the US and Britain for *hundreds* of years. MS isn't bound unless they 1) perform an action that would signify acceptance of the GPL3 license AND 2) indicate the ACTUAL INTENT to accept the license.

      YOU CAN'T FORCE SOMEONE TO ACCEPT A LICENSE OR CONTRACT VIA INACTION unless the accepter has already clearly stated that his inaction may be construed as acceptance.

      Sources:
      American Jurisprudence - Contracts.
      Contract Law (Murphy).
      Contracts: Example & Answers (Blum).

    10. Re:Exactly. by harlows_monkeys · · Score: 1

      If Microsoft does not follow the LICENSE then Microsoft cannot LEGALLY re-distribute the software. Doing so would put Microsoft in violation of basic copyright laws.

      Microsoft isn't re-distributing the software. They are giving out certificates that were bought from Novell. The way the press releases are worded, it sounds like they received a batch of N certificates.

      And if by some big stretch someone argues that distributing a certificate that is redeemable at another company for a copy of software counts as distributing the software (a notion that has no support in any case law or statute that I've seen...), Microsoft would still be off the hook, because of the first sale doctrine. They would be in exactly the same position as a bookstore that sells used books. Once the book is bought from the initial seller, the buyers can resell it ad infinitum with no need to get permission from the copyright holder. Certificates from Novell would be just like that--once Microsoft gets them from Novell, they are commodities that can be freely bought and sold.

      (BTW, this is also why, if you sell something like your Tivo on eBay, you don't have an obligation to provide the source code to the buyer. You are distributing GPLed software when you sell a Tivo, but the first sale doctrine gets you off the hook).

      I have no doubt that this is why the deal was structured around certificates. It puts Microsoft on safe, firm, legal grounds not only against GPLv3, but also against any other licenses used in software Novell includes in current or future versions of SUSE.

    11. Re:Exactly. by init100 · · Score: 1

      May I ask you a simple question that I have been wondering about for some time? Are you a lawyer? Sometimes you sound like someone with legal training, but sometimes you just sound like you are talking out of your ass (or rather asserting your highest hopes as fact).

    12. Re:Exactly. by VGPowerlord · · Score: 1

      IANAL ... but the GPLv3 is a LICENSE not a CONTRACT.

      If Microsoft does not follow the LICENSE then Microsoft cannot LEGALLY re-distribute the software. Doing so would put Microsoft in violation of basic copyright laws.

      Which is why Microsoft quickly distanced itself from the GPLv3.

      As much as I hate saying IANAL at the beginning of every post I make dealing with law, the last time I didn't, some smartass made a commant about it, so here it is.

      A license gives you additional rights not given to you by a law. In this case, copyright law.

      However, if copyright law says I can do something and a license says I can't... copyright law wins, because it's the law.

      The doctrine of first sale is a good example of this point. If Redhat, for example, makes a new Linux distribution with GPLv3 software in it, I can buy a bunch of copies of it and then sell them without ever agreeing to the license. In the US, this is codified in Title 17 Section 109.

      The wording of that section and Section 117 say that, if I destroy all copies I've made of that distribution, or give the new owner any copies I've made, I can also sell a used copy without GPLv3 provisions going into effect. Once I give a copy I made to someone else (without also giving them the original and all other copies I've made), or distribute any changes I've made, then I'm bound by the terms of the GPLv3.

      P.S. As far as I can tell, EULAs are illegal in the US. You don't need a license to install and use a copy of a software product you legitimately bought, thanks to Title 17 Section 117. Also, as I pointed out earlier, a license is used to grant additional rights, not take them away. To be honest, I believe that this is the actual reason Microsoft backed off, as involvement in a software license suit might bring more scrutiny to their own "licenses."
      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    13. Re:Exactly. by cynyr · · Score: 1

      Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. from http://www.gnu.org/licenses/old-licenses/gpl-2.0.h tml

      that would seem to imply that I as the user of gpl 2.0 licensed software, if it contained the statement referenced above, would be free to choose the GPL-3 would be free to impose the conditions of the gpl 3, on the distributer even if they were entered into an agreement with a third party.

      Further, The GPLv3 specifically states that if _you_ include something, you have to have the rights to do so while following the other conditions of the same clause. If the disputed IP is placed in without the rights, it isn't in there. This is something people are going to be running into problems with when they take existing GPLv2 projects and move them to the GPLv3. If something is in them that another person or company has a claim to, they are taking the personal liability for including it under a license that pretends to have the right to use it. When ever you distribute a GPLv3 covered work, unless you place something in it, or specifically know about the issue, you aren't adding anything to the covered work. You cannot be tricked out of your property by mere association. There has to be some purposeful act that you take. The idea that the GPL now attempts to trick people out of their possessions by sneaking a copy into something without your knowledge or permission is ridiculous. If ever there was something wrong with life, that would be it.

      MS did give the rights to include that IP to Novell in the deal they made, so that rules that bit out. since it sounds as if you give the rights to do so, or do so yourself that you are then bound by the license.

      IMO(IANAL) I do think that if any of the software that MS gave out vouchers had the clause in it to allow the use of any other later license that is grounds to hold them to it for that piece of software, now i think that SAMBA is licensed in such a way, I'd have to go look it up, but if it is then they just gave out a copy of all patents free to use.
      P.S. that'll be a 5000USD fine for breaking the encryption on my post.
      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    14. Re:Exactly. by dhasenan · · Score: 1

      So, if anything, the GPLv3 frustrates the deals and MS would likely only be obligated to what was around when the deals were made. Right. In other words, Microsoft is only obligated to distribute GPL version 2 software. That depends on whether the MS-Novell deal specifies whether it applies to arbitrary software in SuSE or to specific software, and whether Microsoft can choose what parts of SuSE it distributes.

      I imagine, though, if SuSE wants to renew the deal, or increase its scope, it will maintain a GPLv3-free branch for Microsoft to distribute. Unless the doctrine of first sale or some other law intervenes, given that Microsoft bought each license they distribute. (You wouldn't expect Borders to be bound by the GPL since they distribute Red Hat binaries with some Linux books, would you?)
    15. Re:Exactly. by sumdumass · · Score: 1

      The later. But don't let that scare you off.

    16. Re:Exactly. by sumdumass · · Score: 1

      that would seem to imply that I as the user of gpl 2.0 licensed software, if it contained the statement referenced above, would be free to choose the GPL-3 would be free to impose the conditions of the gpl 3, on the distributer even if they were entered into an agreement with a third party.
      Sure, sort of. If the statement said "or later version" But the problem is in the timing. When does the GPL kick in for you? Nto when you get the software but when you distribute it. Remember, acceptance is not require to get a copy or use the program, that it outside the scope of this license, Your license change would only take place when you took an action to make the product subject to the GPL again.

      So if you received a copy of something that was GPLv2 or later versions, then you received a GPLv2 copy. You can decide to change it to GPLv3 if it is a later version when you distribute it and the GPL kicks in again. But first you have to make sure that you can satisfy all the requirements of releasing something under the GPLv3 (like patents and having the rights and all that are specifically separate from ).

      MS did give the rights to include that IP to Novell in the deal they made, so that rules that bit out. since it sounds as if you give the rights to do so, or do so yourself that you are then bound by the license.
      Ok, SO if Novell places it in there, MS is can be held to it. But that doesn't take away that if Novell, MS, or any other company distributes a GPLv3 covered product that contains their patents or IP, but they do not know about it being un there, they didn't give any rights to it up. That was the point, not that Novell can act like an agent for MS. It is the process of knowing that you are giving your rights up. The GPLv3 specifically says that rights are given to you and you must pass them on. It wouldn't imply that by participating in anyway, you are forgoing any rights you might have.

      IMO(IANAL) I do think that if any of the software that MS gave out vouchers had the clause in it to allow the use of any other later license that is grounds to hold them to it for that piece of software, now i think that SAMBA is licensed in such a way, I'd have to go look it up, but if it is then they just gave out a copy of all patents free to use.
      Samba has more problems then this to worry about. Well, once they release something GPLv3 as they announced they are moving to. MS can make a few changes and pretty mutch make them an irrelevant relic of the past while using the GPLv3's anti-Novell clause to do so.

      But I don't think that changing the license after the fact obligates MS to anything that wasn't present at the time they made their arrangement. If anything it frustrates the deal and MS should be able to pull out of it, or the parts (the part covering the GPLv3 software) where the license went to something that they couldn't accept. Recently, we saw a decision where websites have to inform everyone specifically of changes in their policies. This wasn't to make sure everyone knew they were screwed but to give them a way out is the terms were unacceptable. Switching license versions is MS's out if only for the Newly licensed software.

      Frankly, I'm getting a little concerned with the attitude that we can somehow now use a technicality to take something from someone else. I expect this type of behavior from greedy corporations and politicians on the take but not from the free software community who has been always the underdog and subjected to stuff like this. I guess when in Rome, do as the Romans do, except, I'm thinking we should stay as far away from Rome as possible. Maybe I just haven't drank enough of the cool aid?
    17. Re:Exactly. by Warbothong · · Score: 1
      We must crack down on these damned pirates! They have no regard for copyright, intellectual property or the US constitution! They go ahead and download software from the Internets, which is STEALING, and then try and redistribute it to honest, law abiding citizens, turning them into dirty, murdering, rapist pirates too! The only way to stop this vicious cycle of sharing, which loses a thousand billion dollars a year for the content industry, is to vote YES to the Mickey Mouse Protection Act, and to vote YES to the Privacy Equals Terrorism Act (after the latter is passed you can carry on with your impulse buying, TV watching, money spending, iPhone touching little consumer 'lives', since we can then vote on your behalf for the rest of the powers we want). Hurry and tell your friends, family, neighbours, coworkers, pets, etc. Make sure they know!*

      * This Information (hereafter referred to as the Information) is protected by international copyright, trademark and patent laws. You are forbidden to tell this Information to anyone, including, but not limited to, friends, family, neighbours, coworkers and pets. This license does not grant you rights to modify, reproduce, remember, read or otherwise know the existance of the Information.**

      ** This also applies to that notice***

      *** And these

    18. Re:Exactly. by mrchaotica · · Score: 1

      Lets put this into some more relative terms, If you are supporting your product and how a third party uses an unrelated product that happens to be conflicting with your product, are you now bound by the license requirements of that third party software?

      That's not the situation I'm talking about! The more appropriate analogy would be that you're reselling the third-party product yourself, the third party changes it's license for a new version of the software, and you continue to resell the product. In that case, you do indeed become subject to the license, because you could have chosen to cease reselling it but you continued, willfully, anyway.

      So, MS isn't distributing anything, Novell is.

      MS is distributing vouchers redeemable for SuSE Linux. According to the lawyers that wrote the GPLv3, that counts as "conveying" SuSE Linux. Therefore, if the vouchers were redeemed for GPLv3 software, Microsoft would become bound by the GPLv3.

      Now that a license attempts to impose restrictions that weren't there when the deal was made, MS can only be held for the obligations it agreed to and that were present under the circumstances when the deal was made.

      Right, MS can continue "conveying" the old version as if nothing had happened. But if Microsoft chooses to "convey" the new, GPLv3 version, then MS becomes bound by the GPLv3. This is common sense!

      Where it gets tricky is the fact that Novell, not Microsoft, is in charge of redeeming the vouchers. What that means is that Novell would be in a position to choose for MS, which would be where the "frustration" you're talking about would come in. But there are only two outcomes from that: either MS agrees with Novell's distribution of GPLv3 code, in which case MS becomes bound by the GPLv3, or MS doesn't agree and Novell distributed the code in violation of the GPLv3. But neither of those outcomes allows MS to "ignore" or "evade" the GPLv3!

      SO yes, their agreement would only cover GPLv2 works and when Novell distributes GPLv3 covered works, MS isn't part of that. It is independent of their deal even if some aspects appear to overlap.

      But MS becomes part of that if the GPLv3 code was distributed by redeeming a MS-issued voucher!

      No, What I am talking about is that MS isn't actually distributing covered works and because the GPLv3 license says so doesn't make them a party to that license just because they made a deal under conditions of another license.

      If GPLv3 code gets distributed or "conveyed," it is done so under the conditions of the GPLv3! This is a freakin' tautology; it shouldn't be that hard to understand! Sure, it's not the same agreement as before, but that's irrelevant. MS can't choose to ignore the new license any more than I could agree only to the Windows 2000 EULA and the install Vista.

      Novell can act independent of MS and use GPLv3 covered code but that doesn't obligate MS to the terms of it.

      Sure! Novell could absolutely distribute GPLv3 code completely outside of the agreement, and be just fine. But Novell can't distribute GPLv3 code when redeeming a MS-issued voucher without involving MS.

      Now suppose the parts are patented by a third party who carried a term in the license that says if you use a sweatshop, you have to pay an additions $5 per unit produced. He heard I was going to china to open a factory to continue making the part and included that provision after our deal was made. When I went to China to make your parts, the new plant is considered a sweat shop and your product now costs $6. Are you liable for the extra $5 or just the $1 per part that our agreement was over? That answer is you are only obligated for the $1 dollar. Now,

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    19. Re:Exactly. by sumdumass · · Score: 1

      That's not the situation I'm talking about! The more appropriate analogy would be that you're reselling the third-party product yourself, the third party changes it's license for a new version of the software, and you continue to resell the product. In that case, you do indeed become subject to the license, because you could have chosen to cease reselling it but you continued, willfully, anyway.

      I don't think that actively reflects the situation. When the local computer shop resells MS software, they don't agree to the license terms of the MS software before conveying it. And unless it is a special OEM version, they aren't required to support it outside what a local law might impose. Novell is offering a good (SuSE Linux) and they are the ones subject to the license agreements. You could argue that Novell's rights to use the code require them to impose obligations but that would be between the copyright holder and Novell not MS in this case.

      Where it gets tricky is the fact that Novell, not Microsoft, is in charge of redeeming the vouchers. What that means is that Novell would be in a position to choose for MS, which would be where the "frustration" you're talking about would come in. But there are only two outcomes from that: either MS agrees with Novell's distribution of GPLv3 code, in which case MS becomes bound by the GPLv3, or MS doesn't agree and Novell distributed the code in violation of the GPLv3. But neither of those outcomes allows MS to "ignore" or "evade" the GPLv3!

      I still don't see it as Microsoft being subjected to the license at all in this case. Novell is distributing the covered works. If anything it would be on Novell's ability to offer a product.

      "Someone else did?" Who did? Remember, I was talking about the situation where you willingly distribute the software, not "someone else." You can't willfully distribute something and then say "oh, whoops -- I didn't really mean it!" That's not how it works.

      Mere distribution doesn't take any rights on the patent deal from you. The "someone else" is whoever put the disputed IP into the product. If it wasn't someone who had the authority to do so then it isn't supposed to be in the work covered by the GPLv3 license. I would have to know that My claimed infringement exists in order to make an act of giving rights to it away. Even if I am willfully distributing the software. If I switch to your software because it works better then mine then later find out that you took MY IP and improved it without my permission, I wouldn't have gave anything up with the GPLv3 because of not only the wording of the GPLv3 but because of other ethical issues concerning theft and fraud. You just cannot submarine something into a product to trick a person or company to give up rights without their knowledge.

      Imagine you're at a flea market. You buy an old box for 2 bucks, open it, and find a million dollars inside. Can the guy who sold it to you suddenly claim that the million dollars is his just because he didn't realize it was there when he sold you the box? Hell no; he's just screwed! Similarly, Microsoft could not go conveying GPLv3 software and then try to claim the patent indemnification doesn't apply because it "didn't know" that it would. MS would just be screwed.

      If the box was represented to only contain air and a few buttons, yes, he could go back on it. Especially when someone else took his million dollars and placed it there to come by later and buy the box. Which is more similar to what we are discussing with this.

      MS would have to either have placed the patent product into the covered work or specifically know it was there.

      Now, keep in mind that I'm talking about MS conveying the software itself, and admitting to doing so willfully. If it's the actions of a separate entity, e.g. Novell, that resulted in it being conveyed then MS would have to argue that

    20. Re:Exactly. by mrchaotica · · Score: 1

      I don't think that actively reflects the situation. When the local computer shop resells MS software, they don't agree to the license terms of the MS software before conveying it. And unless it is a special OEM version, they aren't required to support it outside what a local law might impose. Novell is offering a good (SuSE Linux) and they are the ones subject to the license agreements. You could argue that Novell's rights to use the code require them to impose obligations but that would be between the copyright holder and Novell not MS in this case.

      First of all, I see now that I should have chosen my words more carefully -- "resell," in the sense of a middleman that blindly passes the software on and isn't involved with the license at all, really wasn't what I meant.

      Second, being neither a lawyer nor an expert on exactly what those vouchers say, I'll refrain from arguing this point except to say that the FSF seems to think that Microsoft's involvement as the originator of these vouchers makes it more than just a reseller -- enough to become subject to the license of the software. I trust the opinion of the FSF lawyers more than I do that of the random one that wrote the article.

      I still don't see it as Microsoft being subjected to the license at all in this case. Novell is distributing the covered works. If anything it would be on Novell's ability to offer a product.

      What's your point? All I said was that nothing allows Microsoft to "ignore" or "evade" the license. "Ignoring" or "evading" a license means having the ability to distribute the software it covers without being bound by its terms. Refraining from distributing at all therefore does not count as "ignoring" or "evading," and thus the lawyer that "thinks Microsoft can Evade [the] GPL 3" is wrong.

      The "someone else" is whoever put the disputed IP into the product. If it wasn't someone who had the authority to do so then it isn't supposed to be in the work covered by the GPLv3 license. I would have to know that My claimed infringement exists in order to make an act of giving rights to it away.

      WTF?! No, you're wrong. There exists a thing called "due diligence." If you're going to sell a product, it's your responsibility to figure out what the fuck you're selling before you do it! To think otherwise is, frankly, ridiculous and absurd.

      I'll bet people on trial for fencing stolen goods use your argument all the time, and I'll bet that, if that's their best argument, they swiftly end up in jail.

      Even if I am willfully distributing the software. If I switch to your software because it works better then mine then later find out that you took MY IP and improved it without my permission, I wouldn't have gave anything up with the GPLv3 because of not only the wording of the GPLv3 but because of other ethical issues concerning theft and fraud. You just cannot submarine something into a product to trick a person or company to give up rights without their knowledge.

      Okay, now you're just trolling me.

      • First of all, there's no such thing as "IP." There are patents, copyrights, trademarks, and trade secrets, and none of them are even slightly like property!
      • As an aside, think for a second about what you just said. You're actually complaining that someone improved your idea! And you think the person should require your permission to do so? Just who the fuck do you think you are?! Seriously!

        Here's a newsflash: you do not have some sort of God-given "right" to your ideas, and they are not your property, "intellectual" or otherwise. The only -- rather tenuous -- claim you have to them is based on a set of laws that exists "To Promote the Progress of Science and the Useful Arts," for crying out loud! And you have the sheer gall and audacity to t

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    21. Re:Exactly. by Stephen+Samuel · · Score: 1

      The problem is that MS isn't distributing anything. They are getting pulled into the coverage of the GPLv3 license by specific wording of the GPLv3 that includes conveying as well as distribution. This inclusion is not by any act of Microsoft but a change in an ancillary operations of a intentful license. If Microsoft is paying someone else (Novell) to distribute someone else's copyright work (GPL3 software), they had better have a valid license to do so (i.e. be doing it within the GPL3 terms), or they're going to be liable for (either contributory or direct) copyright infringement.

      Indirect copyright infringement is what brought down Napster -- they weren't actually distributing the software, but they were enabling someone else to.

      If Microsoft doesn't want to be tied by the terms of the GPL3, the only real way to be sure that they aren't is to not be party to the distribution of GPL3 software. Anything else is just dancing on the head of a pin, and hoping you don't fall off.

      --
      Free Software: Like love, it grows best when given away.
    22. Re:Exactly. by sumdumass · · Score: 1

      If Microsoft is paying someone else (Novell) to distribute someone else's copyright work (GPL3 software), they had better have a valid license to do so (i.e. be doing it within the GPL3 terms), or they're going to be liable for (either contributory or direct) copyright infringement.
      Your forgeting that MS is able to assume that the third party (Novell) has a valid right to distribute copyrighted works independent of MS's actions. This is a degree of separability that people are refusing to consider. It all seems to be that MS is causing the covered works to exist when they are just repeating something already available legally.

      Indirect copyright infringement is what brought down Napster -- they weren't actually distributing the software, but they were enabling someone else to.
      I wish everyone would stop repeating this garbage. It is like the new flavor of bubble gum that everyone is raving over, unfortunately, just like the gum, after you chew on it for a while, you have to spit it our and throw it away.

      What got Napster in trouble wasn't linking to copyrighted works. It ws doing so knowing that the copyright was being violated or infringed on. That is what is at issue here. Will MS be secondary liable for a crime that doesn't exist, the answer it a resounding NO. anyone providing the copyrighted works would have to be in violation in it's own right for MS to be subjected to it in this way. And then all the have to do is stop because they aren't obligated to violate a law to keep a contract.
    23. Re:Exactly. by Weedlekin · · Score: 2, Insightful

      "MS is distributing vouchers redeemable for SuSE Linux. According to the lawyers that wrote the GPLv3, that counts as "conveying" SuSE Linux."

      This is a ludicrous assertion. Many magazines, newspapers, gas stations, and product boxes carry vouchers that are redeemable against a huge variety of items, but they aren't assumed by law to be distributors of those items, any more than I would be if I gave somebody some money to go to a store and buy said product for themselves. A voucher that entitles one to a free SUSE Linux isn't distributing Linux any more than one that says "Free Big Mac when you show this at any Macdonald's" is distributing Big Macs - Macdonald's are doing the distributing, not whoever is issuing the voucher. If the GPL 3 says otherwise, then it's in for an extremely rough ride when it gets tested in the courts, so I'm pretty sure that it doesn't actually say anything of the sort.

      I'm also pretty sure that GPL3 neither implies nor specifically states that those who sell sealed, boxed versions of a compliant Linux distro are bound by it, because that would have raised screams of protest from commercial Linux distros such as RedHat, not to mention being guaranteed a quick and ignominious death if somebody challenged it in court. Even Microsoft haven't got the temerity to try and bind wholesalers and retailers to their software licensing terms (that's why EULA is an acronym for end-user licensing agreement), so it's hard to see why so many people here think that Stallman et al would be stupid enough to try and pull something that even a predatory monopoly with several entire governments in its pocket doesn't think it could get away with.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    24. Re:Exactly. by Cessen · · Score: 1
      I believe this excerpt from the GPLv3 is relevant to this discussion:

      If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all.

      IANAL, but I read this as saying that--for instance--if you are unable to propagate the patent rights that you have relating to the software, then you may not redistribute it. An almost identical clause exists in the GPLv2 as well, but the patent issues are made explicit in the GPLv3 elsewhere in the license, giving this clause more bite regarding patent rights.

      So although Microsoft may not be in any hot water, Novell still would be. Novell cannot distribute GPLv3 software if their patent deal with Microsoft doesn't allow them to pass on the patent rights Microsoft gives them in a way that is consistent with GPLv3 terms. This may also implicitly be the case with the GPLv2, but due to being implicit it's substantially shakier in that case.

      As far as I can tell, the point of the GPLv3 was not so much to trap Microsoft as it was to keep the Novell/Microsoft deal (and other similar deals) from trapping Free Software. In that goal I think it succeeds. Assuming people adopt the GPLv3, anyway.
    25. Re:Exactly. by harlows_monkeys · · Score: 1

      So although Microsoft may not be in any hot water, Novell still would be. Novell cannot distribute GPLv3 software if their patent deal with Microsoft doesn't allow them to pass on the patent rights Microsoft gives them in a way that is consistent with GPLv3 terms. This may also implicitly be the case with the GPLv2, but due to being implicit it's substantially shakier in that case.

      Novell may even escape that. The part of GPLv3 that requires passing on the patent rights is this. I've marked in bold three very interesting parts:

      If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

      If Novell says they don't believe that Microsoft's patents that cover GPLv3 software are valid, or they don't know which patents are infringed, or they think there is some reason the patents aren't infringed, then they aren't knowingly relying on the patent license, and they escape. They can take the tack that they don't think the patent license is necessary for the user, but for users that might disagree and are worried, those users can buy from Novell and feel safe.

      Note also that if the source is available under the terms of the license on a public server, then we don't even get to the patent license stuff. I'm not sure just what that means. Suppose, for example, GCC goes GPLv3, and suppose Novell makes no modifications to it, just keeping it exactly like it is on the official download sites. Then it is available, under the terms of the license. Does this mean that the things about passing on the patent license protection only even becomes a potential issue in the case of things that Novell modifies?

      There's another part of GPLv3 which basically says you can't convey GPLv3 software if you are a party to an arrangement like the Microsoft/Novell arrangement. That seems on first reading to be pretty airtight, but it has a grandfather clause that exempts deals made before a certain date, and the Microsoft/Novell deal was earlier than that, so no problem for Novell there. It does stop anyone else from getting such a deal, though.

      It's this last that I find most noteworthy. If Novell indeed can escape the first part because they aren't knowingly relying as defined in GPLv3, then that leaves them with a competitive advantage over the other enterprise Linux vendors when it comes to selling to nervous companies that worry about Microsoft's big patent portfolio. Yes, GPLv3 helps Novell!

      Note that if Microsoft were to actually sue, say, a Redhat customer over a patent covering some software that is common to Novell and Redhat, and Microsoft won, then Novell now would know of an actual patent that is really infringed, and if they didn't stop including that software in SUSE, then they would be "knowingly relying" on the patent license, and so would be in violation of GPLv3. So what the deal with Microsoft really means, after GPLv3, is that if Microsoft gets litigious, and starts knocking things out of Linux distributions via patent suits, Novell will have to drop those things from its Linux distribution, so they won't have an advantage over, say, Redhat, in the content of their distribution.

    26. Re:Exactly. by sumdumass · · Score: 1
      Your pretty foolish and suffer a disconnect with reality if you actually believe half the stuff you wrote. You make an attempt to call me a troll yet it seems obvious the shoe is on the other foot.

      First of all, I see now that I should have chosen my words more carefully -- "resell," in the sense of a middleman that blindly passes the software on and isn't involved with the license at all, really wasn't what I meant.

      Does really matter what you meant. The fact is, Novell has a product, MS sells access to it, they support it when it is intended to work with MS's products. It isn't much different then a shop that resells a product

      Second, being neither a lawyer nor an expert on exactly what those vouchers say, I'll refrain from arguing this point except to say that the FSF seems to think that Microsoft's involvement as the originator of these vouchers makes it more than just a reseller -- enough to become subject to the license of the software. I trust the opinion of the FSF lawyers more than I do that of the random one that wrote the article.

      You can root for the home team all you want. But I wouldn't bet your house on something on blatantly wrong hype. You can look at the GPLv3 and all the holes contained in it plus the dangerous situations it leave open to know that their lawyers are lacking in a few key areas.

      I'm wondering, how many cases have they actually won and how many have they taken to court.

      What's your point? All I said was that nothing allows Microsoft to "ignore" or "evade" the license. "Ignoring" or "evading" a license means having the ability to distribute the software it covers without being bound by its terms. Refraining from distributing at all therefore does not count as "ignoring" or "evading," and thus the lawyer that "thinks Microsoft can Evade [the] GPL 3" is wrong.

      It isn't that they are ignoring the GPL in itself. It is that they can ignore half of the preposterous positions you are attempting to put them in with the idea that it subjects them to it. There is a limited amount of things they can do to be subjected to the GPLv3 and it seems to be less then what you think.

      In that case, he might have a valid grievance against the person who put the money in the box, but not the person who bought it! Similarly, Microsoft would have a grievance against Novell, but not the copyright holder of the GPLv3 software.

      I think you will be hard pressed to find a situation where someone got something they weren't expecting, found out that something was stolen and was allowed by some right to keep it. Even if the wronged party discovered it afterwards.

      WTF?! No, you're wrong. There exists a thing called "due diligence." If you're going to sell a product, it's your responsibility to figure out what the fuck you're selling before you do it! To think otherwise is, frankly, ridiculous and absurd.

      I'll bet people on trial for fencing stolen goods use your argument all the time, and I'll bet that, if that's their best argument, they swiftly end up in jail.

      I can see you have a poor grasp of how things work. The due diligence part is commonly satisfied but representations and statements of fact presented wehn they aquired the product. The GPLv3 does this specifically by saying that anything in there is given to by a license from the contributer,

      Section 10 the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

      and section 11: Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

    27. Re:Exactly. by Cessen · · Score: 1

      If Novell says they don't believe that Microsoft's patents that cover GPLv3 software are valid, or they don't know which patents are infringed, or they think there is some reason the patents aren't infringed, then they aren't knowingly relying on the patent license, and they escape.

      Yup. And that would be exactly as if they'd never made the Microsoft deal at all. So it's moot. Microsoft can still sue over patent infringement, they don't need Novell for that. So I fail to see your point.

      The only use the Novell deal has to Microsoft is if Novell depends on Microsoft's patent protection to implement Microsoft-patented technology into Free Software. GPLv3 would keep that from happening.
    28. Re:Exactly. by Stephen+Samuel · · Score: 1
      The crime of copyright violation does exist, and if it's done for commercial gain, the penalties increase.

      Novell may not be bound to breach the law to complete a contract, but -- if MS enters into a contract with Novell that requires them to violate copyright to fulfill the contract, and Novell does so, in the completion of said contract, Microsoft is going to be vicariously liable for the copyright infringement. It's actually more culpable than Napster, which simply distributed software that allowed people to violate copyright -- knowing that it was extrememly likely -- and just implicitly encouraged the violation.

      Now, .... yeah, Microsoft might be able to get away with this.. but, with billions possibly onthe line, it's not likely worth the rather substantial risk of losing in court.

      --
      Free Software: Like love, it grows best when given away.
    29. Re:Exactly. by sumdumass · · Score: 1

      but -- if MS enters into a contract with Novell that requires them to violate copyright to fulfill the contract, and Novell does so, in the completion of said contract, Microsoft is going to be vicariously liable for the copyright infringement.
      If is a mighty big word. So far it hasn't happened. And the likelihood of it happening is slim. Even if someone cashes in on the vouchers, MS can claim that since the GPLv3 wasn't around at the time, they aren't obligated to it or anything associated with it, tough luck and void their application towards GPLv3 software.

      Now, .... yeah, Microsoft might be able to get away with this.. but, with billions possibly onthe line, it's not likely worth the rather substantial risk of losing in court.
      I don't see how they would lose in court or even have to put anything at risk. What would happen is that the GPLv3 would create obligations that didn't exist at the time the deal was made. It would be up to whoever is loosing out to decide if they wanted to risk those obligations or not. Even so, if someone cashes in a vouch expecting GPLv3 software, it isn't likely that MS or novel would be forced to cover it. And to that point, It doesn't touch MS. The vouchers had an expected value at the time they were sold.

      Back to the point, MS isn't anywhere close to what Napster was. Napster was hosting the locations of files they knew were in violation of copyright. MS is pointing to another company that legally sells and distributes the copyrighted material. If you goto a store that has existed for 20 years, buy a book that was pirated and placed in the store for sale, you yourself aren't linked to the illegal activity. If anything, this situation is in the same sense. Me telling you to goto the store because they got good deals doesn't make me liable for infringement. You buying me a gift certificate so I can goto the store and buy one of the books wouldn't make me liable.

      What would make me liable is if I knew that the copyright was being infringed and then told you to get your stuff there because of that. This wouldn't be the case in MS and Novell. Novell has a legal product that they are distributing, If something changes on that, MS has the ability to get out of it unscathed. The contract with novel isn't a contract to break a law or anything. Novell isn't offering illegal that MS is providing to anyone. I don't see it ever going that far either, Any voucher put in that position would just be refunded or refused. And MS would be separated from it. Again, Nothing like Napster.
    30. Re:Exactly. by Stephen+Samuel · · Score: 1
      I fully agree that MS doesn't have to agree to the GPL 3 and is free to argue that it'd not going to accept it. If you argue that MS isn't bound by the GPL3, then they're not protected by it, either.

      If you're not protected by the GPL3, then anything that you do to cause GPL3 software to be distributed and copied is subject to normal copyright rules -- I.E. a violation of copyright. It's no different than having someone distribute a Rolling Stones CD for you -- or a copy of Pirates of the Caribbean 3. If you're not doing it under the protection of some legitimate license, then you're liable for all sorts of civil and criminal penalties.

      Remember, nobody has an intrinsic right to distribute GPL software without the protection of the GPL. If you don't agree to the GPL3, then you're not protected by it. This is very different from the normal EULA, which tries to take away your rights, and give you nothing in return. If you weasel out of MS's EULA, then you're left with your rights under copyright -- which is noticeably more than what you have if you agree to it.

      --
      Free Software: Like love, it grows best when given away.
    31. Re:Exactly. by sumdumass · · Score: 1

      Protection in the normal sense would be appropriate. but unfortunately we aren't talking about the normal sense in this situation. Effected by the GPL is more to the point and more accurately describes the situation being discussed. So lets keep things into perspective a little here. after all, we are talking about the gplv3 attempting to take away the right of Microsoft to do something they are already doing or continue to let them do it but take away their rights to other property(patents).

      Now with that out of the way, I have yet to see a convincing argument of how reselling gift certificates to an establishment would make a person liable to anything imposed on that establishment. This is after all, what the vouchers really come down to. MS paid for the gift certificates with the patent deals, Novell produces a product and MS give the vouchers for that product away when someone buys support from them. I don't think it would be likely that the rules of napster would apply making you and I liable if I purchased you a $100 coupon for allofmp3.com and you used it to purchase music then they have been found to have violated copyright in giving/selling the music to you. It just wouldn't fit into any normal realms of reality, Novell hasn't violated any copyright yet and if or when it does, as long as MS distances itself from the act, it is all good for them.

      Even if MS was subjected to the GPL in some way, which outside people claiming the "GPL says this", I'm not sure I can see the connections, like we both agreed on already, all they have to do is not use the version that they don't like. And this is easy because the versions weren't in play when their deal took place. But something that might be more interesting is how would a court interpret the provisions in the GPL that would effect Microsoft negatively when the GPLv3 was rewritten after the MS Novell deal specifically to punish the parties and benefit the GPL community? I mean could I write something after the fact to impose influence to a party of a deal you made with a third party knowing I am the sole provider of their product's material? If the answer is yes, then this just shows how dangerous it is to work with a license like the GPL and not a contract that would take all parties to agree on the changes.

    32. Re:Exactly. by Stephen+Samuel · · Score: 1
      Microsoft entered into the deal to distribute GPL2 software, and as long as they limit themselves to (legacy) GPL2 software, you're right that there's nothing to stop them from doing that.

      If, on the other hand, they want their customers to have the full value of the newest versions of some software, then they're gonna have to swallow the GPL pill.

      Things to remember here:
      1: The general feeling is that the MS/Novell agreement was designed to violate the basic spirit of the GPL2. No judge is going to take umbrage at the fact that the people providing this valuable software closed a loophole in their license.
      2: Microsoft is paying someone to manufacture and distribute a third party's software. If that third party is unhappy with what Microsoft is returning to them, they're free to say no.
      A judge is about as likely to force the FLOSS community to distribute their software under the GPL2 as they are to force Microsoft to distribute their software under the GPL2. (unless, of course, Microsoft decides to affirmatively claim that they're distributing their software under the GPL2, in which case they'll be bound by the legal principle of estopel.

      Again: as long as Microsoft remains within the bounds of bare copyright law, they can do whatever copyright allows, and the GPL can't touch them. (actually, the GPL allows MS to do some things which would be illegal under bare copyright law without imposing any constraints).
      You claim that MS never had (much) control over the GPL3 -- that may be true, but neither did the GPL2 community have any input into the MS/Novell deal. If the GPL community decides to change their license to more clearly enforce the purpose of their original license, a judge who gets the case will be left dealing with the intent of the original authors of the software, vs. some company that wants to make money off of the original artist's work, without paying them anything, agreeing to their license for the software or even abiding by copyright law.

      I don't think it'll be a hard call for any sane judge.

      --
      Free Software: Like love, it grows best when given away.
  16. I thought this was intentional? by discordja · · Score: 1

    I may just be forgetting the facts, but I thought that the final revision was altered in such a way to not retroactive punish the ms/novell deal? Wasn't it designed to keep them from entering any others and to take effect once SLED integrated GPL3 code but not n the current GPL2 codebase?

    --
    I stole this .sig
  17. huh? by oohshiny · · Score: 1

    Of course, Microsoft/Novell don't have to worry about this because prior agreements are explicitly exempted.

    For later agreements, the lawyer is missing the point. If Company X distributes under the GPLv3, they are bound by its terms. If Company X later enters into an agreement with Company Y, they need to make sure that they are complying with their obligations under the GPLv3 in that agreement, and that may include imposing conditions on Company Y. If they fail to do so, then they lose the right to distribute the GPLv3 software.

    This isn't some bizarre legal theory, lots of software licenses work that way, including Microsoft's own.

  18. Unclean hands by Anonymous Coward · · Score: 1, Insightful

    It's not retroactive, nobody ever claimed it was. The thing is that MS have distributed vouchers without an expiration date, knowing about both indirect distribution and or later clauses. They also knew GPLv3 would have an Apache style patent clause.

    The courts take a poor view of bad faith attempts to break licensing agreements and Microsoft admitted to working around the GPL for the Novell deal. Microsoft, unclean hands and all will want to keep this one out of the courtroom.

    1. Re:Unclean hands by Anonymous Coward · · Score: 0

      For once, Microsoft isn't the one acting in bad faith here. GPL3 is ridiculous.

  19. good new for MS users by fermion · · Score: 2, Insightful

    For instance, if the terms of a credit card is changed, I believe one has the opportunity to cancel the card and continue to pay off the debt. So I can see that if MS and Novel never using new software that uses the GPL3, and never having to worry about the GPLV3. What I do not see is how MS can demand that the are allowed to interact with current software and not be under the current license. That would be like saying that MS users can never be under a licensee more restrictive than the first one agreed to upon initial use fo the software.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:good new for MS users by sumdumass · · Score: 1

      The problem is that under the GPLv2, no permission was needed to do anything with the software except in distributing it, parts of it, or product built from it. Now, under the GPLv3, they changed that to include the act of conveying it which is more then that.

      Now, all microsoft's actions were from before the GPLv3 came around. If novell changes something that has a restrictive license, Microsoft would have to do something to be bound by that license. Under the current deal, their support and access to updates doesn't require accepting the GPLv2 license and it wouldn't require it with the GPLv3 except by terms in the GPLv3. Now, if MS never accepted the GPLv3, and all it's exposure is because if third parties, why would they be bound to the terms of it. They aren't distributing it, they aren't propagating it, all they are doing is supporting it when you use it with their products and showing where you can get updates. None of which requires permission from the copy owner to do. So, until they do something that requires permission from the copy owner and they cave to accept the GPLv3, they won't be bound to it.

    2. Re:good new for MS users by jbengt · · Score: 1

      Selling coupons for those wishing to license Novell/Suse software may indeed be considered distribution under US law. Do you think Microsoft would want to test this in court by suing Gnu/Linux users over patents that might or might not be held valid, or do you think they'd rather let the current confused atmosphere of FUD contintue?

    3. Re:good new for MS users by sumdumass · · Score: 1

      Sure, they would want to current FUD atmosphere to exist. It does more for them then actually winning a case does. Now they can say, Look, See how viral the GPL software is, we aren't even using it and they are trying to poison our rights to personal property. And the GPLv3 crowd is sitting there going, yea, take that, we fucked your day didn't we.

      Yep, the FUD factor along is worth more to MS then winning in their position. The only people cheering this and the GPLv3 on are the people and companies currently using it. It would look to be a scary proposition to about anyone who isn't already in the know. And the specific wording of the GPLv3 sets it up to get even worse in the future. This FUD is just only starting to happen. Wait until MS puts some effort behind it or you try to talk yet another manufacturer into releasing something GPLed.

  20. shrinkwrap GPL3? click-through EULA? by Anonymous Coward · · Score: 0

    Microsoft's position seems to be "Hey, you're trying to make us enter into contracts the same we we've been doing it to you for years". I completely fail to see how Microsoft's being "passively" entered into the GPL3 is any different from my "passively" letting the cable/DSL installer guy click through a bunch of EULA terms while installing the Internet. If Microsoft doesn't want to be bound by the GPL3, then I dare say they're setting a precedent that will apply to every piece of click-through and/or shrink-wrap licensing that exists.

    Which means the GPL3 wins, albeit at the cost of making a bunch of IP lawyers filthy stinking rich.

  21. Good. by Dputiger · · Score: 1

    A software license shouldn't be a morality tale.

    1. Re:Good. by russlar · · Score: 0

      Hear hear!!!

      --
      Anybody want my mod points?
    2. Re:Good. by vux984 · · Score: 1

      Get over it.

      *All* software licenses are morality tales.

      Whether its released into the public domain, the GPL, the BSD, or under a proprietary license.

  22. Aren't GPL3 patent changes aimed more at Novell? by Karellen · · Score: 1

    Uh, I thought that the patent provisions in GPL3 were more to do with preventing the Novell side of the deal happening - Novell is effectively prohibited from entering it's side of the bargain. After all, they're the one distributing other people's GPL3'd code.

    Or did I miss something?

    --
    Why doesn't the gene pool have a life guard?
  23. A waste of time and effort! by Anonymous Coward · · Score: 2, Insightful

    Regardless of the FSF's intent, this whole GPLv3 episode has been very disruptive within the OSS community.

    Many top developers, including Linus, have wasted many an hour discussing (or arguing) the merits of the GPLv3. But while that was happening, they weren't coding. Spread over a large number of OSS developers, that's a major waste of time and effort.

    1. Re:A waste of time and effort! by Anonymous Coward · · Score: 1, Funny

      Even worse: imagine all the time they've spent eating, sleeping, bathing, having sex, talking to their friends and families.... This whole "humanity" thing is a waste of time and effort, we must do something about it at once, before it disrupts the OSS community even further!

    2. Re:A waste of time and effort! by Anonymous Coward · · Score: 0

      sleeping, bathing, having sex, talking to their friends
      Cmon, these are geeks and /.-goers we're talking about here! Everybody knows they live off of intravenous caffeine injection, don't bath, friends are out of the question, and geeks having sex is against the laws of physics!
  24. I'm still not affected by HalAtWork · · Score: 1

    Microsoft doesn't have to have anything to do with Linux for me to use it, so regardless of what they do I'm not even affected. That's the beauty of using Linux!

  25. Irrelevant by sveinhal · · Score: 1

    Microsoft must redristribute GPL v3 licensed software in order to be bound by that license. As far as I can tell, no software is redistributed by Micorsoft under GPL v3. So why would it apply to MS?

    Microsoft is free to drag people to court over patent issues, if they feel their rights have been violated, even if those alleged violations are in GPL v3 software. Only those that either uses, copies or redistributes the GPL software are bound by its license. Not MS.

    Am I missing the point?

    1. Re:Irrelevant by Anonymous Coward · · Score: 0

      Indirect distribution is covered in GPL2 and recognized by the courts (eg: "materially contribute to infringement" - Napster). The FSF made this even more explicit in GPL3 by using the concept of conveyance. Microsoft vouchers aren't a get-out from contributory infringement, therefore they must adhere (or permit the directly distributing party to adhere) to terms contained within a copyright license. Microsoft wouldn't want it to fly any other way in court, their own business model would be in jeopardy.

      The point you're missing then is that Microsoft punched themselves in the balls - hard.

    2. Re:Irrelevant by vga_init · · Score: 1

      As far as I can tell, no software is redistributed by Micorsoft under GPL v3. So why would it apply to MS?

      That's precisely how they're planning to "evade" it. :)

    3. Re:Irrelevant by VGPowerlord · · Score: 1

      Indirect distribution is covered in GPL2 and recognized by the courts (eg: "materially contribute to infringement" - Napster). The FSF made this even more explicit in GPL3 by using the concept of conveyance. Microsoft vouchers aren't a get-out from contributory infringement, therefore they must adhere (or permit the directly distributing party to adhere) to terms contained within a copyright license. Microsoft wouldn't want it to fly any other way in court, their own business model would be in jeopardy.

      The point you're missing then is that Microsoft punched themselves in the balls - hard.

      IANAL

      US Title 17 Section 109 says that reselling a legitimately made copy doesn't require additional rights from a copyright owner. In other words, they don't have to agree to the license to resell copies of software containing GPLv3 code.

      Of course, Microsoft bringing this up in a court of law would shine a big light onto their Office and Windows licenses, which they really don't want. It would bring to light that Microsoft's activation scheme is in itself illegal by sections 109 and 117 of US Title 17.
      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  26. Licenses aren't changing after the fact by achurch · · Score: 1

    The problem Microsoft (potentially) faces isn't that it suddenly won't be able to distribute certain software; that very "or any later version" ensures that Microsoft can continue to apply GPL2 to their distribution of the software, no matter how much the author might wish otherwise. The problem occurs when new versions of such software are released, because with a new version, the author can change the license freely (since nobody has a copy of it yet). Once this happens, at least according to the GPL3-owns-Microsoft camp, Microsoft will be faced with a dilemma: either it has to accept the GPL3's terms, or it has to stay with the old, GPL2 software, which will no longer be updated unless Microsoft does so itself.

    1. Re:Licenses aren't changing after the fact by that+this+is+not+und · · Score: 1

      No. The 'or any later version' just throws ambiguity into the license. The GPL2 License ensures that Microsoft can continue to apply GPL2 no matter what further happens. Why would the 'or any later version' clause have anything to do with this other than to potentially weaken their rights??

    2. Re:Licenses aren't changing after the fact by Fuzzy+Eric · · Score: 1

      Nope. No ambiguity is introduced. The "or any later version" clause allows subsequent distributors to bump the version of the license that they subsequently distribute under. For instance, source contributed to the Samba project under "v2 or later" can be distributed *in* Samba under "v3", "v4", "v3 or later", or other similarly phrased terms.

  27. Not news by Fjodor42 · · Score: 1

    Not only is MS not bound in the case of the MS-Novell deal, but isn't this deal specifically "grandfathered in"? Wasn't this some of the larger news about the last (or last few) revision(s) of the draft, leading to the final license? /F

    --
    "The number you have dialed is imaginary. Please rotate your phone 90 degrees and try again."
  28. Re:This may betray some sort of ignorance on my pa by FishWithAHammer · · Score: 2, Funny

    be willing to sleep with the devil Hey, why's BSD being dragged into this...?
    --
    "You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
  29. Microsoft would never be caught up in this anyway by Kjella · · Score: 1

    ...unless they distributed GPLv3 software themselves. Whatever Novell does or doesn't do can't bind Microsoft. A voucher to get software from Novell isn't distribution by Microsoft. The ones that could get stuck in the middle is Novell, if a court finds that it can't simultaniously satisfy the GPLv3 and its agreement with Microsoft. That would force Novell to refrain from distributing at all, which would practicly be a death sentence.

    --
    Live today, because you never know what tomorrow brings
  30. Groklaw covered this by mad+zambian · · Score: 1

    .. a while back. here
    Just 'cause M$ say it isn't covered by GPL3 doesn't necessarily make it true.
    PJ has, as ever, done a thoughtful piece.

    --
    Trying to associate Microsoft with "fun" is like trying to associate Satan with aromatherapy. -Tycho
    1. Re:Groklaw covered this by tkinnun0 · · Score: 1

      But those pesky vouchers with no expiration date.... the saga is not yet over. So, let's just say, to be continued.
      FUD, anyone?
    2. Re:Groklaw covered this by harlows_monkeys · · Score: 1

      PJ has, as ever, done a thoughtful piece

      You've mistaken long for thoughtful.

  31. Obviously MS hasn't violated* the GPLv3... by mrchaotica · · Score: 1

    ...yet.

    This is because it, as far as I know, haven't distributed (or "conveyed") any GPLv3 code to anyone redeeming a voucher. It's plain common sense that the GPLv3 doesn't apply to any vouchers redeemed for GPLv2 code.

    However, what the license does prevent is Microsoft "conveying" any GPLv3 code for those vouchers in the future -- an action which Microsoft has full control over. When people talking about the FSF screwing over Microsoft, they're talking about the fact that Microsoft is forced to do one of the following:

    • Refuse to redeem any more vouchers
    • Redeem the vouchers for obsolete (i.e., the last GPLv2 version) software, or
    • Redeem the vouchers for GPLv3 software and thus be forced to give zero-cost, transferable and sublicensible patent licenses to all comers

    Obviously, none of these options are as palatable compared to what Microsoft would prefer to do, which would be to release the newest versions of the software with submarine patent mines, in order to extort license fees from Free Software (which would effectively kill it).

    If Microsoft can successfully redeem the vouchers for GPLv3 software and without giving away its patents, then one could say it had "evaded" the GPLv3. Otherwise, this lawyer is an idiot.

    (* let "violating the GPL" be defined as shorthand for "failing to abide by the terms of the GPL, thus rendering it void and causing the distributor to violate copyright law.")

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    1. Re:Obviously MS hasn't violated* the GPLv3... by Courageous · · Score: 1


      I wasn't under the impression that Microsoft currently conveys, or plans to convey, any GPL based code at all. Are you saying they do? If so, I agree with your analysis.

      If you're not saying that they do, I disagree with you. Microsoft has no agreement with any GPL holder, and the GPL3 cannot come back to haunt them, except to prevent them from distributing GPLv3 software.

      Now, the GPLv3 can haunt Suse very easily. That's a different matter.

      C//

    2. Re:Obviously MS hasn't violated* the GPLv3... by Anonymous Coward · · Score: 0

      > I wasn't under the impression that Microsoft currently conveys, or plans to convey,
      > any GPL based code at all. Are you saying they do? If so, I agree with your analysis.

      Did Napster convey music? Microsoft crafted the Novell deal specifically as a workaround for section 3.7 of GPL2 and were even foolish enough to publicly beat their chest over it.

      If Novell distribute under GPLv3 or Novells "patent deal" customers distribute GPL2 code under GPL3; Microsoft are guilty of inducement, contributory and vicarious infringement. That's before we even get to the testable language of the GPL itself - which Microsoft has publicly admitted to studying intently.

    3. Re:Obviously MS hasn't violated* the GPLv3... by Anonymous Coward · · Score: 0

      If Novell distribute under GPLv3 or Novells "patent deal" customers distribute GPL2 code under GPL3; Microsoft are guilty of inducement, contributory and vicarious infringement.

      That's just silly, in a sort of especially hallucinatory fashion.

    4. Re:Obviously MS hasn't violated* the GPLv3... by jbengt · · Score: 1

      The sale of vouchers for Novell software is conveying and/or propagating the software, and under US law may be considered as distribution. There's a good chance that MS has already, under GPL2, waived their right to sue Gnu/Linux users over patents covering Gnu/Linux.

    5. Re:Obviously MS hasn't violated* the GPLv3... by Courageous · · Score: 1


      Interesting claim. Explain. Part of the problem is I've never seen one of these "vouchers".

      C//

    6. Re:Obviously MS hasn't violated* the GPLv3... by mrchaotica · · Score: 1

      I wasn't under the impression that Microsoft currently conveys, or plans to convey, any GPL based code at all. Are you saying they do? If so, I agree with your analysis.

      At least part of the reason the GPLv3 uses the term "convey" instead of "distribute" is that "convey" is intended to cover situations such as issuing vouchers to be redeemed by a third party.

      If you're not saying that they do, I disagree with you. Microsoft has no agreement with any GPL holder, and the GPL3 cannot come back to haunt them, except to prevent them from distributing GPLv3 software.

      If the "convey" language holds up, then Microsoft could become subject to the GPL if any vouchers get redeemed with GPLv3 code. If it doesn't hold up, then Novell would be in violation of the GPLv3 for releasing code without a correspondingly "viral" patent license.

      Now, the GPLv3 can haunt Suse very easily. That's a different matter.

      Oh yes; either way, Novell is rather screwed (either by violating the GPLv3, being unable to fulfill its agreement with Microsoft, or being stuck maintaining GPLv2 forks of everything).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Obviously MS hasn't violated* the GPLv3... by Courageous · · Score: 1

      If the "convey" language holds up, then Microsoft could become subject to the GPL if any vouchers get redeemed with GPLv3 code. If it doesn't hold up, then Novell would be in violation of the GPLv3 for releasing code without a correspondingly "viral" patent license.

      I don't see how. Microsoft is not a signatory to any GPLv3 agreement. The GPL relies first on ordinary copyright law in order to acquire its legal power, only becoming a contract second, by becoming the one thing the party can depend on to claim that they weren't illegally creating or distributing a derivative work. The definition of "distribute" here is one left to congress to define, or the courts to interpret, as the case may be, according to the copyright laws of the US, not any contract. Since Microsoft does not make or distribute any derivative works of any GPL work, I don't see how the contractual terms can apply.

      I recently went to the trouble of reviewing various web sites where this has been talked about at length. There are some claiming that the vouchers either A) constitute a form of distribution, or B) are "contributory infringement" of the same, ala Napster.

      I don't understand Claim A at all, and would love to hear coherent argument about how that could be, and Claim B will be rather weak, it is certain, as the concept of "contributory infringement" is itself quite new and rather murky indeed.

      And as I said previously, there are plural doctrines of jurisprudence and centuries of judicial interpretation that argue wholesale against the idea of an obscure boo boo suddenly requiring a large company to surrender vast swaths of its property in response to an accident of paperwork. I will summarize them here: "that wouldn't be fair or equitable."

      Deep down in their chests, as much as the community doesn't like Microsoft, if one cannot see my summary to be true, one needs to go off into deep contemplation for a while.

      C//

    8. Re:Obviously MS hasn't violated* the GPLv3... by jbengt · · Score: 1
  32. The license as a sword for an opponent by icepick72 · · Score: 3, Insightful

    It sounds like some people are intending to use the GPL3 to target Microsoft. As soon as the GPL becomes a tactic rather than a license you're playing a stupid game. Then you have to start writing into it piece to try to blunt everything else every other company comes up with that is not desirable. It's a losing game because it's never ending.

  33. Yeah, I don't get what their point is either. by pavon · · Score: 1

    Sure the GPLv3 does not apply to Microsoft unless they distribute software that is licensed under it. The purpose of the new patent clauses were never intended to directly hamper someone like Microsoft, but rather prevent someone like Novell from making similar deals in the future. Now it may or may not do a good job at that, but the article didn't even get into that issue, instead pointing out a bunch of facts that are both irrelevant and well known to those who followed the GPLv3 drafting process. Pretty worthless analysis (or at least worthless reporting).

    PS. Yes the Novell deal,and any other deals prior to 28 March 2007, were grandfathered in - see the second to last paragraph in section 11.

  34. A license is a contract, moron by Anonymous Coward · · Score: 1, Insightful

    A contract is an agreement between two or more parties.

    Thus, a license is a contract, but a contract is not necessarily a license. I may not be a lawyer, but I -do- have access to a dictionary.

    You are also spewing some nonsense about copyright, which doesn't belong there either: not abiding the terms of a license has nothing to do with copyright law.

    It's really amusing that all the best FOSSie minds in the world just started crying because the GPLv3 they just custom crafted in order to specifically attack Microsoft doesn't amount to anything. It seems like FOSSies losing out to Microsoft is kind of a universal theme, like Cobra's schemes always losing out to GI Joe.

    1. Re:A license is a contract, moron by neomunk · · Score: 1

      Personally I think it's even MORE amusing watching the army of ACs who like to be derisive of FOSS software come out all of the sudden with the position at licenses don't REALLY matter after all.

      Where are all the Kerry bashers with the flip-flops when you need them?

    2. Re:A license is a contract, moron by Anonymous Coward · · Score: 0

      You are also spewing some nonsense about copyright, which doesn't belong there either: not abiding the terms of a license has nothing to do with copyright law.

      Where Microsoft gets caught is that the GPL (all versions) gives you more rights than copyright law does. If you overturn the license you then revert to copyright law and have no right to distribute. If you are not bound by the GPL then you are instead bound by the much more stringent laws of copyright with very harsh penalties for illicitly distributing.

      The SCO Group tried to claim that the GPL (2.0) was invalid, that left them with no right to distribute code essential to their operations (Samba, GCC etc) and they had to backpedal quickly.

    3. Re:A license is a contract, moron by Anonymous Coward · · Score: 0

      And haven't I seen wording, by a company convicted of abusing a monopoly, that changes PAST contracts they have made, just by a user continuing to use the software. Now, it seems, that sort of thing isn't allowed.

      I proudly admit I'm neither a lawyer, nor wish to be one, but AM a human being, and am somehow able to recognize what's ethical and what isn't.

      And, if one believes in a just god, so does God.

    4. Re:A license is a contract, moron by ClosedSource · · Score: 1

      As has been discussed before, there's no guarantee that the GPL will be held 100% enforceable or 100% unenforceable. Thus some terms of the license could be held unenforceable without triggering a copyright effect. Not a likely scenario, but a quite possible one.

    5. Re:A license is a contract, moron by jbengt · · Score: 1

      A license is a grant of permission for use or waiver of the right to sue. It can be considered as a one-way deal. Though it is usually granted as part of a contract, there is considerable debate about whether it by itself should be considered an agreement of two parties, i.e. a contract.

      Not abiding by the terms of the license shouldn't mean anything about using the software (MS may disagree), but if you don't abide by the terms of the license, you don't get the waiver of the right to sue for copyright infringement, and so you can't copy or distribute the software or any derivatives.

      The GPL3 doesn't affect MS unless MS copies, modifies, or distributes software published under the GPL3. If they do, then they either agree to the conditions or they can get sued for copyright infringement. My guess is that under many conditions they would be more willing to pay the costs of losing a copyright suit than abide by the GPL3. It won't be clear that they get off the hook for automatic patent licences and the like until court cases and appeals create precendents.

      And the GPL3 was not custom crafted to specifcally attack Microsoft. It was specifically crafted to increase protections against patent attacks and to prevent companies like Tivo from avoiding the intent of the license.

    6. Re:A license is a contract, moron by gbutler69 · · Score: 0

      The GPL3 doesn't affect MS unless MS copies, modifies, AND distributes software published under the GPL3. If they do, then they either agree to the conditions or they can get sued for copyright infringement. My guess is that under many conditions they would be more willing to pay the costs of losing a copyright suit than abide by the GPL3. It won't be clear that they get off the hook for automatic patent licences and the like until court cases and appeals create precendents.

      There, fixed that for you! Important to remember. The GPL ONLY only applies when you MODIFY AND COPY AND DISTRIBUTE (the last being the really key point). You must make modifications AND distribute them in order to be bound by the terms of the GPL.

      Stop spreading FUD!

      --
      Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    7. Re:A license is a contract, moron by Skreems · · Score: 1

      No. It applies when you distribute copies. And Novell/SuSE is distributed digitally, so it's distributing copies by definition. It gives you the ADDED right to make modifications, but make no mistake, the GPL is the only thing that allows you to make copies of GPL-licensed software without infringing on the creator's copyright.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    8. Re:A license is a contract, moron by wish · · Score: 1

      IANAL either but I believe a license is a unilateral grant of rights. No agreement from the recipient is necessary since they are not giving anything up. A license agreement on the other hand is a contract you have to agree to in order to receive a license. Neither of the GPL licenses has an agreement associated with it as they are formulated as a bunch of permissions to do things normally forbidden by copyright.

    9. Re:A license is a contract, moron by grahammm · · Score: 1

      The GPL ONLY only applies when you MODIFY AND COPY AND DISTRIBUTE (the last being the really key point). You must make modifications AND distribute them in order to be bound by the terms of the GPL. NO! The GPL applies if you COPY (either the unchanged work or a modification of it) OR DISTRIBUTE. In the absence of the a licence (GPL) allowing these, 'standard' copyright law applies. If, for example, a company buys a single copy of a print of a painting they would not be allowed (without specific permisson/licence from the copyright owner) to make copies of that print and hang one in every office. Similarly with software, in the absence of a licence all you are allowed to do is run the single copy. The GPL gives conditional permission to copy the original or create a modified copy and to distribute those copies. If these conditions are not met, then you are not allowed to make copies and you need to make copies in order to distribute.
  35. re Lawyer "claims" by jelizondo · · Score: 1

    Lawyers never quite commit themselves, therefore this lawyer "claims" to think that...

    News at 11

    --
    Be very, very careful what you put into that head, because you will never, ever get it out. - Cardinal Wolsey
  36. Re:Microsoft would never be caught up in this anyw by furball · · Score: 1

    So what's the point of GPLv3? To make sure that companies that sells Linux software are doomed?

    Fill me in. I'm not up to date on this stuff.

  37. read the gpl! by SolusSD · · Score: 1

    These lawyers act like they haven't read the damn gplv2 and v3. Its VERY clear that any customer that wants to use the gplv3 license *instead of* the gplv2 has that right-- and it was granted in gplv2.

    1. Re:read the gpl! by sumdumass · · Score: 1

      It was only granted in limited circumstances and the original author has the ability to deny letting it move to a later version when the project starts. After that, it would take all contributing copyright holders to make the switch or deny the switch. In the case of turning it isn't a GPLv2 only project, anything released before the switch can be changed.

    2. Re:read the gpl! by phantomlord · · Score: 1

      The "or later version" text is in the recommended use section of the GPL license file; It is very much outside of the terms and conditions of the license. You cannot convert GPL2 code to GPL3 code unless the software is specifically licensed under "GPL2 or any later version." It is precisely that reason that the Linux kernel cannot go to the GPL3 even if Linus wanted to without a lot of code having to be replaced.

      If you're worried that future versions of the license can cause problems, the best thing to do is to license your code under a specific version (or versions) that you agree with rather than giving a third party that you don't control the power to control the license of your software. If you're so sure of your position, change the license on Linux to GPL3 tomorrow and distribute it... I'm sure several kernel authors will send you some nasty letters threatening to see you in court if you don't immediately cease your actions.

      --
      Don't leave your mind so open that your brain falls out. Don't close it so much that you cut off the blood.
  38. Enough with this bullshit by Anonymous Coward · · Score: 0

    > A voucher to get software from Novell isn't distribution by Microsoft.

    Then centralized p2p file services such as (hint) Napster must be legal?

    GPL2 covered indirect distribution, GPL3 makes it even more explicit. Are you arguing that I can legally sell vouchers for Windows support containing a URL to an offshore download site? Is this what Microsoft are arguing?

    1. Re:Enough with this bullshit by sumdumass · · Score: 1

      Are you arguing that I can legally sell vouchers for Windows support containing a URL to an offshore download site? Is this what Microsoft are arguing?
      If the offshore download site is legally allowed to give out the distributions and you have an arrangement with them giving you access then Yes, you can.
  39. What's the big deal ? by Joebert · · Score: 1

    I read through the GPLV3 & it looks like just about any other license, what's so different about V3 that it would be such a large problem for Microsoft ?

    What does it say Microsoft would have to do, that Microsoft doesn't want to do ?

    --
    Wanna fight ? Bend over, stick your head up your ass, and fight for air.
  40. how absolutely silly this lawyer is,,,, by 3seas · · Score: 1

    its a license. Acceptance is done by using the software, distributing it, etc..

    MS is certainly bound by it, in the event they use it.

    There is no sort of entrapment as MS most certainly had the same opportunity to know what was developing with version 3 of the GPL as everybody else. Its not like t happened over night. It was a rather long process.

    If there was an argument to be had, and there is not, that MS was being entrapped by this change then it could as well be argued that MS intentionally sought agreements with Novel, or anyone they could find that was a klinux distributor with backing, to try and void itself from needing to comply with the license change.

    And in a court case it, that will never happen, it would certainly be brought forward that MS uses unvalidated threats against others to motivate them to pay MS extortion money for the use of teh product of MS competition to MS.

    It is obvious the MS intends to pursue the application criminal activity on their part.

    It should be clear that the article is really nothing more than typical MS distortion of facts.

    If there was a scale to show the believe ability of MS and MS supporting news and announcements, wouldn't the scale show a continued drop with this FUD?

    My distaste for MS continues to increase.

  41. Software Freedom Day by SpaceLifeForm · · Score: 1

    I wonder how they picked September 15th?

    I picked January 11 because that was the day
    that IBM threw down the gauntlet regarding software patents
    to counter the Microsoft FUD.

    Plus 1-11 has that nice binary look.

    Anyway, every day is Software Freedom Day when you
    kick the Microsoft software addiction.

    --
    You are being MICROattacked, from various angles, in a SOFT manner.
  42. AUSSIE LAWYER HAS NOT READ THE BLEEDING GPL3! by argent · · Score: 2, Informative
    The "leading IP lawyer in Australia" has obviously not actually studied the document:

    "'I would be very surprised to see this upheld. It was a nice try on the part of (the FSF), but at this stage, I'd say it's not going to be an effective strategy. It will be tough to hold up in court.' In this case, she said, Microsoft never acted -- never 'entered' into the agreement, and the terms and conditions can only apply to new actions by Microsoft, not older ones. She said: 'Their actions so far are not enough to say that they are bound.'"
    That is: Microsoft's *existing* agreement is immune to the GPL3 because it took place before the GPL3 was finalized.

    Yes. That's correct. So what? WE ALREADY KNOW THIS. That's why the GPL3 contains THIS language: "You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007."

    Not only that, but the GPL3 doesn't actually cover any of the software that Novell is currently shipping... it's all GPL2.

    The "great insight" here is that the GPLs can't do something that it explicitly does not try and do, regarding software it doesn't even cover!

    Sheesh.
    1. Re:AUSSIE LAWYER HAS NOT READ THE BLEEDING GPL3! by Alex+Belits · · Score: 1

      That exemption applies to Novell (who is subject to Microsoft's terms) but not Microsoft (who dictates the terms of the patent agreement). Microsoft still conveys SUSE Linux (of whatever version that vouchers are applied to) and is a subject to its components' licenses.

      --
      Contrary to the popular belief, there indeed is no God.
    2. Re:AUSSIE LAWYER HAS NOT READ THE BLEEDING GPL3! by argent · · Score: 1

      Microsoft isn't distributing Linux. The only GPLed software Linux distributes is in Interix.

      What Microsoft might distribute in the future isn't relevant to the argument that the FSF was trying to "back date" the GPL3. That didn't happen.

    3. Re:AUSSIE LAWYER HAS NOT READ THE BLEEDING GPL3! by Alex+Belits · · Score: 1

      Not in US law. Issuing vouchers is a part of distribution.

      --
      Contrary to the popular belief, there indeed is no God.
  43. Then the patent troll sues microsoft? by walterbyrd · · Score: 1

    Even if that would work, do you think msft wants to give their patents away? Not long ago, a patent troll that owned a tiny part, of a part, of a process sued msft for $1.5B. Msft would be taking one helluva chance giving their patents away.

    If msft had some sort of contract with the patent troll, then it could be argued the the the patent troll doesn't really own the patent.

    1. Re:Then the patent troll sues microsoft? by paulpach · · Score: 1

      The Patent troll does not have to own the patent. For example, Microsoft can grant them a license that allows the patent troll to do these deal and then forward the money to Microsoft with a small percentage staying with the patent troll.

      Heck, Microsoft can create another company just for this purpose. It would not be hard to get around the GPLv3 with that language.

      Leave aside Microsoft for a minute. The GPLv3 does nothing to protect against future threats, as long as the threatening companies does not distribute software. It focuses so much on Microsoft, that it leaves the door open to any other company outside of the software distribution business.

    2. Re:Then the patent troll sues microsoft? by domatic · · Score: 1

      Many here are saying the GPLv3 can't be used to ambush MS (Novell/SuSe on the other hand....) but I suspect using a patent troll as proxy won't necessarily fly in court either. MS would at least be taking a serious risk with such a tactic.

  44. More of a shield than a sword by walterbyrd · · Score: 1

    GPLv3 is a defense against msft's under-handed tactics. Msft has always been the antagonist - not just against Linux but the entire industry.

    1. Re:More of a shield than a sword by that+this+is+not+und · · Score: 1

      That's a ridiculous assertion. Microsoft wasn't even on the radar screen as a major opponent when Stallman started the GPL movement. There were and are many other commercial software vendors who are and were 'the antagonists.'

      Come back and comment again when you've gotten a clue and are not just 'anti-Microsoft' more than anything else. There's a big world out there and taking 'anti-Microsoft' as your credo just reveals you as a narrow crank.

    2. Re:More of a shield than a sword by Anonymous Coward · · Score: 0

      Just for fun I peg you as being born in the 80s. Is this true?

    3. Re:More of a shield than a sword by Anonymous Coward · · Score: 0

      I was betting 90's.

  45. "GPLv3 + coupon expiration date" = CounterFUD by anwyn · · Score: 1
    The GPLv3 + coupon expiration date theory is not intended to be taken seriously by any court. It is counterFUD.

    Eben Moglen is a very smart lawyer. However, he was the General Counsel to the Free Software Foundation, and the FSF is at war with Microsoft. In any war the fist causality is truth. Eben Moglen is running a bluff, but he knows his bluff can not be called.

    I order for the bluff to be called, Microsoft would have to try to enforce one of its bogus patents. Microsoft will never do that because it would expose the patent to scrutiny. Moglen is proceding on the theory that "one good lie deserves another" and "any stick is good enough to beat a mad dog with". The theory is designed to appeal to unthinking suits and PHBs, the kind that could be fooled by Microsoft patent FUD.

    Unfortunately some free software advocates have started "breathing their own exhaust fumes" and started believing this preposterous theory.

    This counterFUD move may be a brilliant tactical move, but it may be in the long run counter productive, because people like PJ destroy their own credibility by slavishly following it.

  46. That raises another question... by SanityInAnarchy · · Score: 1

    Could the FSF possibly have done better than they did?

    I'm not sure we'd want them to have it retroactively apply, but for her to say "it's not going to be an effective strategy" sort of implies that there might be an effective strategy somewhere.

    --
    Don't thank God, thank a doctor!
  47. The real anti-MS weapon by Anonymous Coward · · Score: 0

    Everyone keeps hoping some little thing here or there will help Linux or hurt M$, but FOSS really needs to develop a killer instinct.

    I'm so sick of hearing things like "if you don't like it, use Windows" or "50 different ways of doing it are good for the community." Until GNU/Linux starts seriously targeting average customers, Microsoft will always find ways of keeping it check. Enough man-hours have gone into it, so why are so many things still only half-done?

    I use Ubuntu about 30% of the time, but it still drives me nuts.

  48. There is a thing called "courts" by Danathar · · Score: 1

    And in these courts there are people with jobs and they are called "lawyers". Each "Lawyer" puts forth a view contrary to their opponents.....

  49. The Shackles of Freedom by nacturation · · Score: 0, Troll

    Regardless of what it is, it strikes me as rather ironic that this supposedly free software license is considered so shackling and restrictive that companies will do anything to escape it.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    1. Re:The Shackles of Freedom by Anonymous Coward · · Score: 1

      The Microsoft EULA and the way they try to control my computer to my detriment is driving me to Linux. For myself the GPL is far less of a shackle than is the Microsoft EULA.

      This shackle as you call it only seems to bother those who want to take other peoples code and make it proprietary without agreement to do so. Why should they not be shackled that way? They have no right to the code that is not given to them by the license (the GPL in this instance). If they don't want to be members of the GPL using community then they only need to not use code released under the GPL, easy actually. To be affected by this shackle they have to willingly don it. What is so bad about that?

    2. Re:The Shackles of Freedom by aztektum · · Score: 1

      I think that speaks more to the greedy nature of those companies than the majority of people that stand behind the GPL

      --
      :: aztek ::
      No sig for you!!
    3. Re:The Shackles of Freedom by caseih · · Score: 4, Insightful

      How this got rated insightful, I will never know, because it is not. A couple of points.
      First, Free Software under the GPL is certain free for you to use in any way. You can even embed GPL'd software in your embedded rocket flight control computer if you want. Microsoft can *use* GPL'd software in any way they see fit. In fact Microsoft has entire labs full of Linux machines (they believe that one should know one's enemy). Contrast this with Windows, which is not free for me to use in any way I see fit. I cannot run it under certain Virtual machines, I cannot install it on more than so many computers (as provided by the EULA). In contrast, GPL'd software has no EULA; there are *no* restrictions whatsoever on its use.

      Second, there are restrictions on *redistribution* of the code, though, as there should be.

      What you are saying is pretty silly. If I downloaded a copy of MS's source code from somewhere and tried to redistribute it, you wouldn't say that I am shackled when copyright law does not allow me to do so. GPL'd software is the same. Without the terms of the GPL I have no rights to modify and distribute the source code at all! How the GPL shackles my existing non-rights to distribute copyrighted code that I don't own, I will never know. For without the GPL, I cannot distribute the code to others, and others cannot distribute the code to me!

      Seems to me that the GPL ensures freedom in a couple of ways. It ensures that I can use the code freely for any purpose, even without agreeing to the terms of the license at all! Also it ensure that as the author of GPL'd code, my code will never be stolen from me against my will, and sold back to me with restrictions on its use.

      So let's stop right now with this nonsense about the GPL shackling freedom.

    4. Re:The Shackles of Freedom by Vexorian · · Score: 2, Insightful

      I want you to give us all this irony-free-freedom you are talking about, now that I got freedom I will use my freedom to lock you into a room and not let you go out ever again.

      Or ... we could implement true freedom which would prevent anyone from removing freedom from others.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    5. Re:The Shackles of Freedom by nacturation · · Score: 1

      The jaded version of news that I see on Slashdot presents GPLv3 as a device that can be used to trap Microsoft. I'm sure it stands on its own as a fine license, but the way it's presented here it appears to have been designed specifically as a type of poison pill for certain organizations.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    6. Re:The Shackles of Freedom by Ohreally_factor · · Score: 1

      Rockets! What a great hypothetical example to show one of the areas where GPL 3 really bites. Let's say that I build and sell rockets to the serious hobbyist market. These rockets are controlled by free software, but for safety reasons (and possibly liability) I've locked out unsigned software in the firmware. Can't use GPL software for my toy rockets.

      This is the sort of unintended consequence we get from the GPL 3 reaching past being a software license, and in effect trying to control hardware. According to the FSF, if I take measures to prevent my users from weaponizing my toys, I'm bad because everyone should have the right to weaponize whatever free software touches.

      Rather than repeat the success of the GPL 2, the FSF has made the mistake of trying to go after specific companies they don't like, not giving a damn about unbalancing the fairness of the license, and not caring about who they might hurt if that helps them "get" Tivo or MS. They've moved from principles and are operating on personalities.

      --
      It's not offtopic, dumbass. It's orthogonal.
    7. Re:The Shackles of Freedom by Ohreally_factor · · Score: 1

      To the extent that it is based on the GPL 2 and is a natural progression of the GPL 2, it's a great license. The GPL is an elegant legal hack that uses the power of copyright to enforce "copyleft". Part of it's moral strength comes from it's quid pro quo nature: Tit for tat, code for code. The GPL 3 is a kludge that goes beyond dictating the terms of software distribution and reaches into how hardware may be designed.

      --
      It's not offtopic, dumbass. It's orthogonal.
    8. Re:The Shackles of Freedom by init100 · · Score: 1

      I find it quite natural that those hobbyists would want to tinker with the software. That you think that this shouldn't be possible (except for yourself) is quite strange to me. The talk about weaponizing the toys is just the ordinary terrorism scare tactic, so try better next time.

      If you want to lock down software, don't use software licensed under the GPLv3. It is certainly not an unintended consequence that you are not allowed to do so. It is one of the main points that the new version addresses that the old one didn't. If you don't like it, go write your own software.

    9. Re:The Shackles of Freedom by Alex+Belits · · Score: 1

      Stop the hate and recognize this is a company that's trying to preserve its own self interest. That's it's job in a capitalist society.

      At this point the only useful job it can do is to die. Everything else would hurt everyone else, so why should I care for the well-being of everyone's enemies?
      --
      Contrary to the popular belief, there indeed is no God.
    10. Re:The Shackles of Freedom by Anonymous Coward · · Score: 0

      Important (and somewhat unrelated to issue of software freedoms) consequence of that line of reasoning is "safety mechanisms should always be designed and implemented hardwired, carved in stone and black-boxed".

      In other words, safety modules should be held separate from the rest, well tested, with well defined interface, positioned in the system so that they cannot be circumvented and they should be non-reprogrammable.

    11. Re:The Shackles of Freedom by obeythefist · · Score: 1

      MS uses the Linux environment for interoperability purposes. Sadly one of Linux's great strengths, openness, is being exploited by MS. It's easy for them to make Windows interoperate with Linux (you can do NFS mounts on Windows Server 2003 R2 for example, I found doing that far easier than trying to mount an NTFS5/SMB share from Windows Server from Ubuntu).

      Trying to get Linux to interoperate with Windows on the other hand is a horrible task because the source for Windows is closed so you can't know exactly what is going on. Apparently they are supposed to open it up a little more because of the EU stuff but as far as I can see it's still a nightmare.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    12. Re:The Shackles of Freedom by willyhill · · Score: 0
      this with Windows, [...] I cannot run it under certain Virtual machines, I cannot install it on more than so many computers [...] For without the GPL, I cannot distribute the code to others, and others cannot distribute the code to me!


      Without your apparent need to use Windows, the EULA or any other restrictions would not apply, so I don't see what the huge difference is with Linux or the GPL. I think you picked a really bad analogy here, though of course the mods love posts like yours.

      --
      The twitter monologues. Click on my homepage and be amazed.
    13. Re:The Shackles of Freedom by caseih · · Score: 1

      You can surely *use* GPLv3 software in your own rocket, but the moment you want to sell that to others, I believe the phrase is, "if you don't like the license, write your own damn code." Why should you be allowed to sell software you're using when you don't own the copyright, except as allowed by the license?

  50. wrong by doug · · Score: 1

    A license is not a type of contract, at least not in the USA. I'm not sure where you've gotten your legal training, but it doesn't apply here. If you live in a different country with a different legal tradition, you statement might be correct. I can't comment on that.

    Here in the US, if you don't sign something, it isn't a contract (yes, dramatically simplified). A contract is a legal agreement between two or more parties. Each side agrees to do (or not do) certain things and legally bind themselves to fulfill those obligations. Usually one side agrees to perform some action, and the other agrees to transfer money, but the actual mechanism is far more general than that. But the key thing is that multiple parties agree, and sign something that is binding to them. Note that no one else is bound to it, just the signatories (and successors as appropriate).

    A license which is one party holds all the cards an unilaterally allows deviations from the norm for use of something. A license cannot be used to restrict actions, that is what a contract is for, but many licenses have gotchas where you gotta do X if you want to do Y. No obligation, but if you don't meet the letter of X, Y is off limits to you.

    In this case the GNU General Public License (note - not contract) allows copying and use of software that normal copyright law does not. You have to follow the rules of the GPL if you want to use/modify/whatever the covered software. Without the license the use of the software falls under normal copyright laws, which say you can't touch it without the owner's OK.

    Microsoft is completely correct to say that it never agreed to anything GPL. It doesn't matter what they agree to. They are powerless and have no rights what so ever. At square one they cannot touch someone else's software. The only way to move beyond square one is to a) accept the GPL, no matter how distasteful, or b) steal it via copyright violation. They can bitch and moan as much as they like, but the choice is black and white.

    Go visit http://www.groklaw.net/ if you want to research the differences between contracts and licenses. It has lots of the basics, and targets the geek community.

    - doug

    1. Re:wrong by yada21 · · Score: 1

      Here in the US, if you don't sign something, it isn't a contract
      Bullshit.
      --
      I will have a sig when the market demands it.
    2. Re:wrong by nomadic · · Score: 1

      Here in the US, if you don't sign something, it isn't a contract (yes, dramatically simplified).

      That's absolutely wrong. A contract means, basically, a legally enforceable agreement. It can be oral or written, express or implied.

    3. Re:wrong by thethibs · · Score: 1

      You have to follow the rules of the GPL

      "The GPL" doesn't exist. It's GPLV2 or GPLV3—two different licenses that happen to have similar names and were both developed by the Wil E. Coyote of the software world.

      Microsoft appears to be involved in distributing software that includes code encumbered with GPLV2 and appears to have complied with that license. This in no way binds them to anything in GPLV3 and, in fact, they have said clearly that they will not have anything to do with code licensed with GPLV3.

      Wil E. put his trap in the middle of the road and assumed RoadRunner would run straight into it. Predictably, RR took the bypass. OCD messes up your thinking.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
    4. Re:wrong by harlows_monkeys · · Score: 1

      Here in the US, if you don't sign something, it isn't a contract (yes, dramatically simplified)

      Dramatically simplified to the point of having little connection with the law. For starters, just consider the effects of promissory estoppel. The vast majority of legal contracts in the US do not involve a signature.

      Go visit http://www.groklaw.net/ if you want to research the differences between contracts and licenses. It has lots of the basics, and targets the geek community

      Groklaw often has great legal advice--in the anonymous comments from lawyers correcting the errors in the sites articles. Groklaw is a wonderful illustration of why becoming a lawyer requires four years of college and three years of law school and the difficult bar exam, and becoming a paralegal requires a few evening courses at the community college.

    5. Re:wrong by heinousjay · · Score: 1

      And becoming a net pundit requires a heartbeat and a working finger.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    6. Re:wrong by Spazmania · · Score: 1

      A license is not a type of contract, at least not in the USA.

      If you want to get technical about it, the GPLv3 is both a license and a license agreement.

      As a license, its a property (similar to a copyright) which entitles its owner to perform certain actions not otherwise permitted by law, such as making copies of the covered copyright.

      As a license agreement, its a contract tendered by the owners of the copyright which offers a license to any takers provided they agree to the terms.

      Practically speaking, there's no difference. Microsoft has publicly rejected the tendered offer of a license. Accordingly they are neither bound by the GPLv3 nor have they received any rights under the GPLv3. If you think they're using code covered under GPLv3 and own the copyrights, feel free to sue them for copyright infringement. Don't waste your time alleging license violations though... They never accepted the contract which would have conferred a license.

      http://en.wikipedia.org/wiki/Software_license_agre ement

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    7. Re:wrong by ScrappyLaptop · · Score: 1
      "Groklaw is a wonderful illustration of why becoming a lawyer requires four years of college and three years of law school and the difficult bar exam, and becoming a paralegal requires a few evening courses at the community college."

      ...Is it just me or do lawyers live in a different America from the one the rest of us live in? Specifically, if it requires four years of college and three years of law school and the difficult bar exam to understand the laws that govern our society, something is very, very wrong. It is no longer a matter of differences in education, but rather one of diverging societies. My guess, after reading through today's postings for several stories (RIAA, GPLv3, etc.) and the misunderstandings regarding various legal phrases, is that the average citizen (the ones being represented) and the legal system (the ones doing the representing) are fast approaching logical universes with no overlap save perhaps basic traffic laws. And let's face it, those don't even apply to *everyone*.

    8. Re:wrong by harlows_monkeys · · Score: 1

      Specifically, if it requires four years of college and three years of law school and the difficult bar exam to understand the laws that govern our society, something is very, very wrong

      It's not as bleak as it would seem. Law school and the bar exam cover many areas of law. Even if you go into law school knowing you want to be, say, a tax lawyer or a trademark lawyer, you will take civil procedure, criminal procedure, evidence, contracts, torts, property, family law, legal research, and probably a course in legal ethics or professional responsibility. Most of this is stuff that an ordinary person does not need to know to anywhere near the level of detail a lawyer needs it, if at all. For example, I can't think of a time where, as an ordinary person, I've needed to know the details on what constitutes hearsay under the Federal Rules of Evidence and when hearsay is admissible.

    9. Re:wrong by LO0G · · Score: 1

      In addition, it's worse.

      One of the problems is that lawyers are forced to work in an incredibly imperfect language for conveying contracts: English (or whatever the local language is).

      This means that the language that lawyers use is almost a different language than lay people - certain words that have one meaning (like "opinion") mean something very different when a lawyer uses them than when a lay person uses them. In my example, a lay person thinks that an "opinion" is a statement of belief. But to a lawyer, an "opinion" is a statement of how something will be interpreted under the law, based on their fullest understanding (including relevant case law).

      It's very similar to code. English is too inexact a language for computers, you MUST use a separate, more precise language when dealing with something that needs precision.

      It's extraordinarily difficult to use the vernacular when dealing with contracts, the language is simply not exact enough to convey the complete meaning of the contract. Thats where the years and years of training come in.

    10. Re:wrong by ScrappyLaptop · · Score: 1

      So, then, if a different 'language' is in use, a possible conclusion is that the common man or woman has no hope of understanding the laws that govern them. Somehow that just doesn't seem conducive to a fully functional society...

    11. Re:wrong by TekPolitik · · Score: 1

      A license is not a type of contract, at least not in the USA.

      I bet you're regretting posting this given all of the crud it has generated. Now IAAL, and what you say here is basically right - very basically. Your detail is better, but still gets some things wrong. On the other hand a lot of the responses you got are not right either and some seem rather abusive about something that is a lot more complex than they seem to understand.

      "License" is just lawyer-speak for "permission". If you give somebody a "license" you are just giving them permission to do something that would otherwise be a violation of your rights. A license strictly so called never amounts to a contract.

      Where this gets murkier is that most software licenses are designed to give you rights in return for trading away others. If it seeks to restrict rights you already have, then absent a narrow range of exceptions the license will have to also be a contract. While it might be headed up "License", it may attempt to be a contract and in certain circumstances might become one.

      As an example, in Australia under the Copyright Act 1968 (Cth) s47B, a person who has bought a copy of a computer program has the legal right to load it onto a computer and run it for ordinary use. In such a case the user does not need the separate license, and so does not need to rely on or agree to it. But there is a catch - under s47B(2) any license from the copyright holder can revoke this permission. In a well-written license agreement designed for Australian laws one of the first things in the agreement will be an explicit revocation of all implied or statutory rights to the extent permitted by law. You then have to rely on the rights explicitly granted in the license to use the software, and if there are any other terms in that license that take rights away from you or impose obligations on you, your reliance on the license will effectively make it a contract.

      In the US the equivalent statutory right appears in 17 USC 117, but there seems to be nothing corresponding to the Australian provision that allows this right to be revoked by the license. This has some interesting consequences for Microsoft's EULAs in the US (except in the case of multi-user installations from the same media where 17 USC 117 might not apply because making copies on additional systems may not be "an essential step in the utilisation of the computer program").

      In the case of the GPL, however, the whole thing is premised on the fact that the person to be bound is redistributing. This is not covered by the s47B (in Australia) or 17 USC 117 (in the US) statutory rights and would be a breach of copyright if done without a license. You have to rely on the license to redistribute. In the least favourable view to the copyright holder, the license is a conditional one for which, if all of the terms are not adhered to by somebody redistributing the software, the copyright holder could sue for breach of copyright. However the GPL is also reasonably viewed as a contract which you breach by redistributing without adhering to its terms, and in with the grace periods for violations in GPLv3 this may be the preferable view, and if so viewed the copyright holder could sue for breach of contract. The only difference between these approaches is going to be in the amount of damages, and in fact the options for damages in copyright law are generally more favourable to the copyright holder, especially where, as in the case of the GPL, the copyright holder has no damages, which is no doubt one of the reasons the GPL explicitly revokes the right to redistribute as a consequence of breach.

      So in summary, a license is not a contract, but a document that purports to be a license may in fact contain the terms of a contract and the fact that the document is headed "license" will not alter that.

      It is also not true that a signature is necessary to form a contract. You don't even need writing, although lawyers prefer writing and signature because it makes it easier to prove the existence of a contract in a court.

    12. Re:wrong by TekPolitik · · Score: 1

      For starters, just consider the effects of promissory estoppel

      Promissory estoppel is not a part of contract law, although it may be taught in a contract law class and it may have practical results that are similar to some of those arising from a contract.

      The vast majority of legal contracts in the US do not involve a signature.

      True, but promissory estoppel does not come into it.

    13. Re:wrong by TekPolitik · · Score: 1

      I can't think of a time where, as an ordinary person, I've needed to know the details on what constitutes hearsay under the Federal Rules of Evidence and when hearsay is admissible.

      True, although when my wife went to testify in a court case last year I gave her a brief explanation of the hearsay rule. The defendant, who was running his own case, asked her about something that was not within her personal knowledge so she answered "I don't know, you would have to ask them," which elicited a chuckle from the judge and all of the legal practitioners in the room (if she didn't know the hearsay rule, she'd have just said "I don't know", which wouldn't have been nearly as funny).

      I guess you've gotta be a lawyer to see the humour though.

    14. Re:wrong by Anonymous Coward · · Score: 0
      This in no way binds them to anything in GPLV3 and, in fact, they have said clearly that they will not have anything to do with code licensed with GPLV3.

      At the point in time GPLv3 was launched ( recently ), no code could have been licensed under GPLv3 - causality. This is changing right now, as new versions of software will be and IS being licensed under GPLv3 by the copyright holders of the codebase, people and companies. If 12 months from now Apache, samba, glibc, the linux kernel, gnome, kde, and firefox are are all licensed under GPLv3, this will mean that microsoft will do 1 of 3 things -
      • Stop distributing linux distributions entirely as the majority of all distributions depends on GPLv3
      • Distribute only older distribtions that pre-date GPLv3
      • Distribute modern linux distributions that bind Microsoft with GPLv3 stipulations

      Which of these constitute using the 'bypass' to evade the license in a way that harms Linux or GPLv2 or v3 software? There is no bad scenario here. Microsoft will be forced to comply, forced to withdraw, or forced to distribute only older software that is rapidly irrelevant, pointless, and unsupported by the community who have since moved on. And being a laughing stock for doing so. GPLv3 is inexorable as the tides, Microsoft will need to swim or sink.
  51. Microsoft Windows Services for UNIX by tepples · · Score: 1

    As far as I can tell, no software is redistributed by Micorsoft under GPL v3. Yet. How long do you expect Microsoft to maintain private forks of the GPLv2 software present in SFU?
    1. Re:Microsoft Windows Services for UNIX by sumdumass · · Score: 1

      Why would they need to maintain private forks? There are a number of vendor companies who would suffer on the linux side if their products all the sudden stopped working happily with MS stuff. It wouldn't matter what version of the GPL they wanted to use, If MS has the copyright on the services or if those companies wasn't things to work right, they will be forced to help maintain it.

      I don't understand why people don't remember that MS software is what everyone else if playing catchup to. It isn't like MS needs to allow access or help this along.

    2. Re:Microsoft Windows Services for UNIX by Anonymous Coward · · Score: 0

      Why should there be GPL code in it? Why do you think they didn't wrote SFU themselves, licensed it from Sun, or just used BSD code? What's so precious about the GNU reimplementation that Microsoft would want to use it?

    3. Re:Microsoft Windows Services for UNIX by tepples · · Score: 1

      Why should there be GPL code in it? Why do you think they didn't wrote SFU themselves, licensed it from Sun, or just used BSD code? What's so precious about the GNU reimplementation that Microsoft would want to use it? I don't know why Microsoft would want to use "GNU Utils for Interix" and "GNU SDK for Interix", but it did.
  52. ...in Australia by Torodung · · Score: 1

    I find it hard to believe that this "leading lawyer" from Australia is competent to make proclamations any important jurisdictions, such as any state of the United States (especially Louisiana, yikes), where most of these companies headquarter and do business. The U.S. lawyers are wisely keeping their mouths shut pending actual litigation that would provide a real case to evauluate, I should think. They have reputations to worry about, after all.

    Besides, I thought the GPLv3 already exempted the MS-Novell deal as "grandfathered?" If so, this isn't even a legal opinion, it's a summary of exemptions written into the GPLv3. TFA seems primarily concerned with a deal that the FSF has already said is "off limits."

    This article is a waste of time and bandwidth.

    --
    Toro

  53. Check your facts, MS does distribute GPL software by Anonymous Coward · · Score: 0

    Download the MS Services for Unix package, it is chock full of GPL utilities. Freeloaders.

  54. Nah by Anonymous Coward · · Score: 0

    > The GPLv3 + coupon expiration date theory is not intended to be taken seriously by any court.

    Surely it's to be taken seriously as case law?

    You are probably correct about Moglens intent, however the 'theory' is far from toothless. Moglen doesn't need to stoop to the depths of Microsoft FUD campaigns. Case law already covers indirect distribution (conveyance), you just aren't seeing the mechanism. As you know; in a court GPL violators could either accept the GPL or affirmatively plead copyright infringement. I'd like to suggest you read the Napster and Grokster decisions in that context ;-)

  55. -1, Nonsense by chris_eineke · · Score: 1

    The GPL puts user freedom above all. Just because it won't let a company work around a loop hole in v2 doesn't mean it's "getting closer to anti-capitalism." I would call it becoming ultra-capitalistic; more rights and protections for users to resell GPL'ed software.

    --
    "All you have to do is be fragile and grateful. So stay the underdog." Chuck Palahniuk, Choke
  56. MOD UP by maop · · Score: 1

    The lawyer is completely confused about the situation.

  57. indirect infringement requires direct infringement by anwyn · · Score: 1
    In a totally different case, with a totally different fact picture, Capitol Records, Inc., et al., vs Debbie Foster and Amanda Foster, Lee R. West United States District Judge says:

    The Copyright Act does not expressly render anyone liable for infringement committed by another. Metro_Goldwyn-Mayer Studios, Inc. v. Grokster, Ltd.. 545 U.S. 913, (2005). Rather, the doctrine of secondary liability emerged from common law principles. Id. Under those common law principles, one infringes a copyright contributorily by intentionally inducing or encouraging a direct infringement. The elements of a claim for contributory copyright infringement are: (1) direct infringement by third party; (2) knowledge by the defendant that third parties were directly infringing; and (3) substaintial participation by the defendant in infringing activities. See Newborn v. Yahoo!, 391 F. Supp.2d 181, (D.D.C. 2005); see also Newborn v. Yahoo! Inc., 437 F.Supp.2d 1 (D.D.C 2006) (finding defendant was entitled to an award of attorneys' fees after prevailing upon plaintiff's frivolous and objectively unreasonable contributory copyright claim). Merely supplying means to accomplish infringing activity cannot give rise to imposition of liability for contributory copyright infringement. Id.;see also A & M Records, Inc. v. Napster, Inc. 239. F.3d 1004, 1013 (9th Cir. 2001). One infringes a copyright vicariously by profiting from direct infringement while declining to exercise a right to stop or limit it. Grokster, 545 U.S. 913.
    I have copied the above by hand so check the original.

    The judge is basicly saying that indirect infringement requires direct infringement. If this principle were applied to the "coupons expiration date + gplv3" theory, it would say that Microsoft is not guilty of infringement if Novell is not guilty of direct infringement.

    Free software advocates, in their zeal to get Microsoft, should not attack this principle, because that would make it easier for the RIAA to persecute innocent people accused of copying songs.

    Because of the grandfat her clause, the FSF has all but admitted it does not intend to proceed against Novell.

  58. Re:Microsoft would never be caught up in this anyw by sumdumass · · Score: 1

    It is only to doom companies who become friends with MS.

  59. Bottom Line by domatic · · Score: 1

    The question isn't whether Microsoft can be bound by the GPLv3; it is whether Novell can be bound. Novell cannot simultaneously honor the license on any GPLv3 code they distribute and the contract they executed with MS. The best the FSF could have hoped for was to defang a portion of MS' patent portfolio. If this lawyer says that can't happen, I tend to agree. The GPLv3 does make it impractical and of no benefit to execute any more of these deals with MS.

  60. GPL3 is not about attack, but about defend by Proto23 · · Score: 1

    No one is going to sue MS over GPL3, but GPL3 is a great defence for anyone being sued by MS over IP in Linux.

  61. You didn't read the GPL either. by argent · · Score: 1

    GPL3 explicitly recognizes this situation and exempts deals in force before the GPL3 was released.

    1. Re:You didn't read the GPL either. by Trillan · · Score: 1

      Thanks, but I know that. As I said in the original post (and every post since) it is the "well, good for them for trying" attitude that sucks. They didn't try to do the stupid thing.

    2. Re:You didn't read the GPL either. by argent · · Score: 1

      Err, your original post was really unclear then, because I still can't read it that way.

    3. Re:You didn't read the GPL either. by Trillan · · Score: 1

      That I'll concede. Enough people are interpreting it wrong that it's clearly me and not them... :)

  62. You also didn't read the GPL. by argent · · Score: 1

    This idea that the GPL3 is designed to attack any existing deals is a fabrication. I don't know if the person who posted this article is incompetent to practice law or trying to FUD the GPL... but if even someone like me who thinks we'd be better off without the GPL can see through it, it's pretty poor FUD.

  63. Re:Microsoft would never be caught up in this anyw by jbengt · · Score: 1

    "A voucher to get software from Novell isn't distribution by Microsoft"

    Care to test that theory in a US court of law? Or at least cite some case law backing up your legal theory?

  64. Haven't we been over this a couple of times? by dgun · · Score: 2, Informative

    As Novell puts out future versions of SUSE, they will incorporate GPL 3 software into their OS. If MS then distributes this GPL 3 software, they would be bound by the license just like anyone else.

    From articles on Slashdot over the last year or so, my understanding is that the Novell certificates MS was selling did not have an expiration date, making it possible for someone to redeem them after SUSE has been injected with GPL 3 code, thus pwning MS with the greatest pwning in the entire history of pwnage. Or so the story goes.

    --
    FAQs are evil.
  65. Mod parent up n/t by jbengt · · Score: 1

    n/t

  66. The GPL is not a contract. by anwyn · · Score: 1
    The GPL is not a contract. It was explictly and consciencely designed not to be a contract. It is not a contract because there is no two way exchange of value and no two way agreement. It's text explicitly says that you do not have to agree to it. It is a unilateral grant of rights.

    Eben Moglen tells how he enforces the GPL without it being a contract.

    Next time do some reading before calling someone a moron.

    1. Re:The GPL is not a contract. by Anonymous Coward · · Score: 0

      Next time do some reading before calling someone a moron.


      It's a free country, I can say whatever I want. Moron.
    2. Re:The GPL is not a contract. by Anonymous Coward · · Score: 0

      Yes you can and have expressed yourself freely and also freely demonstrated your idiocy and vast ignorance. Please keep doing it regularly, specially in the work place so that your employer (a free man too) can fire you.

  67. Re:Microsoft would never be caught up in this anyw by init100 · · Score: 1

    I've noticed a lot of people in this thread making assertions about legal issue without specifying whether they are lawyers or not (probably not, how many lawyers read Slashdot?). And even if they were lawyers, nobody can say with absolute certainty how a court would decide. I'd take their assertions with several tons of salt.

  68. Re:Microsoft would never be caught up in this anyw by Kjella · · Score: 1

    I certainly wouldn't mind testing it. How about gift cards? Coupons in magazines? You're not going to get any legal claim against whoever was distributing the voucher, unless the voucher itself is fraudulent. I seem to remember Pepsi giving away several million iTunes Store song "vouchers", are you saying Pepsi> distributed those songs? It certainly would be a creative interpretation which I'm sure the RIAA would like to hear about.

    --
    Live today, because you never know what tomorrow brings
  69. A lawyer speaks by achten · · Score: 1

    "Kay Lam-Beattie, principal with intellectual property lawyers Idealaw, said that based on the limited information available to the public, the Free Software Foundation's (FSF) efforts to hinder Microsoft's bullying over patents are likely to be fruitless."
    Confident statements based on lack of information. Well...
    The next paragraph basically says the same thing in different words.
    She said: "This [initiative] is squarely aimed at Microsoft. The question is, do Microsoft's actions regarding the [support certificates] fall within the definitions in the GPL 3 of what makes them a party to GPL 3?"
    Nowhere do we see an attempt to answer this question.
    It gets hilarious as
    Lam-Beattie said: "The GPL 3 is trying to bind Microsoft accidentally. Microsoft is saying: I have no intention of being bound by these rules."
    Is that a lawyer speaking?
    Then comes another paragraph on lack of information on the Novell-MS deal. What's the point in going on and on?
    The esteemed lawyer then goes on to confuse license with contract. Looks like she missed a few classes at the start of her law school.
    Or maybe it is the reporting after all.

  70. Confused, contradictory and stupid. by twitter · · Score: 1

    While existing customers might not implicate MS into GPL3 obligations; they may not have ANY future customers. And so, it is still a win for the FSF, without any need to go in to court.

    This is really simple. All versions of the GPL are a license that leverages the power of copyright. M$ and anyone else can have it at no cost as long as they abide by the terms. When software is released under those terms, all distributors are bound by them or they don't have permission to distribute. If M$ wants to avoid GPL3, they will have to fork everything GPL2 and maintain it themselves. Their ability to maintain both that codebase and their own is zero as Vista demonstrates their inability to maintain their own code. I doubt there's anyone dumb enough to listen to M$ about this crazy talk about contracts - M$ has a simple choice between a stale distribution and a license that emasculates their patent threat.

    M$ is trying to own free software, which is a blatant admission that free software works and non free can't compete. GPL3 prevents them from doing this with patents, so all the money they spent building a patent warchest was a waste. People who use patents to fight software freedom are not welcome to the free software party and are going to have to do everything themselves. Their FUD against GPL3 is not going to fool anyone, so they had better get coding.

    --

    Friends don't help friends install M$ junk.

    1. Re:Confused, contradictory and stupid. by Anonymous Coward · · Score: 0

      Wow, you are truly stupid

  71. Crap. by Anonymous Coward · · Score: 0

    "Your honor, I didn't distribute the drugs, I just sold vouchers to the kids that enabled them to get the drugs. Therefore I am not technically in breach of the law"

    Yea, I can see how that will fly. Get a clue.

  72. Yes, M$ Loves a Car Analogy by twitter · · Score: 1

    That lawyer obviously reads Slashdot, she went straight for the largely irrelevant car analogy.

    They post most of them here too. It's a pretty good piece of infowar. By making us all sick of something they think Joe Sixpacks likes, they think they are driving a wedge between Slashdotters and the rest of the world. Unfortunately for them, Joe Sixpacks can tell when M$ is blowing smoke up his ass with a false analogy. It's easy enough to ignore the analogy and make your point directly.

    --

    Friends don't help friends install M$ junk.

    1. Re:Yes, M$ Loves a Car Analogy by Macthorpe · · Score: 1

      So, car analogies are a Microsoft disinformation tool!?

      Do you honestly not think before you write something down?

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  73. If the GPLv3 real motive is so clear... by Josiah_Bradley · · Score: 1

    Why don't they just put into the license, plain and clear, a phrase like " The company Microsoft (or whatever it is in legalize) can not use or interact with software that is covered under this license unless it is by its customers using their OS.." etc. If everyone knows they wrote some parts of it to go against the actions of one company, why try and do it so vaguely. After reading the GPLv3 it is very clear some parts of it are politically motivated. I don't even agree with it on some points, but it's not my license, so they should just put in it what they want just like they already have. Right now everything I do I issue no copyright on and am happy if someone else wishes to use anything I may have thought up.

    1. Re:If the GPLv3 real motive is so clear... by yoprst · · Score: 1

      I've been looking for that kind of license, sort of, with little success. What I want is a license that allows app to be used with/compiled for free oses (Linux, BSDs, e.t.c.) only. Didn't find any...

    2. Re:If the GPLv3 real motive is so clear... by Anonymous Coward · · Score: 0

      The intent of the GPL has never been to be able to stop Microsoft or any other organization from using or distributing the software, it has been to set rules that they must follow if they do in order to ensure that everyone receiving the software has the same rights to modify and redistribute it.

      Despite this, some companies have managed to work around the terms of the GPL (e.g. by distributing the software on hardware that doesn't allow it to be modified by third parties - TiVo - or, in the Microsoft-Novell deal, it seems that Microsoft has effectively granted Novell customers "special status" in terms of patent use, i.e. if you're a Novell customer you can use Linux even if it supposedly violates Microsoft's patents, but they can sue anyone else), which is why the third version of the GPL was created.

      The FSF is happy as long as GPL software distributors all give everybody the same rights to modify and redistribute. Even if you consider their position political, it has always been consistent and objective.

  74. So exactly what GPL projects will MS distribute? by Anonymous Coward · · Score: 0

    Post a list of GPL'd projects that would

    a) benefit Microsoft to distribute
    b) that have functionality not already in a MS product
    c) don't have a decent BSD licensed alternative

  75. Bzzzt by Anonymous Coward · · Score: 0

    A license may be included in a contract; neither GPL or copyright law itself are. Microsoft vouchers are inducement and secondary infringement, it'd be hard to claim inaction here.

  76. The GPL3 wasn't trying to trap MS by BlueCoder · · Score: 1

    The GPL3 has nothing to do with Microsoft. No one ever thought that Microsoft would ever choose to release any software under it. Simply put it blocks other companies and developers from paying Microsoft protection money. If you gain privileges from Microsoft then you no longer have the right to distribute the GPL3 software unless you can transfer your privileges to all subsequent developers which MS obviously won't allow. This part of the GPL3 is all about trying to keep a level playing field. It prevents open software from being locked up and restricted through patents.

    A great feature is that open source developers don't need to use the GPL3, that it exists gives them political clout should a company like MYSQL try to lock up open source software though a patent. If any such company tried to do that they know the open source developers outside their company could easily jump ship with a code fork under the GPL3 (patching the code with a non patented technique) and the company wouldn't be able to touch the new code base, open source developers could turn the table on said company.

  77. and twitter loves anal analogies by Anonymous Coward · · Score: 0

    yay

  78. This may help clarify by Anonymous Coward · · Score: 0

    It isn't necessarily that you don't have to agree to the GPL when copying (for personal use) but that the GPL eother doesn't control it (where such right is not under copyright restriction) or that the demands of the GPL (that you give the person who has the copy the license and source) means that for personal copying (including "persons" like a business entity), they have to give themselves a copy of the license and source code that they got from someone else. A null action, unless you're REALLY anal about it.

  79. If "Evade"=="Not use" by Anonymous Coward · · Score: 0

    then MS can evade the GPL. What screws MS up is that in order for the NotADuck to seem not to be a license (which under GPL2 would mean MS granted GPL use of patents [NOTE! NOT!! grant all rights to patents, just use under GPL2. So, for example, Trolltech would have to license separately any MS patent for their non-GPL version of the Qt/KDE stuff]) they had to have Novell be the one distributing, which means Novell get to decide for MS under what license (since it was never specified) their code and MS's patents are released under.

    If MS can stop Novell from distributing GPL3 then they won't be under the GPL3. However, this would require that MS and Novell be partners and therefore arguably complicit in the addition of patents to GPL2 jointly in which case MS have released their patents (if there are any valid ones there) to GPL use.

  80. So AllOfMP3 are fine? by Anonymous Coward · · Score: 0

    And if Novell have the right to distribute GPL3 software with MS patents, then they give those patents under the GPL3. If Novell don't have the right, then MS must sue NOVELL.

    In that case, Novell may well require that MS disclose its patents before suing.

    Which is what the FOSS group wanted from the get go.

  81. Grey imports by Anonymous Coward · · Score: 0

    When you buy unused licenses from defunct companies who didn't actually install the software, MS says that you need a license to sell them on. But they aren't distributing because the copies were already made and legal.

    If MS take the idea that they aren't distributing they are just selling coupons, expect to see

    AllOfMP3 sell "coupons" to music
    TPB sell "links" (which aren't copyrighted) to movies, software, etc
    NapsterIII sell "coupons" to MP3s
    Grey Importers sell "coupons" for MS software from China

  82. Definition of "distribution"? by argent · · Score: 1

    In the sense that it's used in the GPL?

    Does this mean that I can go to CompUSA and demand *they* provide me a copy of the source to any versions of Linux embedded in any routers or other devices that they sell, since they're part of distribution of those devices and therefore (by this theory) they're also specifically bound by the GPL?

  83. Not even wrong by thethibs · · Score: 1
    1. Wild-assed assumption about the take-up of GPLV3
    2. Microsoft has no interest in distributing linux.
    3. Microsoft does have an interest in supporting specs like posix for those really large clients who require it—hence SFU and it's descendants, some of which may be GPLV2. They don't need to upgrade to meet the spec.
    4. The bypass was not to harm linux but to avoid being harmed by Wil E.
    5. The only bad scenario is the shrinking of the GNU audience that GPLV3 forces; and the linux audience as well if the folks behind Apache, samba, glibc, the linux kernel, gnome, kde, and firefox get all religious and forget to look to their best interests.
    6. Microsoft swims in either case.
    --
    I'm a Programmer. That's one level above Software Engineer and one level below Engineer.