Slashdot Mirror


Jeremy Allison Resigns From Novell In Protest

walterbyrd writes to alert us to word from groklaw.net that Jeremy Allison has turned in his resignation at Novell. "The legendary Jeremy Allison (of Samba fame) has resigned from Novell in protest over the Microsoft-Novell patent agreement, which he calls 'a mistake' that will be 'damaging to Novell's success in the future.' His main issue with the deal, though, is 'that even if it does not violate the letter of the license, it violates the intent of the GPL license the Samba code is released under, which is to treat all recipients of the code equally.' He leaves the company at the end of this month. He explained why in a message sent to several Novell email lists, and the message included his letter to management."

77 of 344 comments (clear)

  1. Excellent! by Scott+Lockwood · · Score: 4, Insightful

    Now if a few more people apply similar pressure. What I'd really like to see, is the Samba team officially pull support for Novell/SuSE, if not outright inform them they are in violation of the liscense, and their right to use the software is revoked.

    --
    But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    1. Re:Excellent! by Attrition_cp · · Score: 3, Interesting

      I wonder if developers jumping ship was part of Microsoft's reason for wanting the deal. more disenfranchisement means less open source competition (you could say they'll move to greener pastures but some could just leave). I realize even if that was true it would be a huge monetary waste for Microsoft, but tin foil hats are cheap. No, not trolling. It's a boring workday and I can cook up any plots I like!

      --
      Touched By His Noodley Appendage.
    2. Re:Excellent! by Iphtashu+Fitz · · Score: 4, Insightful

      Can the Samba team do that? Samba is released under the GPL, and even though Novell may be violating the intent of the GPL it's not violating the actual license agreement itself. I don't think the Samba team can unilaterally tell Novell they no longer have the right to use Samba. I suppose they could release new versions under a modified GPL license that specifically excludes Novell, but Novell could still use the current version and modify it on their own. It'd just end up in a split of the Samba project - the full GPL'd version and the bastardized Novell/Microsoft hybrid.

    3. Re:Excellent! by Scott+Lockwood · · Score: 2

      Knee jerk holier than thou reactions make the baby Jesus cry.

      You don't KNOW they're not in violation of the license. Intent is important. Clearly, they are not distributing the software any longer in a manor that is palatable to the people who write the code. That's a no-no. Also, they're trying for an end run around GPLv2, which is bad.

      Frankly, I'd like to see it go to court - I believe a case could be made that they are NOT fully compliant with the license. That, or I'd like to see Samba go GPLv3.

      --
      But this is slashdot. A slashdoter who didn't build his own computer is like a Jedi who didn't build his own lightsaber!
    4. Re:Excellent! by AceJohnny · · Score: 2, Insightful
      It'd just end up in a split of the Samba project - the full GPL'd version and the bastardized Novell/Microsoft hybrid.


      The worst part is that the bastardized Novell/Microsoft hybrid would probably the best-working version. (Hey, who better than microsoft to know the backward-compatibility quirks of Samba/CIFS?)
      --
      Misleading titles? Inflammatory blurbs? Keep in mind that Slashdot is a tabloid.
    5. Re:Excellent! by Eggplant62 · · Score: 5, Insightful

      Scott!!

      Yeah, I'm with you, pal. When I consider Steve Ballmer's comments regarding this deal, it stinks to high heaven. There's no way Novell or Microsoft will ever square this deal in my eyes in light of those patent threats made by the CEO of Microsoft. Novell's proper reaction should have been to turn right around and drop the deal once they heard what that creep was spouting. "Undisclosed balance sheet liability" my arse.

      No matter what Novell does, they still look to me to have been bullied into this agreement. Most likely MS came to Novell threatening legal action and this is how they settled it. We weren't inside, and we'll never know, but that's what this whole thing feels like to me.

    6. Re:Excellent! by GodInHell · · Score: 4, Insightful

      The assertion is that Novell is in violation of the GPL. You can't assert or rather, can't prove that something isn't. I didn't ask you to prove it, just to argue it. Arguments (as used in court) discuss questions of intent, meaning of text, possible conflicts, and proposed remedies.

      To the above ACs who feel that delcaring that Novell is not technically breaching the letter of the contract means that the contract is not breached, do some reading up on contracts. The words are open to interpretation - with the goal of divining the intent of the parties. Knowingly misconstruing the meaning of a contract to evade its obvious intent is a breach of contract - according to Englo-American juris prudence.


      -GiH

      Not a lawyer, just a student.

    7. Re:Excellent! by fudgefactor7 · · Score: 2, Insightful

      Novell now no longer needs Samba, with MS being their shiny new sugar-daddy. They'll just come out with something *like* Samba, but different, and proprietary (50% MS, 50% Novell), and it would probably work better than Samba does now...thus killing an otherwise excellent OSS program...and locking in more to MS's solutions...which is what MS wants. The only people that lose in this scenario is Samba and the OSS/GPL movement in general.

    8. Re:Excellent! by Anonymous Coward · · Score: 2, Insightful

      What I'd really like to see, is the Samba team officially pull support for Novell/SuSE, if not outright inform them they are in violation of the liscense, and their right to use the software is revoked.

      Er, so basically, you want the Samba team to treat Novell differently to other recipients of the code... because Novell don't treat recipients of the code equally?

    9. Re:Excellent! by DragonWriter · · Score: 5, Insightful
      Can the Samba team do that? Samba is released under the GPL, and even though Novell may be violating the intent of the GPL it's not violating the actual license agreement itself.


      I'm not sure that's the case; certainly, Allison's position sounds as if it is that the deal violates at least the spirit and possibly the letter of the license. Certainly, a high profile group of suppliers of GPL software included in Novell's Linux offerings raising the specter of litigation and license violations over the deal would undermine the primary purpose and destroy the value of the deal, which was, after all, to help Novell sell its commercial Linux products by removing uncertainty associated with them stemming from the specter of litigation over the IP violations.

      If there is a cloud of GPL-related potential litigation seen surrounding Novell, all its done is traded one potential source of litigation for many potential sources of litigation.
    10. Re:Excellent! by Eggplant62 · · Score: 4, Interesting

      I don't care what Novell says. They're trying to smooth feathers is all. Go back and read the entire statement Ballmer made and tell me you didn't feel physically revolted by his words. I know I did.

    11. Re:Excellent! by 10scjed · · Score: 4, Insightful
      exactly, Novell is Microsoft these days, sharing PR and sales offices, and spreading FUD about potential infringement since they are in the unique position to benefit from it.

      Novell isn't using their patents/IP to FUD against open source, they are using their partner Microsoft's patents/IP to FUD against open source. A technicality perhaps, but still wholly unacceptable.

      --
      --10scjed IANAL,AFAIK
    12. Re:Excellent! by eno2001 · · Score: 5, Insightful

      This is what I predicted from the beginning. The goal here was fragmentation of the Linux development community. It looks like they could succeed. It's basic "divide and conquer" because there will be some developers who don't see much wrong with the deal and will support the Novell Microsoft deal and there will be others who will not. The ones who don't MAY start new forks/projects and join other distros, or... they may just move on to other things entirely. This ensures a two-tiered Linux world with crappy underdeveloped software in non-blessed distros (Gentoo, Debian, etc...) and second-rate (compared to Microsoft Windows solutions) software in the intentionally stunted Novell Suse Linux and anyone else who decides to sign on. Microsoft very likely wants Novell Linux to be as successful as Apple's Mac OS was pre-OS X. That is to say, "enough to stay alive and prove that there is competition but not alive enough to compete on Microsoft's turf in the profitable business markets".

      Microsoft couldn't care less if Apple Macs were all the rage in schools early on because that wasn't one of their markets. Schools aren't as comparatively profitable as businesses. Once Microsoft had conquered the business world, they then started paying attention to schools and libraries and took those markets away from Apple. If the Apple platform actually started to make major inroads in server rooms, office suites, groupware and provided a killer alternative to Exchange, MS would be actively trying to take them down a few pegs again. Many Linux distros are doing exactly that and that's why taking Linux down a few pegs is a necessity to MS. MS doesn't want Linux dead. They just want it to smell funny. Probably something like pee. (I keep doing that)

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    13. Re:Excellent! by lawpoop · · Score: 5, Insightful

      Now witness the genius of the GPL. If you distribute software you have derived from GPL'ed code, you must provide that source code to the public under the terms of the GPL.

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    14. Re:Excellent! by Amazing+Quantum+Man · · Score: 3, Insightful

      he says that even though Novell is not violating the GPL, under which Samba is released, it still is not upholding the true intent of the license.

      No, that's not what he's saying. You're close, though. What he's saying is that even if Novell is not violating the GPL, under which Samba is released, it still is not upholding the true intent of the license.

      There's a difference. The actual statement is a hypothetical. Your version is an assertion.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    15. Re:Excellent! by garcia · · Score: 2, Insightful

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      Then they'll just link to an external library that hides all the new functionality.

    16. Re:Excellent! by PinkPanther · · Score: 3, Informative
      you must provide that source code to the public
      Er....um...no.

      You must provide access to the source code to the person to whom you delivered your derived work. Nothing in the GPL says that you need to provide access to the public.

      You are correct that the genius is that distributing something that was under the GPL must be distributed under the GPL itself. Recursive genius, though some fudslingers call it viral genius.

      --
      It's a simple matter of complex programming.
    17. Re:Excellent! by bb5ch39t · · Score: 3, Interesting

      But that person then has the right to redistribute. And if they do, then they must supply the source code. That is also a part of the GPL. You cannot take a GPL'ed program and say: "Here is a modified version and the source. But you cannot give it to anybody else!" Once the modified program is distributed to ANYBODY, then it can be distributed to EVERYBODY. And that cannot be stopped.

    18. Re:Excellent! by Damastus+the+WizLiz · · Score: 2, Insightful

      The assertion is that they are in violation of the SPIRIT of the GPL not in violation of the letter of the license. He clearly states that though Novell is not in volation of the GPLs terms the agreement Novell is ignoring the intent of the GPL.

      --
      I often have trouble remembering which way is out of bed in the morning.
    19. Re:Excellent! by larry+bagina · · Score: 2, Informative

      Now witness the genius of the GPL. If you distribute software you have derived from GPL'ed code, you must provide that source code to the public under the terms of the GPL.

      If MS/Novell create a better samba derived from the samba team's GPL code, they *must* provide access to the source code. Any improvements MS/Novell make to samba are guaranteed to become available to us, and they can never take it away.

      What you said is true... except that the GPL v 2 (which the hypothetical MicroSuse SAMBA fork would be licensed under) is incompatable with GPL 3 (which SAMBA will be licensed under). MicroSamba's improvements can't be merged back into SAMBA.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    20. Re:Excellent! by lawpoop · · Score: 2, Interesting

      Oh, now I get it. So that means that since it isn't MS developing GPL derived code, they aren't giving any implicit permission to use patented methods. Novell has an agreement with MS to use the patented methods, and they can develop GPL-derived code, but the recipients of Novell's GPL-derived code *don't* have an agreement with MS to use MS' patented software methods in the GPL code that Novell produced.

      Now I get it.

      However, this doesn't seem to be any kind of death knell for the GPL. If this were happening in the early nineties, it might be a problem, but we seem to have a critical mass of GPL software so that you can have an entire system that's GPL.

      I predict that this patent-encumbered Samba can only boost Linux adoption. The customers for MS/Novell Samba will have Linux servers and windows desktops. There's no reason to use this if you don't have Linux servers. And if you have Linux servers already, you must use Linux on the server for reasons other than it's cheaper than a Windows license. Why migrate to Windows servers if you can have Linux servers with no software cost?

      This type of software-patent work-around for proprietizing GPL code would seem to only work if there were an existing, well-developed GPL app that solely functions as a replacement or emulator for a proprietary program, and then, the proxy developer has to have an interest in creating and selling it. Sure, you can pay someone to create patent-encumbered GPL code using your patents, but then you have to get people to use it. That means that they have to have an agreement with you. So, just use the already free, already available alternative.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
  2. What really happened by autophile · · Score: 3, Funny

    Executive #1: Hey, I just got an Internet!
    Executive #2: Who from?
    Executive #1: Some guy named Jeremy. Isn't this caviar good?
    Executive #2: Sure is. Who's Jeremy?
    Executive #1: I think he's some greasy coder.
    Executive #2: Ha ha, they are *so* *guh-ross!*
    Executive #1: You said it! Here, have a small, autonomous Micronesian island, complete with 143 nubile slaves and an offshore account.

    Ha ha only serious?

    --Rob

    --
    Towards the Singularity.
  3. Re:Intent doesn't matter by eln · · Score: 2, Insightful

    It sounds to me like he released Samba under the GPL with the idea that the GPL somehow reflects some sort of utopian ideal where everyone is equal, and the GPL just doesn't say that. I wonder if he decided to use the GPL because it was the best-known Open Source license, without actually reading it (or better yet, having his lawyer read it), and is now caught off guard when he sees that the license he chose is not as reflective of his idea of the "Open Source Ideal" as he thought.

    He chose to release his software under a license that permitted this sort of behavior, and now he's complaining when people actually engage in this sort of behavior.

  4. Putting your money where your mouth is by astrashe · · Score: 5, Interesting

    Whatever you think about what Allison has done, you have to repsect him for living up to his convictions. This sort of thing can't be good for your career, or for your bank account.

    I really admire people who choose to live by their principles, even when it's hard or costly to do so.

    1. Re:Putting your money where your mouth is by PinkPanther · · Score: 3, Insightful
      This sort of thing can't be good for your career, or for your bank account.
      I will admit that this sort of move is risky, but I strongly suspect that this will be good for both his career and his bank account.

      So this leader of a popular software development project goes and gets his name splattered all over the web tied to an account of how strong his integrity is?

      You can't buy marketing like that :-)

      --
      It's a simple matter of complex programming.
    2. Re:Putting your money where your mouth is by Heir+Of+The+Mess · · Score: 2, Insightful

      I wouldn't feel too bad for him. He's moving to google http://blogs.zdnet.com/microsoft/?p=170/ which I'm sure isn't too bad for his career or his bank account. It's easier to have strong principles when you have a safety net. I've always found a job offer from a competitor to be the perfect opportunity to get things off my chest followed by a resignation.

      --
      Australian running a company that does C# / C++ / Java / SQL / Python / Mathematica
  5. Re:Intent doesn't matter by arth1 · · Score: 4, Funny
    You don't think that MS and Novell have had teams of lawyers going over everything for this deal, including the GPL. When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers.

    If I write a contract to deliver a dozen roses, but for some reason I think that carnation is called a rose and instead deliver a dozen carnations, I will be held in breach of contract. It doesn't matter what my intent was if I framed the contract improperly to ensure my intent.


    Fortunately, YANAL, and you're dead wrong. Using your example, if you deliver Kevin Rose and 9 members of his family, you've fulfilled the letter of the contract, but will still be held in breach of it because you violented the intent of it.

  6. Re:I don't understand this... by mccalli · · Score: 3, Insightful

    * The only people who are complaining are those who are true *idealists* when it comes to Linux and Open Source

    ....or in this case, the people that actually produce the software being used.

    I have large customers (people who spend money on software AND use Open Source) who run Windows and Linux side by side. Their NUMBER ONE complaint has been lack of interoperability.

    Precisely. Users will think this is great, but it's not users who are writing the software being abused. Large users in particular (I work for a very large corporate user of Linux) will think this is great, because they're already paying for their support contracts and are basically seeing Linux as a commercial OS anyway - that's true in their case, because they're paying for support and restricting themselves to supported configs etc.. But it's the people writing the code that are objecting to their labour being used in this way, not the end users.

    Cheers,
    Ian

  7. Re:I don't understand this... by Enderandrew · · Score: 2, Interesting

    Part of this agreement involves Novell paying Microsoft not to sue them.

    It makes the Linux world look guilty of stealing from Microsoft.

    And the second Novell gave Microsoft money, Novell ceased development on products that would compete with Microsoft.

    Do you think that Novell isn't forever compromised by this deal?

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  8. Probably Not by codepunk · · Score: 2, Funny

    However, nobody is saying samba has got to be easy to compile, run or maintain on Novell's distro.

    --


    Got Code?
  9. Re:I don't understand this... by MysticOne · · Score: 2, Insightful

    From what I understand, it doesn't protect any developers unless they work for Novell. Aside from that, it only protects Novell's customers from patent lawsuits. If you're using a different Linux distribution, you're not going to be covered.

    The problem here is that it does violate the spirit of the GPL. Rather than granting all users freedom, they're granting users freedom only if they've purchased a specific distribution. The GPLv3 will more than likely fix this, but for now we're stuck with the GPLv2 allowing actions such as this.

    Oh, and just how is Microsoft going to be fostering interoperability? I haven't seen yet where they've adopted any of our open protocols or open formats. I don't see them working with developers of free software products to help them inter-operate with Microsoft software. All I've seen so far is that Novell is going to be making an OpenXML plug-in for OpenOffice, and OpenXML is a standard in name only, also completely avoiding the intent of what it means to be a standard.

  10. Re:I don't understand this... by ctid · · Score: 2, Insightful
    * Microsoft says it will not file any lawsuits against developers over any patent issues

    MS said they won't file suit against hobbyist developers. They didn't say anything about developers who are paid to work on Linux by companies other than SUSE.
    * Companies can use SUSE Linux and Windows and know that total interoperability is the goal of both Microsoft and Novell

    Jeremy Allison has been quoted many times about some of the problems of making SAMBA work with Microsoft's SMB. Many of these problems have been because Microsoft do not (perhaps that should be "did not") want operability between Windows and Linux. As the founder of the SAMBA project, he's in an invidious position for precisely the reason you state when you talk about customers who complained about interoperability and who now want to switch to SUSE.

    --
    Reality is defined by the maddest person in the room
  11. Pretty simple actually by codepunk · · Score: 2, Insightful

    He did not like how his employer was circumventing the spirit of the license by which his code is developed. You see it does not matter what you, Novell, MS, HP etc thinks this is about developers. In a FOSS development model those commercial entities mean absolutely nothing at all, the developer who licensed the code steers the ship, not the other way around.

    Good on him, it is his code!

    Not like he has to work very hard at finding a new job anyhow.

    --


    Got Code?
  12. Re:I don't understand this... by mrsbrisby · · Score: 5, Insightful
    * Microsoft says it will not file any lawsuits against developers over any patent issues
    Maybe this is where you're confused.

    Microsoft says it will sue users of Samba, but not if they give Microsoft money by being a customer of Novell (because a portion of the SUSE warantee agreement goes to Microsoft directly).

    By doing this, Novell is violating my copyright and the copyright of every contributor to free software by redistributing my software to people who do not have the ability to redistribute my software (with all rights they received therein). The GPL expressly forbids this, both in intent and in letter.

    Novell is now saying that when I said anyone they distribute my software to must be given the same rights to redistribute that Novell has, and be told as such, that I really didn't mean it. While the GPL says this means Novell no longer has the right to redistribute my software, I strongly suspect they think it doesn't say that either.
  13. Winnowing The Herd by mpapet · · Score: 2, Insightful

    I think someone at Microsoft understands that most paid OSS developers choose their salaries over the many principals violated with the deal. I'm not discrediting the developers who make this choice. I've sacrificed my principals in exchange for feeding my family many times and I'm not alone.

    As has been said before, Microsoft is trying to narrow its Linux competition to one or two then eliminate them later. The influx of corporate politics and big money/power stands to poison the whole notion of bazaar-style development. Big-Money has a way of doing that. Look at Debian and dunc-tank. That's hardly big money and it's already affected volunteerism at that project.

    As is often the case, there are just a couple of people who carry such a strong sense of principals, that they choose a more uncertain path over a more predictable one that is the result of having more flexible principals.

    I for one admire his sense of conviction.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Winnowing The Herd by Tx · · Score: 2, Funny

      I'd sacrifice my principals for lots of cash, but not my principles.

      --
      Oh no... it's the future.
  14. Of course they can by bonefry · · Score: 3, Interesting

    A software's author that licensed the project under the GPL or any other license STILL RETAINS THE COPYRIGHTS of that project. Thus ... the author of a software project can specifically forbid a certain individual or company from distributing that software. If the Samba team holds the copyrights of Samba ... go figure, they can.

    1. Re:Of course they can by T-Ranger · · Score: 2, Informative
      Well, he diddn't change the text of the license. He added a clarifying statement to before the text © FSF. And he didn't change the license, either, as the license explicityly allows for such clarifying statements.
      9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
      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.
      If you are going to be commenting on licenses, it may be a good idea that you actually read them.
    2. Re:Of course they can by Linegod · · Score: 2, Informative

      >>Except that if the team wants to continue to use the GPL, the FSF doesn't allow modification of the wording of the GPL
      >>license...

      > How did Linus get away with modifying the GPL? The GPL states that:

      Because that is not the license. It is a paragraph that tells you which license you can use. It is not a part of the GPL. Many people use the same paragraph, but it is not a part of the license.

      --
      -- I care not for your foolish signatures.
    3. Re:Of course they can by Millenniumman · · Score: 2, Insightful

      It's stupid to let a third party change your license at will. You're essentially giving the FSF full control of your software with that clause.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    4. Re:Of course they can by Kjella · · Score: 2, Insightful

      Except
      a) It doesn't work retroactively and far more important
      b) It will no longer be GPL

      There's no such thing as "GPL with my extra requirement", then it's not GPL or even GPL-compatible. If you're lucky it's still OSI-definition "open source", but I think that would even disqualify it as that.

      --
      Live today, because you never know what tomorrow brings
  15. The GPL is no longer sufficient for many coders by pscottdv · · Score: 5, Insightful

    From TFA

    "Do you think that if we'd have found what we legally considered a clever way around the Microsoft EULA so we didn't have to pay for Microsoft licenses and had decided to ship, oh let's say, "Exchange Server" under this "legal hack" that Microsoft would be silent about it - or we should act aggrieved when they change the EULA to stop us doing this?"

    I think this sums up both the reason why the GPL community is mad at Novell even if they didn't technically violate GPLv2 and why there is a need for GPLv3.

    Some are saying that the community has no right be mad at Novell because they aren't technically in violation of the GPL. Fine for them. But many of those that contribute code to GPL projects do so because they believe in the intent of the GPL, which is that all who receive the code are to be on the same legal footing as all others regardless of how they receive it. If the GPLv2 is no longer sufficient to provide this guarantee, then changes are needed. And it is perfectly valid for Eben Moglen to craft the changes to plug specific legal-loophole, zero-day exploits in the GPLv2 such as this Microsoft-Novell deal.

    Novell keeps trying to make this deal smell rosy by talking up the interoperability part of the agreement. Are they really so stupid that they do not see that the interoperability part of the deal is not what has GPL supporters upset? They could have made any number of deals with Microsoft to work on interoperability without trying to destroy the foundation of the GPL.

    --

    this signature has been removed due to a DMCA takedown notice

  16. This makes me a sad Panda by rudeboy1 · · Score: 3, Interesting

    SUSE 10.2 is my preferred flavor of Linux, and with all that is currently going on, I feel guilty for liking it as much as I do. I see it as a potential windows alternative down the line, once XP is sufficiently outdated, if 10.x keeps improving, cause I'm sure as hell not pissing money away on Vista. Now I feel like I'm being sucked back to the Microsoft teet even as I make plans to break away.

    --
    Raging in an online forum won't do anything for the world around you. To see change, you must take action.
    1. Re:This makes me a sad Panda by rkhalloran · · Score: 2, Insightful

      I've run SUSE for a few years now, through 10.1, but with the Novell deal I've reimaged with Kubuntu 6.10 and I don't plan to look back.

      Ballmer promptly started spewing once this deal was signed that customers of other Linux distros were at risk [somebody shut him up shortly afterwards]. This provides MS a wonderful FUD opportunity now that the SCOX farce is winding down. This implies that Linux actually infringes on Microsoft patents somehow without openly admitting it, and that Novell paid them off to stay legit. All of which is anathema to the FOSS movement that created this code to start with.

      If Stevie B actually thinks there's patent violations in Linux, let him bring them forward. If not, he should STFU and try competing on the merits of his company's products. Oh wait...

  17. Won't revoke rights; Samba team too good for that by KWTm · · Score: 4, Insightful
    Because Samba is distributed under the GPL, they won't be able to revoke the rights to Novell as long as Novell stays within the (letter of) the agreement.

    Besides, in the past, the Samba team has demonstrated a professionalism that has put their detractors to shame, and I hope they can continue to uphold their standards. Witness what they said to SCO when SCO accused the evil Samba team of spreading the deadly plague of Open Source (all the while distributing Samba with their SCO Linux). Here's the letter from Samba to SCO:
    Samba is developed and distributed under the GPL, in exactly the same manner as the Linux kernel code that SCO has been criticising for its lack of care in ownership attribution.
    Because of this, we believe that Samba must remain true to our principles and be freely available to use even in ways we personally disapprove of.
    Even when used by rank hypocrites like SCO.

    Translation: "Up yours, SCO." But they say it in such a way that it will carry weight in business circles. In the same way, Allison's resignation makes a clear statement.

    It would be a mistake to do otherwise; if the Samba team says, "Well, then I *un*-give you the code! Nyaah nyaah!", it would epitomise in the minds of executive decision-makers that Open Source is run by a bunch of immature J.Random Hackers From China who will revoke your license at the slightest provocation.

    One only hopes that Novell will show some more understanding of how much turd they have now placed their foot in, and make some public gesture to show the IT world that OSS is alive and well. Sort of like what EV1 did. Novell's done a lot of good for OSS. I hope they continue.
    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  18. Re:I don't understand this... by PenguinBoyDave · · Score: 2, Interesting

    I might be dead-wrong here. I might be so wrong that I'll lament ever supporting this. But I look at this as Microsoft finally admitting that Linux and Open Source are here to stay, and since they can't and won't beat it, why not see how to best work with it. The formation of the Port25 website and the Open Source lab is a good step in the right direction.

    --
    I'm not a troll, but I play one on Slashdot.
  19. Re:I don't understand this... by neaorin · · Score: 2, Insightful

    How is Novell violating your copyright because of something another company said?

    If there were no deal and MS said 'we'll sue everyone, but not Novell 'cause we like their funky green lizard', would Novell still violate the GPL by redistributing?

    Now if MS comes out and points out copyright violations in GPL code, Novell can't legally distribute it regardless of the deal...

    I've RTFA and I think the guy is saying he feels marginalized by the community because the company he worked for 'made a deal with the devil'.

    "We can pledge patents all we wish, we can talk to the press and "community leaders", we can do all the right things w.r.t. all our other interactions, but we will still be known as GPL violators and that's the end of it."
  20. Re:is he tainted now? by rkhalloran · · Score: 3, Insightful

    EXACTLY the sort of consideration this deal generates, all to MS' gain.

    And why the developer community is so seriously dead-set against it. Any code contribution by Novell at this point has to be considered suspect against MS claims of infringement that Novell/its customers are supposedly safe from, but the rest of us are wide-open to.

  21. Intent matters in contract law. by GodInHell · · Score: 2, Interesting

    You don't think that MS and Novell have had teams of lawyers going over everything for this deal, including the GPL. When it comes down to it, it's the letter of the contract that matters, not the intent that was in the minds of the writers. You are about 170 degrees off true (mostly wrong, but not all wrong). A written contract is always subject to interpretation of meaning, definition of words, etc. The more complex the terms used in a contract the more likely it is to be open to interpretation. In American Jurisprudence, the normal goal in interpreting a contract is to reach a true understanding of the intent of the parties to the contract. Here, the parties are the GPL community and Novell/MS. The GPL includes several clear statments of intent - to create freely available open source software, to encourage contribution, and to prevent abuse by parties who would seek to seize that software and claim it for their own.


    I'm not going to take the time to teach class in contracts, but the long and short is that judges (usually) interpret for intent, punish those who seek to abuse ambiguity, and interpret toward a useable contract (if an interpretation makes the contract void, they go with a different interpretation).

    If I write a contract to deliver a dozen roses, but for some reason I think that carnation is called a rose and instead deliver a dozen carnations, I will be held in breach of contract. It doesn't matter what my intent was if I framed the contract improperly to ensure my intent. That's actually not true. If the mistake is unilateral (only the other party made a mistake and you were not aware of it) then they are probably in breach - however, if any element of the contract suggests that the mistake was apparent at the time of contract (the price is far too low, there is evidence that you were show a picture of the final product, etc) you're boned. Judges will tend take a narrow view of parties who attempt to abuse contract language to enforce and unfair deal. If it is clear that the given interpretation is decidedly one sided, or that an interpretation requires ignoring common use of language and interpreted meaning of the contract - they will see it for what it is, abuse of the legal system, and rule accordingly.

    Wikipedia has some information on mistake, and also interpretation: Mistake / Interpretation of Tems.


    -GiH

  22. Novell would be the one with the fork. by khasim · · Score: 4, Interesting
    This is what I predicted from the beginning. The goal here was fragmentation of the Linux development community. It looks like they could succeed.

    Okay.

    It's basic "divide and conquer" because there will be some developers who don't see much wrong with the deal and will support the Novell Microsoft deal and there will be others who will not.

    But that does not seem to be happening.

    So far it is just Miguel who supports it ... and everyone else who opposes it.

    The ones who don't MAY start new forks/projects and join other distros, or... they may just move on to other things entirely.

    I think you're confusing those items.

    If the legendary Jeremy Allison moves to Red Hat or Canonical, he'll probably still be working on Samba. And when the GPL v3 comes out, it will probably be adopted by Team Samba.

    So in that specific case, it would be Novell who would have to fork the project and do all the work without the help of Team Samba.

    This ensures a two-tiered Linux world with crappy underdeveloped software in non-blessed distros (Gentoo, Debian, etc...) and second-rate (compared to Microsoft Windows solutions) software in the intentionally stunted Novell Suse Linux and anyone else who decides to sign on.

    Huh? So Red Hat (where Alan works) is "second-rate"?

    Or is it that Ubuntu is "crappy"?

    I don't see that happening. Instead I see a company flailing at its declining marketshare and signing an agreement to FUD everything else Linux related.

    Just like SCO did.

    And Novell will die, just like SCO is dying.
    1. Re:Novell would be the one with the fork. by eno2001 · · Score: 2, Insightful

      It's all hypothetical, but I'm speaking strictly from the vantage point of a non-technical person (I am an IT person, I'm just playing non-tech's advocate.) and that is likely the way they will see things. "Oh... I heard that you shouldn't use RedHat in the server room because it can't run on the latest servers since they didn't go with the Trusted Computing option that Novell did". Or... "Yeah, I could use Debian to run a web server but this review I read said that Novell's Apache based web server has full IIS compatibility and is able to essentially duplicate the previous version of IIS". To those people, Novell is going to seem like the easy choice and the others will be fairly irrelevant. Of course to those same people anything that isn't "Big name/corporate backed" isn't relevant anyway. My bosses keep trying to convince me that we should have paid support for EVERYTHING we run in the server room so they really want Redhat or Novell. With the latest, they are starting to lean towards Novell and away from Redhat. Not wise, but that's the typical impression of non-technical folks.

      Personally Gentoo rocks my world and I run it on all the boxen at home as well as on a few Xen VMs here doing some fairly important stuff (syslog for our network switches routers and firewall for example). The only thing that makes me run "supported" Linux distros are product requirements. Oracle's management package MUST run on RedHat Linux Enterprise for example. Can't get away from that... So if these companies eventually start dictating that only the "one true" Novell Linux is the only supported one, I'll be stuck. And you know there are going to be people who will see the Microsoft "blessing" of a Linux distro as meaning that it's got a higher level of quality over non-blessed distros regardless of the truth.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  23. It's not about copyright by Anonymous Coward · · Score: 5, Insightful

    The issue with the Novell deal isn't copyright. It's patents. In countries dumb enough to allow software to be patented (ie, the US), Microsoft could make Samba 100% compatible with Windows and 100% GPL. They'd be able to say, though, if you're not a Novell user they'll sue you for patent infringement.

  24. Would GPLv3 protect against this? by mpcooke3 · · Score: 2, Interesting

    I'm interested to know if the GPLv3 would help stop this kind of deal.

    My understanding is that under GPLv3 Novell would have their rights to redistribute samba terminated if they themselves tried to enforce a patent claim against Samba.

    Under GPLv3 would Novell have their right to redistribute Samba terminated if they knowingly introduced code that was patented by Microsoft into Samba? Also how could it be proven?

  25. Utter rubish by Anonymous Coward · · Score: 2, Insightful

    Pardon me, but you sound like a Novel apologist, trying to sow memes of acceptance of Novell.

    Allow me to disprove your contention; it's quite simple. This deal has been such an utter P.R. disaster for Novell that they have had several P.R. opportunities to try to explain themselves. Not once has there ever been any hint of a statement that this deal was either a mistake, or that they were forced into it.

    Your "feelings" about this deal are seriously misguided. If this were indeed the case, Novell would have at least dropped some hints in this direction. Please quite trying to justify this deal by making excuses for Novell.

    My impression of Novells' actions and statements is that this deal is all about greed, not fear.

  26. Re:Red Hat Opportunity? by Anonymous Coward · · Score: 2, Interesting
    Well, here's a nice hiring opportunity for Red Hat - let's see if they take advantage of it.

    To be honest I think I would rather see IBM pick up Samba and Jeremy. Not because I don't have anything against Red Hat because I don't. IBM has a lot more good lawyers should Microsoft start threatening lawsuits and IBM would be better equipped to stand up against any attack from Microsoft. Not to mention the fact that SMB originated at IBM.

  27. Others can do a better job. by GodInHell · · Score: 2, Informative

    I'm not involved in coding for the project or in GPL litigation.. however others who are have posted below. Check it out.

    Here's one argument on how Novell is breaching the GPL: sample

    I'd do more linking.. but it's lunch time.. [runs off to meet fiance]

    -GiH

  28. You miss the point by Eric+Damron · · Score: 5, Interesting

    You miss the point. Novell and Microsoft are saying that they can release code under GPL v2 that is encumbered by patents. If this is the case FOSS CANNOT use that code without denying the freedoms that were the intent of the GPL.

    Microsoft could, for example, help Novell inject their IP and later tell users that they must pay or be sued for patent infringement.

    I didn't support GPL v3 in the past but I do now. Let's close this loophole and shun Novell until they straighten up and fly right!

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:You miss the point by lawpoop · · Score: 2, Interesting

      Let me see if I understand what you are saying. They are creating works derived from GPL'ed code, but they claim that their contribution is covered by patents, so even if they were to distribute the code, end-users would have to deal with patented processes, ideas, etc. in that new code.

      So there would be a kind of built-in conflict of the resulting code -- on the one hand, it's GPL'ed, but on the other hand, it's covered by patents. Is that about right?

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    2. Re:You miss the point by giminy · · Score: 2, Interesting

      Thank you. A few years ago I got flamed on slashdot for suggesting that patent encumbrance could be an issue for the GPL. This deal is making people "get it." Yay!

      I recommend taking the GPL Quiz for anyone that questions anyone else's understanding of copyright and patent issues. It's a great starting point to understand some of the issues, and slashdot would be a better place for it.

      --
      The Right Reverend K. Reid Wightman,
  29. It's not LGPL by mangu · · Score: 5, Insightful
    they'll just link to an external library that hides all the new functionality


    The beauty of the GPL is that they cannot do that. That's why I support the GPL over all other licences, its track record to this day has been perfect in keeping free source free.

    1. Re:It's not LGPL by Sloppy · · Score: 2, Insightful
      they'll just link to an external library that hides all the new functionality
      The beauty of the GPL is that they cannot do that.
      Really? They'll get sued and injuncted like Nvidia and ATI did?
      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:It's not LGPL by Znork · · Score: 2, Interesting

      Do note that many Linux vendors do not ship proprietary drivers because of that exact GPL requirement. You're entirely free to ship the components apart (like NVidia and ATI), letting the end user do the combination, but shipping the combined work is a violation.

      Supposing a loadable module functionality for Samba that would allow a reasonably 'separate' entity to exist without incursions into the Samba sourcecode it might be possible for a third party to ship such a module and let the end users do the combining. But it would fairly painful to manage.

    3. Re:It's not LGPL by OriginalArlen · · Score: 4, Insightful
      Right, but I think you underestimate the skill of the lawyers and engineers Microsoft will have poring over this problem. How's this for a scenario. Microsoft release a new product specifically for SuSE interop - not just for SMB, but the real value of the Microsoft LAN stuff which is Active Directory. The product contains two main components. A client-side blob runs on the SuSE client and includes ready-to-go config files (note: not software, just configs) to set various stuff up - Kerberos or OpenLDAP, Samba, PAM, CUPS perhaps, and so on. All that software can be made to work well with AD, but anyone who's tried to learn it from the man pages will have also spent a lot of time searching mailing lists for config tips. The software probably has a wizard, it prods the local network and DCs to see what is likely to be well received, makes "intelligent" guesses to recommend default settings, builds the config files and HUPs the required services / daemons. The whole thing would appear in the SuSE installer as something like "Microsoft Network InterOp Kit". The MS-blessed configs would just eliminate the hell of trying to make everything work OK. (I've been using Linux as a workstation and for security and web development work for eight years now, and it's as much as I can do to make icons on the desktop that open smb:// URLs in Konquerer. A keen web dev tried to get his LAMP wiki to use AD authentication, he was messing about with mod_auth_kerb for weeks, every few days he'd get excited & come over asking me to try it again, again without success. The Microsoft-blessed config files can of course be easily read and copied, but they're (c) Microsoft and no other distribution can use them. They can't even read them , go "Aha! I need to set signing to NTLMv2 AES-128 *only* for NMB lookups, not Samba SMB traffic itself" (or whatever it may be) and then write the appropriate lines into their own custom config files. And if anyone looked like getting close, MS would I am sure be happy to kick off a decade or two of lawsuits, draining tens of millions of dollars from the victim distributions and vigorously smearing FUD over the whole GNU world. The end result is that SuSE Linux interoperates beautifully with a Windows AD based network, has a "Microsoft Approved" sticker on the front, and comes with file & print, mail & whatnot all working really slickly. No other distribution can ship the same thing because Microsoft own the copyright on the configs and client-side agent binary. Other distros can attempt to find their own magic configs, but let's face it, we've been working on Windows interop technologies for ten years and although huge amounts of excellent work have been done, Microsoft will always easily be able to FUD corporates by saying it's unsupported -- "Unlike Microsoft's new "Services for Linux" product, included with our selected Linux Partner Vendor, Novell. Here's their number, tell 'em Bill sent you..." No linking to GPL'd software required, no source released, Microsoft succeed in partially subverting Free software. Score: Microsoft 1: Free Software community 0.

      I personally think it's a tactic that shows signs of desperation; you can bet they've spent a lot of lawyer-years brainstorming ways to attack Free software, but it looks like they've got something here in the short term. It would be a dangerous move to be seen to endorse Linux even slightly, and shipping software to run on it would certainly do that -- but most of all I think it'd increase the exposure of Windows admins to Linux / Free software, which just increases the rate of attrition of MS mindshare. So in a couple more decades, OSes will be seen as far more of a commodity, and minimal, streamlined feature sets with straightforward modular components. And will include an old .au file of a man saying "My name is Linus Torvalds, and I pronounce it 'Lee-nuhx' :)

      --

      Everything I needed to know about life, I learnt from Blake's Seven
  30. Re:I applaud him! by SuiteSisterMary · · Score: 4, Funny

    "GPL3 ain't done till Microsoft and Novell won't run"?

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  31. They would run Windows, not Linux. by khasim · · Score: 4, Interesting
    It's all hypothetical, but I'm speaking strictly from the vantage point of a non-technical person (I am an IT person, I'm just playing non-tech's advocate.) and that is likely the way they will see things.

    I'm not seeing that. If people question Linux, they'll choose Windows instead.

    Just like Novell's CEO saw when he tried to go head-to-head with Microsoft ... and kept losing the deals.

    "Oh... I heard that you shouldn't use RedHat in the server room because it can't run on the latest servers since they didn't go with the Trusted Computing option that Novell did". Or... "Yeah, I could use Debian to run a web server but this review I read said that Novell's Apache based web server has full IIS compatibility and is able to essentially duplicate the previous version of IIS". To those people, Novell is going to seem like the easy choice and the others will be fairly irrelevant.

    No, the "easy choice" will be Windows. The "easy choice" in IT is always to go with a single vendor. That way there's no finger-pointing about why something won't work that way the salesperson said it would.

    Why would anyone be looking for "full IIS compatibility" from a different vendor when they can have IIS itself? Migrations are expensive and the customers know that deals between IT companies can go sour. It's safest to involve the fewest companies and that means buying from the vendor selling the product itself. Not from someone promising "compatibility" with that product.

    Linux has a few advantages over Microsoft products. And licensing is one of the biggest advantages for the end user. Once that is gone (and it is under Novell's deal), there really isn't any reason for the end user to consider "compatibility" with Microsoft's products when they can just go with Microsoft itself.

    Particularly when Novell has to maintain its own "forks" of projects such as Samba because Team Samba has gone with GPL v3.
  32. The spectre of litigation by GodInHell · · Score: 2, Insightful

    If there is a cloud of GPL-related potential litigation seen surrounding Novell, all its done is traded one potential source of litigation for many potential sources of litigation. There is an essential difference between a threat of litigation from Microsoft, and a similar threat from any grassroots community. MS has the cash on hand to fund litigation until they've emptied the pockets of nearly any opponent - they can file motion after motion which you must reply to or face the very real possibility that the judge will summarily rule in MS's favor (since you failed to respond). The resulting legal bills are extremely cost-prohibitive.


    An honest litigant dosen't need to use these tactics, they are the techniques of the abuser and the oppressor company, but they work, and there are lawyers who will do this for Microsoft, RIAA, and other sources of pain and suffering.


    Microsoft would be willing to bear these costs, because they see a need to confront the open source movment NOW before Google shows the world how to get run everything through a web browser, and open office winds up sitting in front of technical evaluators at middle sized companies. Putting the stink of this kind of litigation - branding open source software as an illegal movment which steals and cheats the system, will drive buisiness back towards main stream solutions. As of right now, MS is the only show in town that qualifies.


    This is another in a long chain of life altering moments that you should probably write about in your diary - today I saw MS launch the second stage of its war on linux.

    -GiH

  33. What about Nat Friedman? by Bruce+Perens · · Score: 5, Insightful
    I've publicly told Nat Friedman, whom Novell is using as the public apologist for the patent agreement, that I think his ethical position stinks, Jeremy's resignation (which I applaud, of course), should reinforce this. Nat should leave too.

    Please sign the Open Letter to Novell. I'd like to get that over 3000 signatures at least today. It's at about 2950 now.

    Thanks

    Bruce

    1. Re:What about Nat Friedman? by Rimbo · · Score: 2, Interesting
      Bruce --

      If I were a Novell executive, upon reading your second sentence, I would immediately think: "That's correct. This is in our best interests financially!" I would stop reading beyond that point; you just made my point for me, so any disagreement expressed would not be in my interests to investigate.

      Novell doesn't care about betrayal, unless it affects their bottom line. Now, you and I both know that Novell's decision will affect their bottom line. So instead of patting Novell on the back for their wise financial judgment in the first paragraph of this letter, let's start the letter with a sentence that connects the dots for them?

      I would recommend the following first paragraph:

      The Open Source community would find little to criticize in your agreement with Microsoft, had it remained a strictly technical agreement. As the agreement stands today, it betrays the authors of the software you re-market and their users worldwide for a potential short-term gain that will lead to a certain long-term loss, as betrayed authors and users discard Novell's products and services in favor of those provided by Novell's competitors and partners.


      That last sentence could be broken up, as it's a bit wordy, but you hopefully see my point. We have to get their attention, and that means showing them the money. Telling them that their agreement is for their own financial benefit will just steel their resolve.

      Make that change, and I'll sign your letter.
    2. Re:What about Nat Friedman? by Bruce+Perens · · Score: 2, Interesting
      If I were a Novell executive, upon reading your second sentence, I would immediately think: "That's correct. This is in our best interests financially!" I would stop reading beyond that point; you just made my point for me, so any disagreement expressed would not be in my interests to investigate.

      I see. You believe that the phrase "it betrays ... for Novell's sole financial benefit" would be percieved as "we screwed someone to make money, great!, no need to read any more of this, there can't possibly be any negative consequences".

      If that degree of cynicism applies, and it may well, there's little hope of convincing them of anything. Our only choice would be to follow a similar strategy to SCO - deprecate them and direct customers elsewhere until there's no business left. And that's what we're doing, because there never was very much hope that they'd "get" it, and we've handled situations like this enough times to know that yes, we'll be rid of them eventually.

      I hope you can understand that I am wary of editing the document after 2973 people have already signed it.

      Thanks

      Bruce

  34. I think that THAT is the reason for this "deal". by khasim · · Score: 3, Insightful
    The whole system is designed to set you up for failure, presumably so that if they send the BSA around for an audit, they're bound to find something that's not up to scratch.

    EXACTLY. And if you'll look at the SCO case, you'll see the exact same thing. SCO sued a couple of its own customers NOT because they were using Linux but because they did not comply 100% with the contract they had signed with SCO.

    When Microsoft comes in for an "audit", they're not doing it to help you. They're doing it because they want more money out of you. And the only way to get more money out of you is to "find" that you are not "in compliance" with the agreement you signed.

    Which is why it would be smarter for people to avoid Novell products which Novell is paying a ROYALTY to Microsoft for if you're looking to reduce your exposure to Microsoft lawsuits and/or reduce your costs to Microsoft.
  35. Re:I don't understand this... by PenguinBoyDave · · Score: 2, Insightful

    We could go back and forth like this all day long...point for point. But I'll break it down like this:

    1. Windows was in the Data Center first (except for mainframe and Unix...but hang with me for a minute)
    2. Linux is the newcomer to the corporate world.
    3. Companies are not going to dump their Windows environment for Linux, just because Microsoft has, admittedly, made no effort to integrate with Linux. We would be foolish to believe Gates / Ballmer would say "you know, it would be great if we could make our OS work with this new, free OS that is our direct competition." If they did, they would have their shareholders up in arms. My last company made great strides in integrating Linux into their corporate environment, but when you have a gazillion Exchange servers, you're not going to dump that. Just isn't going to happen. Same with SQL servers...not going to win that one either.
    4. Now, Ballmer decides he can't beat Linux or Open Source decides that perhaps it is time to work together, because the customers are telling them they need to do so. Great. But don't expect him to change over night. Sure...he can say "all Linux users are fair game..." but what are the odds of that happening? Surely he's seen the fiasco that is the SCO lawsuit. He's not that stupid.

    Look...if it were up to me, everyone would run Linux on the desktop and the server. I've done it for years, and with the exception of my work laptop, I'm either running Linux (Debian & SUSE) or Mac OSX. But it isn't up to me. IBM said they were going to switch everyone to a Linux desktop. They didn't. Novell said everyone was going to use a Linux desktop. A lot do, but not everyone. The plain and simple fact is that Microsoft is the world's largest software manufacturer. Ballmer is charged with protecting its interests. The Open Source lab and the deal with Novell are a good step. But as I said, we can't expect him and the ship that is Microsoft to change course over night. It takes time. Companies and individuals will also change over time, and more Linux will show up on the desktop and server. When I work with friends setting up businesses I recommend and help them implement Open Source software. But that is from the ground up. Trying to get bigger companies to make that change isn't easy, and they will stay with what they have because of what it would take to switch.

    Come up with a tool that will seamlessly migrate Windows desktops and server to Linux with little to no down-time, and you'll be a Billionaire...guaranteed, and this discussion won't happen, because everyone will run Linux, because they can, and it won't hurt in the process of changing over.

    --
    I'm not a troll, but I play one on Slashdot.
  36. That is correct by Eric+Damron · · Score: 4, Insightful

    Yes, that pretty much sums it up. Novell has always maintained that it hasn't infringed on Microsoft's patents but Microsoft has openly stated that Samba and Mono and other software does infringe.

    So what you have is Microsoft offering .NET to the world as an "Open Standard" and then claiming that whoever implements it are using Microsoft's IP that are protected by the patent laws.

    Microsoft has never been known for playing fair and it's time for the entire world to work hard to simply make them irrelevant. Don't implement standards that are not truly open. Don't support Microsoft in ANYTHING they do. Demand that they be held accountable for their continued antitrust violations. Microsoft needs to be broken into at least three separate companies in order to level the playing field. This can easily be justified by their continued lawless actions and the effects those actions have on the IT world.

    --
    The race isn't always to the swift... but that's the way to bet!
  37. Re:Won't revoke rights; Samba team too good for th by Omnifarious · · Score: 2, Insightful

    Except, that's not ad hominem because it's directly related to the issue at hand. Pointing out that even SCO doesn't really agree with their own arguments if you look at their behavior doesn't create the standard logical fallacy of an ad hominem attack.

  38. stop spreading FUD by oohshiny · · Score: 2, Insightful

    If the legendary Jeremy Allison moves to Red Hat or Canonical, he'll probably still be working on Samba. And when the GPL v3 comes out, it will probably be adopted by Team Samba. [...] So in that specific case, it would be Novell who would have to fork the project and do all the work without the help of Team Samba.

    There is no rational reason anybody has demonstrated why SuSE shouldn't be able to ship Samba under GPL v3. So, please, stop spreading FUD.

  39. GPL3 is expressly incompatible with Novell deal by OmniGeek · · Score: 2, Insightful

    So, if Novell is distributing under a nontransferable "patent umbrella license" from MS, wouldn't that put them in violation of the GPL3 with any GPL3-licensed package they were to distribute? That's the crux of the whole GPL3 issue, IIRC; that Novell would need to do its own support and updates under GPL2 'cause they couldn't distribute anything under GPL3 and still offer the "patent protection." I don't seem to recall there being any wiggle room in that deal for Novell to distribute Open Source software outside the "umbrella," and that's the only way they could still be in compliance.

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
  40. Playing right into Microsoft's hands by petrus4 · · Score: 2

    If anyone in the community had bothered to stop and think about this, they might have realised that it is possible that causing such division is exactly what Microsoft intended with this agreement. As those of you who've read ESR might remember him saying, the greatest (and ultimately only) strength FOSS people have is their programming ability.

    If Allison had stayed with the company, he might have been able to keep securing funding for the Samba project, which in turn would mean that code would continue to get written...presumably GPLed code which Microsoft thus would have been unable to co-opt.

    Throwing a tantrum and leaving accomplishes nothing. It will not hurt Microsoft in the slightest, nor is it likely to impress anyone watching with Allison's "moral stand." The only thing it will accomplish is possibly throw the future of the Samba project into question, at least with regards to his ability to continue maintaining it.

    A number of people involved in FOSS need to read Machiavelli and get a clue about how the real world works. Isolated exceptions like Gandhi aside, "principled" martyrdom generally accomplishes exactly nothing. 99.9...% of the population are only ever going to care about FOSS purely on the basis of how doing so benefits them. They DO NOT CARE about moral abstractions of any kind. I wish I knew why so many people associated with Linux had such difficulty comprehending this.

    Please try and understand one simple concept. Windows became the dominant system purely because it gave people what they wanted. No other reason. If the people who develop Linux want it to become the dominant system, then they are ultimately going to have to abandon any other consideration; technical superiority, "principle," whatever. If Linux's developers want it to take over the world, the *only* thing that can matter is that it does what people want.

    If principle is something that Linux's developers care more about than relevance, that's fine...but people need to start recognising that the two are mutually exclusive. If you want one, you're going to have to let go of the other. In terms of gaining the type of popularity for Linux that many of its' developers seem to want, Hobbesian ethics are far more likely to be of assistance than the Lockean philosophy that such groups as Debian claim to adhere to.

    This more than anything else is how I know that people are naive when they believe that Stallman is the being of light that they do, while still having managed to gain the marginal degree of influence that he has. Power doesn't work that way. It comes from giving people whatever pleasant mirage they want to see. In Stallman's case, the Prophet, St Ignucius, is the image some people want, and which with a certain demographic, Stallman has managed to rate pretty highly...but again, it's purely because by following along with his crusade, people expect to either be able to get free software, or make money from it...straight back to the "what's in it for me?" principle.

    As an example of this, it nearly made me vomit the other night when, in a reply to one of my posts here, someone from India in particular had the gall to quote the FSF's party line on morality and principle.

    I know exactly why Stallman is so popular in India; it's because Linux is one of the primary elements enabling India to do a role reversal with the US as an economic member of the Third World. If you think it's because contemporary Indians take after Gandhi in being pillars of virtue and caring about the FSF's "principles", then please, pass me some of what you're smoking.