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."
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.
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.
..why didn't he resign immediately?
It's easy to be courageous with another job waiting.
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.
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.
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.
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.
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.
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.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 / Interpretation of Tems.
-GiH
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.
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?
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.
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. 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!
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.
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.
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.
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
Bruce Perens.
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