Showing posts with label Mono. Show all posts
Showing posts with label Mono. Show all posts

Thursday, November 25, 2010

Attachmate, Novell and the sale of 882 patents to CPTN Holdings, a consortium organized by Microsoft

On Monday I attended a European Commission and European Patent Office conference on intellectual property rights and standardization (I blogged about it) when the long-awaited acquisition of Novell was announced. I received questions about it but for lack of information wasn't able to say anything of substance at that point.

Relatively speaking, it's easier to comment on new patent suits because once one obtains a copy of the complaint, there are usually various aspects worth looking into.

Just so you're not disappointed if you read further: there still isn't anything spectacular or dramatic about this Novell transaction and I guess there never will be. But it is an important deal for open source, so I'll sum up what I've read and what I think so far. Let's talk about the projects first, then the patents.

Mono

Miguel de Icaza, a Novell vice president who started the Mono project (a FOSS implementation of the .NET API) and previously founded the GNOME project, reassured the Mono community with this tweet:

"After the Novell acquisition, Mono continues as-is, but our paychecks will come from Attachmate instead of Novell."

A few months ago I disagreed strongly with Richard Stallman after I read an interview with Glyn Moody in which RMS said that developers "shouldn't write software to use .NET. No exceptions."

I don't know if any of those Mono critics will restate their baseless concerns, but at any rate, I believe that the acquisition of Novell is positive for Mono. It ends a period of uncertainty for the brilliant team Miguel leads. Miguel's blog indicates that they are being very productive these days.

SUSE and openSUSE

I remember the time when SUSE was capitalized differently ("SuSE") and often spelled with dots ("S.u.S.E."). That German Linux distribution used to be much more popular in Europe than Red Hat Linux. At an online gaming startup I co-founded and managed in the late 1990s, we used SuSE on our servers. I also ran SuSE on a computer at home (for MySQL).

Later, SuSE was acquired by Novell and renamed "SUSE" because people struggled with the lowercase "u" in the middle of an otherwise all-caps name although the SuSE team liked that kind of silhouette: they named one of their key differentiators YaST ("Yet another Setup Tool"). SoME SeEM To LiKE ThAt.

A few months ago I blogged about IBM's discriminatory pricing strategy in the mainframe business and mentioned z/Linux, the mainframe version of Linux. SUSE has been the market-leading mainframe Linux distribution all the time and still has a market share of 80% (worldwide).

I'm sure that SUSE is a pretty substantial part of the value that Attachmate saw in the acquisition. There's a lot of potential to narrow the gap between SUSE and Red Hat. For a company that doesn't own much intellectual property, Red Hat's margins are unbelievably high, suggesting to me that SUSE has a world of opportunity if it executes well. An open source model doesn't guarantee low prices all by itself: market dynamics still depend on effective competition.

Attachmate has already emphasized that SUSE will be run as a stand-alone business unit, and that the openSUSE community project "is an important part of the SUSE business" and "no change to the relationship between the SUSE business and the openSUSE project" is expected as a result of this deal. Pascal Bleser, a leader of the openSUSE project, writes on the official openSUSE blog that "the openSUSE Project has had, since its beginning, a very vibrant cooperation with Novell, especially with Novell’s SUSE business". Now he and his team "are looking forward to continuing this once Novell and SUSE become part of Attachmate!"

882 patents to be acquired for $450 million

My focus on this blog is on how patents get used -- from an open source angle -- and not on the secondary market for patents. But I do know that numerous patents are on the auction block all the time: some are sold individually or in smaller packages, others are sold in large blocks. Deals come in all sizes. For example, a Morgan Stanley analyst estimated six months ago that a portfolio of 4,500 Nortel Networks patents and 1,000 patent applications was worth in excess of $1 billion.

The structure of the Novell deal appears to be such that Attachmate pays $6.10 in cash per share of Novell (NASDAQ:NOVL) shareholders, a total of approximately $2.2 billion. Since Novell has, according to certain reports, cash of approximately $1 billion in the bank, this means an "enterprise value" of approximately $1.2 billion. The price to be paid already takes into consideration that a Delaware company named CPTN Holdings LLC will acquire "all of Novell's right, title and interest in 882 patents [...] for $450 million in cash" (I quoted from the SEC filing related to the acquisition, to which the merger agreement is attached).

A list of those patents is not available. Some have pointed out that 882 is a greater number than that of all patents registered in Novell's name with the USPTO. This led some to believe that the number includes some patent applications, and it may. It's also possible that Novell acquired the ownership of some patents that have not yet been re-registered in its name.

