A little background here: If you refer to the Novell/Microsoft not-quite-license as "eating a bug for money" (as I did in a conversation with Jeremy Allison) you get a call from Novell. Not surprising, I guess. I really want to understand this patent thing from Novell's point of view, so I talked with Carlos Montero-Luque, Justin Steinman, and Kevan Barney. Pretty high ratio of questions asked to questions answered, but I'm starting to get the point.
From Novell's point of view, the deal is supposed to be about giving customers some peace of mind over being sued for patent infringement. But the document that is supposed to explain this to customers is missing some information, and the documents that are actually supposed to contain the missing information are secret.
I don't think this is some big conspiracy, just the result of rushing something through without reading it very carefully. Novell and Microsoft are too big to pull off a conspiracy, but they're both bureaucratic enough to do paperwork that ends up being full enough of dumb mistakes to be pretty much meaningless.
Simple things first. If you still believe people read this stuff, try reading it. Covenant to Customers has two obvious mistakes: Novell spelled "Novel" and the awkward "on account of a such Customers' use of specific copies", which looks like the result of someone starting a singular-to-plural edit and not finishing. The page has been up since November 2 of last year. Not a big deal, but like I said, nobody reads this stuff.
Now go back and read "Covenant to Customers" again. You get a bunch of Capitalized Words, some of which show up in the definitions section, and some of which don't. One of the terms is "Clone Product". You don't get sued for running a Covered Product, but Covered Product doesn't include Clone Product, and Clone Product isn't defined. So which of the products included in the SUSE distribution are Clone Products? I asked, but that list is not available.
Justin Steinman: "Two examples of what might be considered a clone product might be OpenOffice.org and Samba, to be specific. Both of those are open source technologies that mimic technology offered by Microsoft."
But no, you don't get a list of what is and isn't a clone product, and Steinman says, "All the end customer really cares about is if they are using anything that is part of the SUSE Linux Enterprise platform they have a covenant not to sue from Microsoft."
You have a Covenant, so you're all squared away, right? But the Covenant says it covers Covered Products, and Covered Products doesn't include Clone Products, and you don't get a copy of the definition of Clone Products. Covered or not? You're just as mystified about the answer to "Will Microsoft sue me?" as you were before.
Another good one: "Microsoft reserves the right to update (including discontinue) the foregoing covenant pursuant to the terms of the Patent Cooperation Agreement..." Yes, the Patent Cooperation Agreement that you don't get to see.
Put it all together, and you get, "We promise not to sue you for running some but not necessarily all of the software you get from Novell, unless we stop promising not to sue you, and we won't tell you which software you get from Novell we might sue you for now, or under what circumstances we'll stop promising not to sue you for the rest."
If you were doing a EULA parody site with a voting system, people would reject this kind of thing as too over the top. "By opening the box you agree to the EULA inside the box" is one thing, but this is a little extreme. But nobody reads this stuff.
So, as a Linux customer, Novell user or not, it looks like you have the same protection from a Microsoft lawsuit after this deal as you did before. Linus Torvalds told BusinessWeek, "I'm not that concerned about the threat of Microsoft enforcing patents against Linux. I think their mode of operation isn't through the legal system. I think they hate lawyers more than most companies. They've been on the receiving end. [CEO Steve] Ballmer and [Chairman Bill] Gates have pride in the fact that their competition may have tried to crush them with legal wars, but they overcame. I think they would have a hard time using legal tactics. They would be ashamed."
That sense of wanting to win by product, not by litigation, is what protects you in the short term. What protects you long term is that the IT industry is just a series of recruiting contests. A company wins recruiting contests by serving good fajitas and letting an employee get a $70 laptop power supply without spending $200 in time on getting approval to buy it. A company loses recruiting contests when it's seen as succeeding through legal attack, not great product. Who wants to work on a product that customers have to be sued to buy? If a company's litigiousness makes it miss a round of recruiting, it misses the round of product that those recruits would have built, and game over.
Anyway, the check is cashed, the bug is eaten, Microsoft seems equally likely to sue you for running Linux no matter where you get it -- not very -- and if all goes well, a lot of that money will go to the many helpful, hard-working developers at Novell who are doing useful work. I guess what I learned here is that the patent deal doesn't really give Novell customers any special assurances. The combination of Covenant and secret agreements means that Novell customers are in the same boat as other Linux users, and isn't "hanging together" on patents the whole point?
Podcast interview with Jane Silber and Carl Richell
Tune in to our podcast for the answers to your Ubuntu questions. What's new in Ubuntu's "Feisty Fawn" release, what does Canonical offer to system integrators, and how many virtualization systems can one distribution offer?LinuxWorld Conference and Expo San Francisco, August 4-7, 2008.
Linux Plumbers Conference Portland, OR, Sept. 16-19, 2008.
FreedomHEC Santa Monica, November 8-9, 2008.
|
|
Sponsored links |
nice
Hey! nice analysis. Maybe the best I've read.
I read this stuff
Keep up the good work, Don!
If you can digg up which big customers bullied their supplier Novell (I can spell it, and I'm not even a native speaker ;-)) into barfing all over the place in stead of fixing their heterogenous network by making it GNU/Linux homogenous server side and save money at the same time it would be a real treat. If only the pointy haired bosses of the world would leave ICT alone... sigh... even deeper sigh ...
What is wrong with these people? Am I a brain surgeon? No. Do I try to act like one? No. Why do pointy haired bosses try to act like they know ICT and state ICT goals in the particular ALL THE TIME: "We need Exchange, we need Microsoft Office" in stead of "We need e-mail and a shared calendar, a word processor and a spreadsheet application".
Aaaaarrrrgggghhhh!
The Exchange-enabled management team
Look at a group of managers, executives, and assistants who use Microsoft Exchange routinely, though. There is a bunch of well-thought-out workflow in that program for things like "let's have a meeting Friday of everyone on the example.com account plus Bob, but Bob is on an airplane today so we can't ask him for a good time, but we need to get the meeting time nailed down today so we know when to tell the example.com people we can go see them."
People who do lots of meetings are to Exchange as people who do lots of source code merges are to Bitkeeper. You can give them a less featureful solution because it has other qualities you prefer but they _will_ complain about it. If you set Exchange up right, which is a social/technical skill like anything else in this business, the software gives the executive the best of both worlds: a calendar application he or she can check any time and access for an assistant who is empowered to help with scheduling. So often the person who most appreciates MSFT Exchange is the C*O who controls the software budget.
If your employer hires a corporate VP who is used to using Exchange and has any influence at all over the IT budget, it's likely to spread to your company, too.
A properly-configured, reliable Exchange does require an Exchange consultant/guru and substantial infrastructure to get working, though. Will be interesting to see if Google Apps for Your Domain is able to creep up on Exchange from the low end of the market.
It's not the software, it's the pointy haired decisions
My point was not that Microsoft Exchange is a bad piece of software - its not if you use in a Microsoft only environment. I'll even admit to having liked working with it in a homogenous environment. However, that was not my point, so I'll try to explain more fully.
You are completely right - management likes to invite each other to meetings and exchange documents - and that's the point. The task can and should be described by management in a vendor independent way.
Why is this important? Because I believe in free (as in freedom) software and know that it can be done with free (as in freedom) software? I do believe that, and I know that to be true, but NO WAY!
It is important independent of which vendor or philosophy the manager chooses, exactly because the manager cannot fix bad workflow or reach business goals with software - the manager needs people for that, people with different skills.
It is unusual for the head of the ICT department to also be an expert at marketing and sales, thus no decisions about it are made by the head of the ICT departement.
It is unusual for the head of marketing or the information officer to be any good at creating LAN and WAN links over VPN to branch offices. Thus no decisions about it are made by the head of marketing.
Yet it is usual for pointy haired managers to demand a *particular* piece of client side software based on no ICT insight what-so-ever which requires a vendor specific protocol to get or send files to anyone else, or a particular database server, or a particular web browser, creating a heterogenous environment as it cannibalizes its way into server space. That's not good managment - its bad manners to shit in someone elses department. Yet they do it time and time again - they never learn. It's not the software, but the pointy haired decisions.
All true, but there comes a point...
There are some underrated rules here that account for a lot of the success of Microsoft Exchange.
1. People usually prefer what they already know, so they need a reason other than price to switch.
2. People who travel a lot want something that works well offline.
3. Every project has a secret requirement that is never written down but you have to adhere to anyway: "Make it work like the decision maker expects it to work."
Thanks to ASP/SaaS, the days of "BOFH" IT departments inflicting the department's choice of software on users are over. Give Management an email/calendar solution that doesn't follow those three rules, and you could come in to find that the new plan is shut the mail servers down, we're bringing in a hosted Exchange company.
(And I hate to say it, but marketing departments make an awful lot of IT decisions these days. They don't get the web apps they want from IT, and even if they did non-employees couldn't get on the company VPN, so the marketing department just puts their stuff on a 37signals app so they can share it with all the consultants and contractors they hire.)
Novell made a deal with the
Novell made a deal with the Devil because Novell was hemorrhaging $$. What Novell doesn't realize is that people like myself are the ones who make the decision which Linux distribution to purchase/use. When we see stuff like this we basically right off Novell entirely. The real Linux experts/enthusiasts are the ones who have been using it day in and out for 10+ years. The problem for Novell is those Linux experts have also spent the last 10 years climbing the corporate ladder.
This whole IP thing is simply the next stage because no one gives a crap about the SCO outcome anymore. Microsoft realizes that they are going to have to keep the FUD machine going themselves. As someone else so eloquently stated on Slashdot. "Sue someone or shut the fuck up."
Not really about the money.
Au contraire.
Novell did have some opportunities to do deals that depended on either or both of (1) supported hetereogeneous (MSFT on Linux or Linux on MSFT) virtualization and (2) making the Microsoft guy who was shaking the customer down for a patent license go away. The announcement did help Novell close those deals, but not because it really offers any patent assurances that the customers didn't have before.
What's really going to be interesting is finding out if customers can get support for Windows applications on Windows guest/Linux host. Any Exchange customers want to ask your Microsoft contacts if you can keep your support in full force if you move it to a virtual machine on SUSE?
Something for Nothing
Microsoft promisses nothing. (Your analysis isn't the only one to come to that conclusion.)
Microsoft gets the promise that Novell won't sue it for patent violations. Novell is clearly seen to have abandoned it's pledge to use it's software patent portfolio to support FOSS.
That's the summary. I didn't follow the flow of dollars, that was involved.
Well... my reaction was to abandon all consideration of SuSE, to remove mono and all products that used it from my system, and to stop thinking of Novell as a company that I would like to support. I've no idea WHAT that agreement was about, but Novell now appears to have five years to slip MS technologies into FOSS code, so any code they release can't be trusted. And it appears quite plausible that mono is behind the MS tradeoff (presuming they had anything, I can't tell).
I'll grant that most people at Novell are decent and honorable. It only takes one or two in the correct jobs. That's the problem with centralized control.
"slipping in"
Two problems with this theory.
First, there are so many software patents in effect that you're likely to inadvertently infringe a bunch just doing normal work. And you don't know until an actual case goes to court which of the patents you stepped on are going to hold up. So an eager conspirator trying to slip in patented stuff is unlikely to infringe more patents than someone just working. Actually, the person working normally will probably infringe more patents, since he'll have more time to work and less time to scheme.
(Imagine that rhyming word patents were in effect, and you were trying to write a long poem.)
Second, people contribute to projects under their own names, and a developer's career is likely to outlast Novell as a company. Even if there were a conspiracy to pollute open source projects with sneaky patented code, the interests of the the people who would have to do the conspiracy's work don't align with the interests of the conspiracy.
Please try to put yourself in the position of each person in the chain and ask if you would have a good reason to do what you would have to do in order to make the "slip in" plan work.
Why would Novell want to do this?
Disclaimer: I have been using SuSE Linux since 6.x or about 7 years. I still use it and don't intend to change at this time. So if you feel that makes me evil stop reading now and move on to the next comment.
The statement:
"I've no idea WHAT that agreement was about, but Novell now appears to have five years to slip MS technologies into FOSS code, so any code they release can't be trusted."
Makes absolutely no sense to me. Even taking into account Don's comments about the particular developers, why would Novell want to inject MS code into projects. They'd just have to remove it later on. That's a lot tougher then not doing it in the first place.
As a long time SuSE user I'm willing to give Novell the benefit of the doubt. I've used it this long because for me it just works. And yes I've used other things. I've taught classes using Red Hat/Fedora. In my current job we have a few Ubuntu machines running. I've installed various small footprint distros on older hardware. And finally I lead a Linux SIG for a local general PC User Group and have people who use most of the major distros in the group so I hear about all the options.
So again I ask Why? Why would Novell want to do this?