Update: The transcript is now available.
This write-up is the combined result of the notes of Evan McNabb and Frank and Elizabeth Sorenson. We also got some notes and a chart from Mark Belnap, and Stuart Jansen helped in typing everything up. We have requested a transcript, but the court reporter said it may take a week or so before it will be available (we'll get it the same time that the lawyers do). We wrote down everything we could, and have attempted to give a general play-by-play of what happened during the hearing. Most of the wording is approximate, but when in quotes, we're pretty sure we got it word-for-word. Stuff in brackets either gives a description of what is happening or the gist of what someone said.
Judge Wells has a very small courtroom, and can accommodate approximately 20 people in the audience. About 15 people were present in the audience, including the court security officer. Before the hearing began, members of the audience chatted a little, and realized that most of us were local Linux users (vim won the quick-poll).
The SCO lawyers came in at about 9:50, and sat at the Defendant's table (left). Judge Wells' Courtroom Deputy asked them to move to the correct table (right). SCO's attorneys were Kevin McBride (Darl McBride's brother) and Brent Hatch (who wore a light suit and Christmas bowtie). Darl McBride (who arrived just before the door was closed) sat immediately behind them with another attorney (we think) whose name we missed. He had no bodyguards (unless that was who we thought was the lawyer).
IBM's lawyers appeared at about 9:57, and David Marriott and Todd Shaughnessy sat at the table. Amy Sorenson [no relation] was also present, but sat on the back row of the courtroom.
As each party entered, they checked in with the courtroom deputy, Amy Pehrson, who also asked who would be speaking for each side. Kevin McBride spoke for SCO, and David Marriott spoke for IBM. Also present was some sort of intern or assistant to Judge Wells (She jokingly referred to him as the brains), and she also made sure that he had copies of all the documents. There was a court reporter present, and she was nice and friendly, and helped us figure out how to get a transcript. At 10am, the deputy asked if everyone was present from both parties (yes), then went into Judge Wells' chambers. She emerged shortly, commanded "All rise!", and the judge came in.
Judge: I have reviewed all of the memorandums, including the most recent filings, and am up to date. [Note: We stopped by the Court Clerk's office on the way out for copies of the most recent filings, and the file was in Judge Wells' chambers--she really was up-to-date]. After reviewing everything, my intention for the day is to grant IBM's motion, and to require SCO to file responses within 30 days, or to require SCO to file affidavits as to why they couldn't respond. IBM's responses should correct deficiencies to the 11/4 addendum to include interrogatories 12 & 13. I'd like to postpone any other discovery until this has been done. [Checked with both attorneys to make sure there was a protective order in place.] I am willing to hear arguments from both sides for or against proposed intention. [Asked who wanted to go first.]
K. McBride: [Offers to start.]
K. McBride: May I have a few minutes to convince you otherwise? Because the issues are complex, and we want to suggest a more appropriate path, put the motion on hold until a specific discovery is produced.
Judge: It appears that "what is happening is somewhat circular." Seems to be failure to confer under rule 37. [Note: Rule 37 says you have made good faith efforts to obtain complete responses to the interrogatories without court action, but have been unable to do so.] We can't get off the ground until we get started.
K. McBride: What really should happen is specific discovery should be identified and then we will reply with our discovery. The case at the fundamental level is infringement. We need a clear definition of "what source code is at issue" before discussing types of infringement. "This is a complex case, your honor." [NOTE: He pointed out a number of times that this was a complex case. In case any of us missed it the first and second times.] There was some contract disputes, some copyright disputes, and some of neither. This is the frontier of interaction between copyright and contract law. [Cited Sun v. Microsoft, 1999 in 9th circuit court handed out copy of material related to case.] "Some paragraphs are worth reading." Microsoft made changes and distributed Java. The case is about interaction of copyright and contract law. [pulled out big chart and asked for permission to display it. Mark Belnap later copied this chart down, and we have tried to recreate it here]
Judge: "If you can find a place to put it, go for it." [Invited IBM to come behind the bench to see chart if necessary.] "My court room is spatially challenged."
K. McBride: [Gives small copies of chart to IBM lawyers]
K. McBride: I will give a background of licensing issues between the two companies. This case "involves the genesis of computer software for large corporations." All corporations use Unix at the Fortune 1000 level and have used it for over 20 years. AT&T started Unix and licensed multiple parties to modify it. SCO acquired all the rights to Unix. "SCO is in the shoes of AT&T." IBM had a special license, but Sequent had a standard license. There was a scope clause in the license limiting what you could use the software for. You could use it and modify it, provided it was treated as part of the original software product. IBM is obligated to maintain some kind of confidentiality under some kind of law, whether copyright, contract, or trade secrets. [NOTE: The level of specificity is McBride's, not ours.] Do we have a copyright case? A trade secret case? [NOTE: somewhat rhetorical] They can't step out of making money with it. "You can't use your stuff in violation of our license." We have no problem saying that AIX is IBM's, they just can't use it in violation of our contract. [NOTE: he did specifically state several times that they acknowledge that AIX belongs to IBM]
We need to identify first all this stuff IBM put into Linux. We know that IBM gave away source code, development methods, and sequences into Linux. "We don't have issue with the non-infringing part of Linux." "We're not making it up new." IBM did contribute stuff to Linux, "we just don't know what it is." Linux is undermining the entire Unix operating system market. We know IBM contributed stuff because they boasted about their contributions in the press.
Judge: "It isn't just IBM making public statements is it?" My concern is, I want to focus back on the question of motion to compel.
K. McBride: I'll hurry up. [Starts reading IBM quotes so fast the court reporter had to ask him to slow down. Quotes IBM about donating to Linux and making it as strong as Linux.] We're happy to live with what they've said and what we've said. Specifically addresses interrogatories 12 and 13. IBM's interrogatory 12 is not a part of the case to us, but if they court wants us to we'll do it. For IBM's interrogatories 1, 2, and 4, we need IBM to produce all versions and developer notes for AIX. Then we can compare and make very clear specification about what contributions and what kinds. Staying discovery would to tremendous injustice and keep us from explaining to the court what's what and why.
Judge: So, tell me why [she mentions two particular cases IBM brought up in their Memorandums] don't apply to this case. These cases say that the burden of proof is on the plaintiff. What is relevant to future discovery? "None of us know!"
K. McBride: Neither of these cases address our specific facts. We won't know what is trade secrets and what is contract and what is copyright until we see IBM's discovery. We will file a second amended complaint regarding copyrights within the week.
Our trade secrets claims come from the joint development starting in 1997 time frame, project Monterrey. [History of RISC and Intel platforms, no one was focusing on Intel except SCO, who spent 16 months making Unix work on Intel.] IBM was left out in the cold wihtout an operating system they could sell as Intel chips got big. In Project Monterrey we we gave them our stuff, trade secrets stuff, and they did Linux at the same time secretly, and then stepped out of Monterrey and used our stuff.
We've given everything to them, all of our knowledge and trade secrets. They have the code.
Judge: What about the pages in non-machine readable format?
K. McBride: We gave them all our source code.
Judge: But did you give it to them in 100,000's of pages of unusable text?
K. McBride: "You have to have discovery of the universe" and then we can figure stuff out.
Judge: [Turns the time over to IBM's attorneys]
D. Marriott: I will cover three issues: 1) Operating system and source code background. 2) what is at issue, proposed ruling is great 3) some examples of shortcomings of SCO Group's responses to Interrogatories.
Without software, a computer is a lump of metal. You take source code, put it through a compiler, get out 1's and 0's. [Gives the judge, assistant, and SCO's attorneys a booklet with all of his supplementary material for his arguments.] One of the pages shows an example of source code, comments in red and code in black. "Unix is a family of operating systems." Linux is also an operating system. Only Linux is developed publicly, as a "massive collaborative exercise". [explains Linux development process, and shows diagram from book--we think it is the diagram Linus and Andrew Morton presented here, and which was discussed here on Groklaw.]
show [from the book] an example email submission to Linux by an employee of SCO. SCO began in 1994 as a Linux distributor, contributed to Linux. The Crux of SCO's case is paragraph 101 [in book--we think he is referring to SCO's amended complaint].
[Holds up 2 books, one with about 200 pages in it and the other with about 500 pages. Gives copies to Judge, assistant, and SCO. McBride jokes as he gets his copy, "Is this AIX you're finally producing?"] The little book represents Unix source code, the large book represents a single file of Linux source code. They are claiming that we took some of this [little book] and put it in this [big book]. [Talked for a bit about the 2 books (each book represents a chapter of a larger book, which represents a single version of Linux or Unix). He compares sizes, subtley pointing out how silly the claim sounds. Pointed out that SCO still has not said what parts of small book IBM supposedly put in which parts of big book.] We don't even know what book [version], chapter, or file of Unix we're talking about. We don't know what book [version], chapter, or file of Linux we're talking about. [He mentions that the physical book he's holding up (the bigger, Linux book) actually contains the printout of a single file from a single version of Linux.] This file has 31597 lines, and comes from Linux 2.5.69 [include/asm-ia64/sn/sn2/shub_mmr.h fits this description].
In order to file the complaint, SCO had to have what they say they have. Case law says a party may not dump information on a party and expect them to extract relevant information. Actually, many cases that say that. We moved to compel after waiting 4 months, then got some supplemental responses that are still inadequate. There are 14,548 chapters [files] in Unix, millions of lines of code, and we don't know which lines they say we misappropriated.
It is not just IBM that has a problem with this, they are also accusing Linux users. This is like stopping someone walking out of Barnes and Noble who just bought a Linux book and saying, that book holds our stuff, now you have to pay us in order to keep the book.
[Talks about how SCO has shown stuff to other people under an NDA] "We shouldn't need an NDA, we have a protective order."
The only case that SCO quotes actually doesn't contradict our case examples. It is a copyright case which, as of now, SCO hasn't accused us of yet.
"We don't think they had any evidence at the time they filed the case and we don't think they have any evidence now." "No reasonable person could conclude that SCO has" stated their claims with specificity.
K. McBride: "There is no trade secret in Unix System 5. Copyright yes." "There are trade secrets in UnixWare... that was given to IBM in the joint development project."
"Confidential information is not a trade secret."
These are the most recent CD's produced from both us and IBM [holds up 2 CD-R's]. Ours is numbered 122, and theirs is only numbered 21. I guess we just got 22 and 23 today, but we've produced 100 more CDs than they have. IBM should be ordered to give us AIX and Dynix, then we can make more concrete allegations after 30 days.
Marriott: We have agreed to give AIX and Dynix, just not every iteration. That would be 40 million pages.
K. McBride: "We want the 40 million pages!"
Judge: "And you will digest them by Sunday?"
K. McBride: We have expert analysts who can go through it [they want 30 days to go over the code].
D. Marriott: [closing remarks] Linux is an open development model, and Her Honor can go online and see it being developed at any time.
Judge: Okay, this is my ruling, it is essential to get the ball rolling. My initial ruling stands. At this time, I will grant IBM's Motion to compel both sets of interrogatories. IBM is to add interrorgatories 12 and 13 to the listed deficiencies. SCO will have 30 days after the ruling is recorded to comply. If they can't in good faith, they should file affidavits as to why they cannot.
IBM should correct the defficiences in their addendum filed Nov 4th [to add interrogatories 12 & 13]. [Marriott needs to get the complete list of missing/incomplete stuff to McBride.] All other discovery is posponed. By Wednesday of next week, IBM should submit the order, then SCO has 30 days, and then let's have a hearing about 2 weeks after that, around mid January.
[discussing of timing, etc. Judge was willing to give more time, after the 30 days was up for briefings, but not more than 30 days to comply. Hearing set for 23 January at 10am] address remaining motions of SCO with the assumption that SCO has completed discovery with the required specificity. She is not ruling on SCO's motion at this time.
Some notes: Our general feeling is that McBride was choppy, chaotic, and random in his speaking. It felt like he was running a filibuster. IBM was direct and to the point in everything they said and did. They were prepared every time that the judge asked them a question, and appeared to be right on top of everything that was going on. SCO presented exhibits to the court that were copied and stapled. IBM's exhibits and other documents had simple comb bindings, and looked more professional.
When McBride was speaking, he wandered around the courtroom, and seemed to be talking off the top of his head. Marriott stood at the lectern and seemed to be working from well-prepared notes that he had practiced. [We enjoyed listening to his arguments]
Judge Wells seemed to have little patience for the filibuster [She stated that the proceedings needed to conclude before noon (probably lunchtime!), but with both sides having a chance to state their case]. She interrupted McBride several times to help focus him back on the point of the hearing. She was very fair and direct. She gave McBride every chance to convince her that she should not grant IBM's motions. She brought up several points that weren't directly addressed during arguments, indicating that she had read and absorbed the material, and noticed some of SCO's antics. She especially did not seem impressed about handing over the code on paper, rather than in a useable format [McBride remarked that he believed they had resolved that problem].
After the hearing, Darl turned around and recognized Evan from the protest. Darl said that he wasn't surprised about what happened, but it was what they had expected. We later shook hands with the IBM lawyers. They "like to keep up with what's going on" [partially referring to Groklaw].