But the one piece of information that could make a major difference is whether that count relates to 882 patented inventions or 882 per-jurisdiction patents. Software patents are granted in almost all of the industrialized world. In an analysis of international equivalents of patents over which Apple, Paul Allen's Interval Licensing and Oracle are suing other companies, I gave examples. I found that a certain Apple touch-screen software patent was filed for in the United States, Canada, China, South Korea, Japan, Australia, and 34 European countries. Depending on the approach, this could count as 1 patent, 7 patents (if Europe counts as one patent because of a centralized examination process at the EPO) or as 40 patents (since an EPO patent is a bundle of national patents, each of which results in additional costs, gets a separate patent number and would have to be enforced separately in its jurisdiction with potentially different outcomes; the number of countries in which an EPO patent actually gets registered varies greatly, with the 34 countries in that example being close to the maximum).

Financial structure: $2.2 billion for Novell minus patents plus $1.4-$1.5 billion

Attachmate offers to lay down $2.2 billion in exchange for a company that will, following the patent sale, have $1.4-$1.5 billion in the bank. That makes the transaction more affordable, and NOVL shareholders benefit because they will get to sell their stock at a price that is 28% higher than before a hedge fund named Elliott Associates (which already held a chunk of Novell shares at the time) made a buyout proposal. Attachmate's offer is 9% higher than the closing price on the last trading day before the Attachmate-Novell announcement.

Wall Street clearly believes in this deal. Yesterday NOVL closed at $5.93. This means that investors buying the stock now will -- all going well -- realize a 3% gain, which is a good deal for the "arbs" (risk arbitrageurs) if the deal closes quickly. They need a certain margin since every once in a while a deal may fall through for whatever reason and then they may have to sell their holdings with losses. A 3% margin so shortly after the announcement suggests that those professional speculators expect the deal to close on those terms relatively quickly. It's a nice margin for a virtually certain quick flip but wouldn't make sense otherwise.

It's also a good sign that Elliott -- whose buyout offer got the ball rolling earlier in the year -- "will become a shareholder of Attachmate under the latest offer" (as Zacks.com reports). Some thought Elliott's offer in the spring wasn't serious and was just meant to force a sale. However, by putting its money where its mouth is, that hedge fund shows it really believes in the longer-term value of the combined company and wasn't merely looking for an exit strategy concerning Novell.

In this financial context, let me restate a disclosure I previously made in connection with possible investments in mainframe software companies: at the time of publication of this posting, I do not own stock (or related derivatives) in any of the companies mentioned.

Patent holding consortium organized by Microsoft

The fact that Microsoft organized CPTN Holdings LLC, the consortium that agreed to buy those 882 patents, has made waves in the media. I have seen worries expressed over this fact in articles by Steven J. Vaughan-Nichols ("Dark horse Attachmate buys Novell, Microsoft helps"), Dana Blankenhorn ("Novell sale shows its control by Microsoft"), Katherine Noyes ("Microsoft's Hand in Novell Deal Bodes Ill for Linux"), Rob Enderle (who sees Red Hat and Google as "first targets" of a "creative" IP strategy), and Timothy Prickett Morgan, who asked:

"Novell shareholders have to wait to see exactly what Attachmate is selling off to Microsoft and then ponder the deal. Wouldn't it be funny if Microsoft ended up owning whatever rights to Unix that Novell thinks it has?"

The wait-and-see approach is right. Actually, the other journalists -- all of whom I really respect -- also made it clear where the facts end and their gut feelings begin.

CPTN Holdings LLC is a consortium organized by Microsoft but involving other "technology companies". Names, numbers and the allocation of shares are unknown at this stage, but it's certain that the decisions of the consortium will not be taken by Microsoft singlehandedly. That fact should actually give a lot of comfort even to those who don't want to trust Redmond.

No big difference

I previously commented on Microsoft's cooperative approach to patents and still can't see any reason to be particularly concerned about. (I could, however, put together a whole list of other patent holders I would be uneasy about.) Microsoft's dispute with Motorola is just one of many in the smartphone context. So even if Microsoft bought those patents directly as opposed to being just one of several shareholders of CPTN Holding LLC, I wouldn't be concerned.

Mary Jo Foley, famous for her intimate knowledge of Microsoft, looked into "Microsoft's role in the Novell-Attachmate deal" and quoted Horacio Gutierrez, Microsoft’s Corporate Vice President and Deputy General Counsel of Intellectual Property and Licensing, with a business-as-usual statement.

