SCO Accuses IBM of Destruction of Evidence 266
Udo Schmitz writes "According to an article at Forbes, SCO claims that IBM destroyed evidence by ordering programmers to delete copies of code that could have helped SCO prove its case. SCO's attorney Brent Hatch says that 'one IBM Linux developer has admitted to destroying source code and tests' and that they didn't mention this in public, because it only became relevant now, and that 'the claim was part of a motion SCO filed in March 2006, which has remained sealed'." From the article: "IBM declined to comment, citing a policy of not discussing ongoing litigation. In her sharply worded ruling, Wells criticized SCO's conduct in the case and seemed to indicate she was annoyed with the company. 'I don't know if that's true or not, but that's a question I'm asking myself,' Hatch says. Hatch concedes the Wells ruling represented a setback for SCO. But he says SCO still has a strong case. "
Re:Except... (Score:5, Informative)
Also, the longer this mess goes on, the more money it bleeds from SCO. Even the stock market is finally reluctantly starting to realize, years after Slashdotters, that SCO doesn't really have any ground to stand on. SCOX is currently valued at $2.51 a share, having lost about $1.50 or so in the past month. One source says that SCO is down to $18 million in cash. I think IBM is just trying to get them to run out of money by the time this is settled in IBM's favor so they won't be in a position to launch endless appeals of the verdict.
relevant excerpt (Score:5, Informative)
even after the Court ordered the source code to be produced, IBM failed to produce all versions of its AIX code, claiming that they cannot be located. Even more egregious was IBM's spoliation of evidence. Weeks after SCO filed its lawsuit, IBM directed "dozens" of its Linux developers within its LTC and at least ten of its Linux developers outside the LOC to delete the AIX and/or Dynix source code from their computers. (SCO Opp. Memo. (3/7/06) at 3.) One IBM Linux developer has admitted to destroying Dynix source code and tests, as well as pre-March 2003 drafts of source code he had written for Linux while referring to Dynix code on his computer. (Id. at 3-4.)
SCO has access to every version of AIX and Dynix released in recent and not so recent history and they can't identify any infringement in them. So now they're saying that the same code that were copied or cached on the developers' workstation must have had the smoking gun in it. That's a really really desperate argument. Clearly they're just trying hard to raise arguments - any arguments - that may lead to this devastating ruling to be reversed. I suppose I can't blame them lawyers for not leaving a stone unturned.
Re:Classic projection (Score:3, Informative)
In general, when providing a definition and example, you must use the word you have defined... in the example.
Re:Anyone else... (Score:5, Informative)
Re:Anyone else... (Score:2, Informative)
Re:Anyone else... (Score:2, Informative)
Re:This Brent O. Hatch is Sen Hatch's son (Score:4, Informative)