SCO Files Response To Demand For Evidence

The Welcome Rain writes "SCO has posted its notice of compliance with the court order of December 12, which required them to produce evidence. The document itself is brief, but refers to a sixty-page supplement which lists the offending lines, and asserts that it can find more when IBM produces some of the evidence demanded of them by SCO. Millions of lines on sixty pages? How silly."

Comments

Files and line numbers may be sufficient

[int2str]

You can fit a lot of files and line numbers on 60 pages, so I wouldn't dismiss it just because of the "millions of lines of code".

Now my experience with legal documents suggests that it's hard to say much in 60 pages legalese periods, but the note that they complied with the courts request is not enough to speculate on how valid their response is. We will have to wait until the judge (and IBM) have read it.

Re:Files and line numbers may be sufficient

[rgmoore]

But it's not sufficient for them to list the lines of code that they think are in violation. They also have to say why they think so, how SCO got the rights to them, what evidence they have that IBM put them into Linux, who else might have seen the code, and what steps SCO has taken to prevent those others from disclosing the code. That's a heck of a lot of information, and that's just about the code disclosures. SCO is also supposed to be answering questions about IBM's alleged unfair competetion, interference with trade relations, and breach of contract. For each of those allegations, SCO has to provide a detailed description of who at IBM did what when. I think that they'd have a hard time putting all of their allegations about one of those topics into 60-70 pages, much less all three and a detailed answer about all of the code that IBM has supposedly misappropriated.

My gut feeling is that the big consequence of this is that SCO will be forced to drop most of their claims. Their only real argument (and this is streching the idea of a real argument pretty far) is that IBM violated the confidentiality provisions of the Software Licensing agreement. IBM's actions in donating RCU and JFS are quite well documented, and would constitute a violation under SCO's reading of the agreement. I have a hard time imagining a judge or jury buying the "All Your Code Are Belong To Us" interpretation, but it's the most reasonable and best supported argument that SCO can make.

Are we going to learn our lessons, or what?

[vkg]

So, ok, the SCO case might be beginning to crumble. Might take a little longer, and who knows, with M$ looking for any shot it can take, there might be more problems in future.

So what are we going to do about it? Are there any measures the open source community can take to prevent contaimination of the open code base with improperly cleared code? Can we look at this as a subset of the more general "malware CVS committs?" problem? Should we have coders sign contracts stating that they have all appropriate rights to what they are about to commit so that we can offload liability to them?

Open Source Programmer insurance couldn't be far behind that....

Anyway, your thoughs please!

Re:Are we going to learn our lessons, or what?

[burnin1965]

My thoughts? It seems you are assuming there is a lesson to be learned here for the open source community, I suggest there will be no lesson to learn until we get some results from this case.

Furthermore, I believe that if there is a lesson to be learned then it is a lesson for all software developement models. Just because you cannot see the source code in a proprietary model does not mean they aren't using stolen code.

In fact, considering that most EULAs provide virtually no protection for the end user in the event that a proprietary vendor is using stolen code I would have to say that all end users should start demanding open source to ensure they are protected.

So, considering the vast volumes of open source code out there and there is only one court case, which appears to many including myself to be a facade, I'd say the mere fact that open source is open provides a significant deterrent to contributors to introduce stolen code, they will be caught.

burnin

Re:Are we going to learn our lessons, or what?

[6.023e23]

How does one go about critiquing an Open Source programmer's code as far as IP ownership goes? Or ANY programmer for that matter? You're taking it on their word that the code they submit was written by them and has no encumberances. The best you can do, IMO, would be to have signed affidavits from the programmers to such effect - proving the IP ownership would still be all but impossible. And how many programmers do you think would want to bother with signing an affidavit for every project to which they contribute? And how many projects are going to want to deal with the overhead? Of course you could require licensing/registration of all programmers... "Excuse me sir, but do you have a license to operate that there keyboard?" Methinks not.

SCO Bending the Truth

[tobechar]

Can't SCO get into trouble for lying about 6 million lines of code when the code fits into 6 pages?

There has to be some type of legal mechanism that would penalize them for this. Quite the oversight if you ask me.

So, in response to an order to produce evidence

[kfg]

what they have done is produce an abstract.

An abstract that merely refers to an unsubmitted index.

Ummmmmmmmmmmm, guys? That's not evidence.

The line listing is evidence.

You guys can make up any inhouse doofy theory of law you wish, but the fact of the matter is, and the court has made some attempt to explain this to you and placed you under compulsion, the claimant must produce the evidence that their claim is justified. The defendant need do nothing until such time because the defendant is only required to defend itself against the filed evidence.