I just want to be rational. The prospect of a company that already owns about 15,000 US patents -- and uses them pretty reasonably -- acquiring indirect, partial ownership of hundreds more doesn't set off an alarm on my end. At their current rate (roughly 3,000 new US patent applications a year) they file for that number of new patents every quarter, and I'm sure many of those -- as well as many patents obtained and held by countless others -- read on some open source software.

Software patents are a fact of life. Even if all of those 882 patents were invalidated overnight, the patent threat to open source wouldn't be diminished in any noteworthy way.

I also don't subscribe to theories that the Open Invention Network plays any role in this transaction. The OIN doesn't appear to impact anything too much. I have yet to see a single verifiable success story involving the OIN. My guess is that Attachmate will look at all of the partnerships Novell has in place, continuing with those that deliver tangible value and revisiting those that don't. The patents that are sold to CPTN Holdings LLC will be outside the scope of the OIN, but that could happen to the patents of any other OIN member or licensee. Other OIN companies, especially IBM, are far bigger patent holders than Novell.

A year ago I warned against the acquisition of MySQL by Oracle. The FOSS community was divided, but today hardly anyone describes Oracle as a good steward of the open source assets it acquired. Some argued that the acquisition was a way to prevent Microsoft from acquiring Sun's patents and using them against open source, but Oracle's suit against Google proved that preference completely wrong.

I will continue to watch this process, of course, and I will discuss relevant new information if and when it becomes available.

If you'd like to be updated on patent issues affecting free software and open source, please subscribe to my RSS feed (in the right-hand column) and/or follow me on Twitter @FOSSpatents.

Saturday, July 17, 2010

Richard Stallman's Mono and DotGNU patent concerns

Glyn Moody, a true FOSS expert among journalists and author of the OpenDotDotDot blog, has interviewed Richard Stallman, the founder of the software freedom movement, by email to discuss RMS's concerns over software patents in connection with free implementations of the .NET programming interface (Mono and DotGNU).

Glyn's article was published by Computerworld UK.

To sum up the key points, RMS stated the following in the interview:
  1. Due to patents held by Microsoft on its .NET technology, the availability of two .NET implementations (Mono and DotGNU) under free software licenses doesn't mean that free software developers should, according to RMS, write code for the platform. His call on the free software community: "You shouldn't write software to use .NET. No exceptions." RMS says that Microsoft could one day use patents against free .NET implementations.

  2. RMS thinks that the C# ("C Sharp") programming language should also be avoided. He makes a distinction between that one and .NET because C# was "standardized by a standards committee" and Microsoft made "a stronger commitment" concerning patents than for alternative implementations of other elements of .NET.

  3. As a requirement for RMS to encourage the development of free software on free implementations of .NET, Micosoft would have to "make an ironclad commitment that its present and future patents will never be used against implementations of DotNET."
The exchange between Glyn and Richard has raised important questions and resulted in interesting answers. I agree with RMS on the incompatibility of software patents with the notion of free software and on many other patent issues, but I don't think the advice he gives to the developer community makes any sense at all in this particular case.

RMS's utopian advice runs counter to commercial logic and fails to advance the cause of software freedom

Adopting his advice would be an utterly stupid decision for any developer from a business point of view, which is actually normal because RMS's agenda is all about software freedom and not at all about commercial success. But even from a non-commercial free software point of view I think this kind of advice doesn't make sense in the world in which we actually live.

The only alternatives in terms of programming languages and platforms that could perhaps be supported under RMS's premises would have had to be open-sourced in exactly the same form more than 20 years ago (without even the smallest modification made ever since) and then the new software one writes on top of it today wouldn't be guaranteed to be truly free software for another 20 years. 20 years is the potential life expectancy of a software patent, and I'll explain the logic of this further below.

So unless someone wants to waste 20 years or even an entire professional life of 40 years just for the sake of an ideology, it's better to reject such utopian advice and take a realistic perspective on patent-related risks.

There's no particular reason not to develop software for .NET (as compared to any other platform on this planet), and free implementations of .NET such as Mono and DotGNU aren't really less free than a free Java application server or a PHP interpreter for Apache.

RMS focuses on the lesser risk and ignores the greater one

The fundamental mistake made by RMS in the aforementioned interview is that he narrows the whole patent-related risk down to only one company (Microsoft), which actually has a stronger commercial interest than any other in the world to make the .NET platform popular and to ensure developers succeed with the applications they build on top of it. And we all know how much competition there is between platform companies for the hearts and minds of developers. More importantly, Richard completely ignores the fact that hostilities against Mono and DotGNU could also come from other patent holders.

