Jeremy Allison Resigns From Novell In Protest 344
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."
Re:Excellent! (Score:3, Interesting)
Putting your money where your mouth is (Score:5, Interesting)
I really admire people who choose to live by their principles, even when it's hard or costly to do so.
If it's a matter of principle.. (Score:0, Interesting)
It's easy to be courageous with another job waiting.
Re:I don't understand this... (Score:3, Interesting)
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?
Re:Excellent! (Score:5, Interesting)
Of course they can (Score:3, Interesting)
This makes me a sad Panda (Score:4, Interesting)
Re:I don't understand this... (Score:3, Interesting)
Intent matters in contract law. (Score:3, Interesting)
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).
Wikipedia has some information on mistake, and also interpretation: Mistake [wikipedia.org] / Interpretation of Tems [wikipedia.org].
-GiH
Novell would be the one with the fork. (Score:5, Interesting)
Okay.
But that does not seem to be happening.
So far it is just Miguel who supports it
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.
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.
Would GPLv3 protect against this? (Score:3, Interesting)
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?
Re:Excellent! (Score:3, Interesting)
Re:Red Hat Opportunity? (Score:2, Interesting)
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.
You miss the point (Score:5, Interesting)
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!
Re:You miss the point (Score:3, Interesting)
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?
They would run Windows, not Linux. (Score:5, Interesting)
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
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.
Re:It's not LGPL (Score:3, Interesting)
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.
Re:You miss the point (Score:3, Interesting)
I recommend taking the GPL Quiz [gnu.org] 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.
Re:What about Nat Friedman? (Score:3, 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.
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:
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.
Re:What about Nat Friedman? (Score:3, Interesting)
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
Re:Excellent! (Score:3, Interesting)
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.