Open Source Risk Management has been in the limelight for a while as a
result of its Linux insurance policies. This group has, just in time for
LinuxWorld, issued
a
press release on software patents and the Linux kernel. The PR
describes a survey performed by Dan Ravicher; it contains both good and bad
news. The good news is that Mr. Ravicher performed a study of all
U.S. software patents which had actually been litigated, and concluded that
the Linux kernel infringes none of them. On the other hand, 283 patents
were found which have not seen a day in court, but which could, perhaps, be
used to make claims against Linux.
It will, doubtless, come as a great surprise that OSRM is now gearing up to
sell insurance policies to Linux users who fear patent infringement suits.
A mere $150,000 per year buys $5 million in coverage.
There are certainly good things to be said about what OSRM is doing.
Insurance against patent suits may give some large users the confidence
they need to go forward with Linux development and deployment. The
insurance pool could be used to aggressively challenge the validity of
patents which are brought to bear against Linux - if the insurers choose to
take that approach. The invalidation of a couple of patents could be a
powerful deterrent for any other litigious patent holder who has thoughts
of going up against the Linux community.
A white paper
(PDF format) published by OSRM suggests that invalidation of
patents is not the only, or even first approach that OSRM will take. An
alternative which is discussed there is obtaining a license for the patent
which applies to GPL-licensed software. This license might even be
purchased:
"First of all, the patent holder can always be compensated with
lump-sum, annual, and/or milestone royalty payments," continued
Ravicher. "And, remember, the patent holder that signs a
GPL-compliant license for free and open source software can still
enforce its patents and seek money or injunctive relief against
proprietary software."
The interesting fact here, of course, is that the GPL would make it very
hard for OSRM to solve a patent problem only for its policy holders. If
patent holders decide to target those users who are insured by OSRM
(because that's where the money is), the entire community could benefit
from the settlements. But OSRM could find itself in a situation where
everybody waits for somebody else to buy the insurance and be the target.
The OSRM white paper also talks about rewriting code to sidestep patent
suits. But, says OSRM:
Re-engineering is a powerful weapon, but it must be used sparingly
so that Linux developers can concentrate on technological advances,
not alternative implementations of current function. OSRM will
consult directly with leading kernel developers, and in particular
with the Open Source Development Laboratory ("OSDL)", Linus
Torvalds' employer and the "Center of Gravity" for ongoing Linux
kernel development, to seek consensus prior to any future
recommendation for re-engineering.
One can only hope that they think very carefully before going out and
issuing "recommendations" to the kernel development community.
OSRM describes itself as "vendor-neutral" more than once in its PR. But
that is not entirely true: OSRM is a vendor of insurance products that, by
some strange coincidence, address just the threat that the PR describes.
Just to be sure you don't miss the point, the PR also discusses the
multi-million dollar cost of defending a patent suit in court. This work
may not be FUD in the normal sense, but it cannot be denied that OSRM's
press release does seek to inspire a certain amount of fear, uncertainty,
and doubt in Linux users.
OSRM is not without a potential conflict of interest here. A long list of scary
patents can only help to sell OSRM's products, so its researchers have
every incentive to be as inclusive as possible. The list itself is not
directly available to the public. Interested parties can apparently get it,
but only after being warned about exposure for triple damages for "willful"
infringement. That is a risk that many will choose to avoid, so most of us
will have to trust Mr. Ravicher when he says 283 problematic patents
exist. Then again, many people see that number as implausibly small, given
the large number of bogus software patents in the U.S.
The PR claims that "OSRM is active in promoting systematic patent policy
reforms to address the issue at its roots, patent policies themselves," but
is not particularly forthcoming on what form that activity takes. So we
asked:
This is something we address regularly as we talk with various
influencer audiences, press, analysts and policy groups. Most
recently, Bruce Perens (who is on OSRM's board of directors)
recently went to D.C., where he held several meetings with various
policy groups about the problems with the patent system, and the
particular threat to open source. We'll continue working with
those and other groups, including the Public Patent Foundation and
Electronic Frontier Foundation, to push policy reform.
Here is another statement from the PR:
What it boils down to is that Linux has patent risks; but they can
and will become conventional insured risks, just an everyday cost
of doing business. OSRM's whole mission is to make the issue of
Linux liability simple, routine, and manageable.
Who wouldn't like to become part of the "everyday cost of doing business"
with Linux? OSRM only stands a chance of collecting its piece of that
"everyday cost" as long as Linux users and developers see patent suits as a
threat. That should be kept in mind when pondering the company's
motivations and actions. The community is little served by
headlines throughout the mainstream media that Linux violates almost 300
patents, but an insurance business may well benefit.
So is OSRM guilty of spreading FUD? They say not:
OSRM has helped the community by actually studying what that risk
exactly is and concluding that it is not an unmanageable or
doomsday amount of risk. Rather, the OSRM study showed that it's a
normal amount of risk that would be associated with any software as
successful as Linux. Those who see the message as sparking fear
are not familiar enough with our messed up patent system, which is
truly the entity to blame for the results of the analysis.
OSRM also pointed out to us that it can only be successful as long as free
software is successful. Since fewer users means fewer customers for OSRM,
the company has no interest in scaring people away. People in the free
software community have been warning about patent threats for years; all
OSRM has done is to try to quantify the risk.
It is worth noting that OSRM's patent insurance will be restricted to the
kernel. The kernel, however, is a very small part of any deployed Linux
system, and litigious software patent holders will certainly not restrict
themselves to that one piece. Purchasers of OSRM's patent insurance will
not have decreased their exposure by much.
And that exposure does exist. There is no doubt that Linux will be the
target of a high-profile patent suit sooner or later. We (and many, many
others) have been saying that for a very long time, to the point that many
people may
not believe it anymore. The SCO case has shown the world just how strongly
the community will fight back when it is attacked, and how good the
community is at digging up interesting history - such as prior art. The
prospect of going up against the community may well deter a number of
casual patent shakedowns. Even
so, somebody will eventually give in to the perceived promise of easy money
(or, perhaps, the salvation of a failing business) and go on the attack.
It is just a matter of time.
Anything we can do to prepare ourselves for that day is good. Insurance
policies are almost certainly a useful part of that preparation, and it is
good that companies like OSRM are stepping up to provide those policies.
But we should not forget that OSRM's interests are not precisely aligned
with those of the community; if software patents went away, so would that
part of OSRM's insurance business. A company like OSRM must walk a fine
line; let us hope that they continue to stay on it.
(
Log in to post comments)