Even if one sides with RMS concerning what the greater risk is and rejects my business logic for the platform company itself being most likely to want the best for its application developers, no one can reasonably deny that there's a huge number of patent holders other than Microsoft whom RMS fails to take into consideration. That mistake is sufficient all by itself -- regardless of how to assess the different risks -- to prove RMS's advice concerning C#, .NET, Mono and DotGNU wrong in the sense that there are also patent risks concerning any other programming language or platform out there.

Yes, free software is incompatible with patents, but software patents exist on pretty much every kind of software technology and therefore I don't think one can make the case that free .NET implementations or software written to run on them is inherently less free than other software available under the same licenses.

Time heals the wounded and invalidates patents

In the patent minefield that exists, there's no such thing as a reliably patent-unencumbered programming language or API (application programming interface) except for a hypothetical scenario of no practical relevance. That scenario is one in which all patents that may read on the platform have either expired or can be easily invalidated.

Since software patents (at least in the jurisdictions I know) have a maximum term of validity of 20 years and patented ideas must be new by the time of the application (or they can be invalidated later on the basis of "prior art"), one can argue that if software was published (as open source) more than 20 years ago, all patents will either have expired or the published source code (which should be time-stamped to prove its vintage year) could be used as prior art to take down younger patents on the same technology.

Therefore, free software developers would have to use free platforms that are more than 20 years old (and were published as free software back then, not just later). The applications they write couldn't be guaranteed to be patent-unencumbered for another 20 years after the publication of their source code.

In other words, the price to be paid for a guarantee of being patent-unencumbered is to be decades behind the evolution of technology, and to be extremely patient relative to the duration of a human professional life.

The pragmatic alternative is to regard free software as a great idea and a wonderful vision, but to understand that patents make all software potentially non-free, regardless of whether the patents in question are held by Microsoft or anyone else.

The solution proposed by RMS (an "ironclad commitment") would be desirable but insufficient

At the end of the interview, RMS made the proposal I mentioned in item 3 of my summary of his position at the beginning of this posting. He said that Microsoft should make an "ironclad commitment" not to use current or future patents against free implementations of the .NET API.

I, for my part, would very much welcome such a commitment. But I disagree that it would make all the difference that RMS suggests it would make. It wouldn't solve the problem of third-party patents. Every other current or future software patent holder in the world would also have to make that promise in order for RMS's vision to materialize.

The second part also applies to platforms for which the original developer makes an "ironclad" patent promise. Even a free programming language like PHP can infringe and almost certainly will infringe on some third-party patents out there, unless you take a programming platform that was open-sourced more than 20 years back (as I explained further above).

So I strongly recommend to focus on how patent holders actually use their rights. In that respect, I will comment on Microsoft in greater detail in some other posting, but I can already say at this stage that there simply isn't any evidence of Microsoft using patents in a way that would drive companies out of business or jeopardize the existence of FOSS projects.

Don't cut off your nose to spite your face

RMS also refers to Eben Moglen's assessment that Microsoft's Open Specification Promise "is not something we can rely on." I can see why Richard and Eben say so. But I can also see reasons for which one could say the same about (to name but a few examples) Red Hat's patent policy, the promises Oracle made concerning the acquisition of MySQL (without wanting to comment on what Oracle is doing now), Google's vague assurances concerning WebM, the Open Invention Network's arbitrary scope of protection, or IBM's broken patent pledge.

Concerning IBM's pledge, I remember that RMS also commented on it unfavorably back in 2005 when it was made (not as aggressively as I did, but it was clear that Richard also rejected that approach). So he's aware of the fact that vendors don't make those public commitments in an "ironclad" form. That's a general problem and it's not particular to .NET, C#, Mono and DotGNU. Nor are the other concerns voiced by RMS specific to those technologies.

That's why I think a decision to write software for .NET, or to implement .NET interfaces in free software, isn't a statement against freedom any more than using any other current platform: Java, PHP, you name it. But acting in accordance with RMS's advice would be a self-imposed restriction of freedom, for no good reason.

With the greatest respect (which he deserves), he sometimes proposes to cut off one's nose to spite one's face.

If you'd like to be updated on patent issues affecting free software and open source, please subscribe to my RSS feed (in the right-hand column) and/or follow me on Twitter @FOSSpatents.