Which part of this don't your high payed lawyers understand?

If you're lucky the judge will say, "Ummmmmmmm, nice try, you've got one more chance at getting it right. I presume counsel has had at least basic training in the rules of evidence?. . . Good. Please apply that knowledge in future."

If it were me I'd simply toss their asses out for noncompliance and a side order of legal arrogance.

KFG

Don't bet on a buyout. SCO will die alone

[bckrispi]

IBM, I believe has no interest in purchasing SCO as part of a settlement. There's no chance in hell that M$ will pick them up. They are still appealing the fact that they are a Monopoly based soley on the fact that they own Windows. The FTC/SEC would never approve a buyout that would make MS the owners of both Windows and Unix. That would be, like, a monopoly^2

Millions of lines

[Anonymous Coward]

(Hold off on the troll mods people, read and think first)

"Millions of lines on sixty pages, how silly"?

Now that's silly. Trying to make something look silly by using statistics, have you even seen the pages? The fact is, if SCO can prove it's case in sixty pages (or more if this is only part of it) in a court room with a presiding judge then it will win, end of story.

What we're going to see is SCO drill down to the most tiniest bit of code with their so called expert witnesses asking where the code came from and how it got there. We may even see some linux kernel developers subpoened? This could get ugly. Once you get to microscopic levels of looking at code and a few sleazy tricks (observational selection of code) then a judge might start to be convinced. You won't be able use the argument, "well that's just some code your honour in an ocean of code".

Read before embarrassing yourself

[rjamestaylor]

The purpose of drawing attention to the number of lines on the page wasn't to set a maximum number of lines code that SCO was claiming as infringing. It was to point out that in 60 pages you basically have 3600 lines. That's not even enough to tell a good story, much less explain $3 Billion worth of infringement claims. The preface to such a document would be 60 pages. In this case SCO claims millions of lines of code infringe. To be taken seriously, they would have to not only give the range of lines and files that infringe (which they already did) but explain (1) what is infringed upon, (2) how they conclude that there is infringement and (3) how it relates to IBM -- at a minimum! Remember, they already did the All these files, your Honor trick. Didn't work -- the Judge said 'with specificity'.

So, don't be like the other idiots who responded to this post and argue "ya but I could claim every atom infringes in just one line!" Sheesh.

Re:hmmm

[Anonymous Coward]

"It is the burden of the plantiff to prove their allegations. Considering that Linux source is available, I don't see why SCaldera needs ANYTHING from IBM to "prove" their "millions of lines" allegations."

SCO seems to be making two related allegations. One is that there is use of SCO copyrighted code in Linux. The other is that IBM has contributed "Unix" code (which by SCO's reckoning, seems to be anything that ever ran on a unix box) to Linux in violation of their licensing agreements with SCO.

If essentially any AIX code is covered by the Unix license provisions, then any AIX-derived code contributed to Linux would be in violation of the license. But SCO would have no way of identifying it, since SCO doesn't have the AIX source. So SCO would need that source from IBM before they could say what the license violations are.

Now, I don't buy SCO's expansive interpretation of derived works as related to the licensing provisions. But I think it is logically possible that IBM could have violated the license without SCO being able to point to the offending code. What an appropriate course of action would be in that case for someone in SCO's position is hard for me to say.

That being said, I'm looking forward to the day when you can see Darl McBride on the sidewalk with a cup in his hand and a sign saying "Will sue for food."

Re:SCaldera seems REALLY desperate...

[stwrtpj]

The SEC really needs to get involved, NOW.

Sorry to pick on your specific post, this is more directed at the /. crowd in general.

Look everyone, get it through your heads right now: The SEC does not give a shit about this case. SCO is not big enough to warrant their time, SCO does not have enough shares out on the market to affect the market as a whole, and, like it or not people, SCO has not done anything wrong in the eyes of the SEC.

Now before I get flamed for stating that SCO has done nothing wrong, please reread what I just said: They have done nothing wrong in the eyes of the SEC. The SEC cares only about the big players of the market. Smaller companies like SCO do not show up on their radar unless they do something really horrendous. We can shout "pump and dump! pump and dump!" until we're blue in the face, but all the evidence to date is circumstantial.

Besides, we don't need the SEC. SCO's case has more holes in it than swiss cheese. IBM is going to stomp all over them and salt the earth over their remains. But don't expect any help from the government on this, folks, and frankly, we don't need it.