decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
IBM's Memo in Opposition to SCO's Expedited Motion for Protective Order - as text
Sunday, June 06 2004 @ 07:01 AM EDT

Here is IBM's Memorandum in Opposition to SCO's Expedited Motion for Protective Order. Thanks go to Henrik Grouleff for transcribing it.

IBM patiently explains how ridiculous SCO's request for more delay is. In addition to all the reasons we can think of, IBM points out that no discovery from them will help SCO prepare for the depositions it seeks to postpone on the grounds that it hasn't received all discovery items it just asked IBM for:

"Moreover, as SCO well knows, review of IBM's documents is not necessary for any of the depositions next week. Two of the witnesses scheduled next week, Messrs. Frasure and Wilson, are former employees of AT&T, not IBM. SCO as the purported successor of AT&T's rights, should have these documents, to the extent they exist, in its files. Similarly, Mr. Rodgers was employed by Sequent, not IBM, and IBM does not have any of his documents. The final deponent, BayStar, is an investor in SCO, wholly unrelated to IBM, and that deposition apparently will not go forward."

Footnote 1 is of interest, because it seems BayStar really wants out:

"IBM agreed to postpone the BayStar deposition provided that BayStar was amenable to doing so. IBM tried diligently to reach BayStar to discuss this issue, but BayStar has ignored our calls and letters. SCO, on the other hand, has talked to BayStar. This morning, we finally received a message from BayStar's counsel stating that the deposition would not go forward next week."

Unfortunately, the referenced exhibits are paper-only, so we don't have them yet.

***************************

SNELL & WILMER LLP
Alan L. Sullivan (3152)
Todd M. Shaughnessy (6651)
[address, phone]

CRAVATH, SWAINE & MOORE LLP
Evan R. Chesler (admitted pro hac vice)
David R. Marriott (7572)
[address, phone]

Attorneys for Defendant/Counterclaim-Plaintiff
International Business Machines Corporation

IN THE UNITED STATES DISTRICT COURT

FOR THE DISTRICT OF UTAH

THE SCO GROUP, INC.,

Plaintiff/Counterclaim-Defendant,

v.

INTERNATIONAL BUSINESS
MACHINES CORPORATION

Defendant/Counterclaim-Plaintiff

DEFENDANT/COUNTERCLAIM-
PLAINTIFF IBM'S MEMORANDUM
IN OPPOSITION TO SCO'S
EXPEDITED MOTION FOR
PROTECTIVE ORDER

Civil No. 2:03CV-0294 DAK

Honorable Dale A. Kimball

Magistrate Judge Brooke Wells

Defendant/Counterclaim-Plaintiff International Business Machines Corporation ("IBM") respectfully submits this memorandum in opposition to SCO's Expedited Motion and Memorandum for a Protective Order, filed June 3, 2004.


Introduction

     The Court should deny SCO's eleventh-hour attempt to postpone depositions that have been scheduled for almost a month. The most notable feature of SCO's "expedited" motion is the complete absence of any explanation why SCO chose to wait until just days before those depositions to ask that they be postponed, and to foist on the Court and on IBM the need to deal with this motion in an unreasonably expedited manner. In reality, as explained in more details below, there is no legitimate reason why SCO cannot attend the depositions as presently scheduled. Perhaps more important, not proceeding with the depositions would impose an undue burden both on IBM and on the third party witnesses who have been scheduled for almost a month.

Factual Background

     IBM served its notice of depositions on May 13, 2004. The notice included the third party depositions scheduled for next week - David Frasure and BayStar Capital on Tuesday, June 8, and Otis Wilson and David Rodgers on Thursday, June 10. SCO did not object to the depositions scheduled for next week, raise any issue concerning the dates on which they were scheduled, or complain that they could not adequately prepare for them. Instead, on May 26, 2004, SCO's counsel wrote a detailed letter explaining why various other witnesses could not be deposed on the dates IBM selected, and why various SCO employees would have to be deposed in locations other than where their depositions had been noticed. (See Heise ltr. to Kao, dated May 26, 2004, copy appended hereto as Exhibit A). On May 28, 2004, counsel for IBM responded, agreeing to all of the scheduling requests made by SCO's counsel. (See Kao ltr. to Heise, dated May 28, 2004, copy appended hereto as Exhibit B). During these exchanges, SCO's counsel never suggested that there were any problems with the depositions scheduled for next week, nor did he raise any of the issues that are now contained in SCO's moving papers. On this basis, IBM reasonably assumed those dates were acceptable and confirmed them with the witnesses.

     These third parties arranged to take time off of work and in several instances to retain lawyers. Having heard no objection from SCO, these dates were cleared with the witnesses and counsel, court reporters and conference rooms were reserved, and travel arrangements for all involved were made. Last Thursday, May 27, the Court sent notice that SCO's Motion to Amend the Scheduling Order would be heard next Tuesday, the date previously set for the depositions of David Frasure and BayStar Capital. Although that notice was sent by email Thursday morning, and presumably received at that time by one or more of the several SCO attorneys appearing on the Court's mailing list, SCO did not contact counsel for IBM last week with any scheduling concerns.

     Indeed, SCO's counsel did not contact counsel for IBM until Tuesday of this week. At that time, SCO's principal concern seemed to be that the Court had scheduled the hearing on a date when both the Frasure and BayStar depositions were scheduled. IBM agreed to postpone the BayStar deposition to accommodate SCO's counsel. (1) (See Kao ltr. to Heise, dated June 3, 2004, copy appended to SCO's motion as Exhibit 3). SCO's counsel then requested that all of the depositions scheduled for next week be postponed, in light of the hearing on SCO's Motion to Amend the Scheduling Order. (2)Because these witnesses and their counsel have made arrangements to appear, and because it would impose a burden on them as well as upon IBM, IBM declined to continue these depositions.

Argument

     SCO raises four arguments in support of its motion to continue the depositions scheduled for next week, each of which is without merit:

     First, SCO argues that because its Motion to Amend the Scheduling Order will be heard next week, IBM should postpone the depositions. SCO repeatedly states that IBM, by not agreeing to reschedule the depositions, "presupposes that the Court will not amend the Scheduling Order." (SCO Mem. at 2, 4.) On the contrary, SCO's insistence on rescheduling the depositions presupposes that its motion it will be granted. As of today, there is a Scheduling Order in place. IBM has carefully scheduled its depositions with a view to completing them, along with SCO's depositions, within the time allowed under the existing Scheduling Order. By demanding that these depositions be postponed until some later time, SCO assumes that the Court will grant its motion and give the parties additional time to complete them. Indeed, we would expect that if these depositions are continued, SCO will argue next week that there are now even more depositions that need to be completed within the time remaining. As SCO concedes in its memorandum, IBM noticed these depositions "to comply with the...Scheduling Order." (SCO Mem. at 2.) That Scheduling Order remains in place and, unless and until it is modified, the parties should be expected to operate under it. SCO's request to continue these depositions, on the assumption that its motion will be granted, is inconsistent with the order now in place and should be denied. Moreover, the fact that the Scheduling Order might be amended does not mean that depositions should not proceed, or that deposition discovery in general should be stayed, which appears to be the intent of its present motion.

     Second, SCO contends that the hearing scheduled for next Tuesday, June 8 conflicts with the depositions, and on this basis, apparently all of the depositions scheduled for next week should be postponed. (SCO Mem. at 3.) IBM acknowledges that the date of the hearing creates an unanticipated scheduling issue, and therefore agreed to postpone the BayStar deposition, one of the two depositions that had been scheduled for almost a month. SCO fails to offer any explanation why postponing one of the depositions scheduled on Tuesday is insufficient to address its concerns. More important, SCO fails to explain why none of the 12 lawyers or four law firms that have entered an appearance in this case on behalf of SCO have the ability to cover a single deposition, or oral argument on a Motion to Amend the Scheduling Order. If SCO believes that the presence of a "senior lawyer" at the Frasure deposition is critical, there is no reason why one of the dozen lawyers who have entered an appearance in the case, most or all of whom are partners with their respective firms, cannot argue SCO's motion or attend the deposition.

     Third, SCO raises for the very first time, the argument that it has not had an adequate opportunity to review IBM's documents and therefore prepare for the depositions. (SCO Mem. at 3.) If this truly was a legitimate reason to postpone the depositions, SCO could and should have raised it in mid-May, when the depositions were scheduled, or in late May, when it was exchanging correspondence with IBM on this subject. At a minimum, one would expect SCO to have raised it earlier this week, when it first requested the depositions be continued. SCO's failure to do so is reason enough to deny its motion. Beyond this, IBM produced documents long ago, and there is no reason, particularly given the deadlines imposed by the existing Scheduling Order that it should not have completed this review long ago. Moreover, as SCO well knows, review of IBM's documents is not necessary for any of the depositions next week. Two of the witnesses scheduled next week, Messrs. Frasure and Wilson, are former employees of AT&T, not IBM. SCO as the purported successor of AT&T's rights, should have these documents, to the extent they exist, in its files. Similarly, Mr. Rodgers was employed by Sequent, not IBM, and IBM does not have any of his documents. The final deponent, BayStar, is an investor in SCO, wholly unrelated to IBM, and that deposition apparently will not go forward. The issue regarding SCO's ability to review IBM's documents is simply too late in time, and too weak on the merits.

     Fourth, SCO argues that postponing the depositions will not cause any hardship to IBM or to the witnesses involved. These third party witnesses have scheduled time off from work and made arrangements, including retaining attorneys and clearing these dates with their counsel, to appear at their depositions. They likewise presumably intend to spend time preparing for their depositions. And, in the end, having your deposition taken is no small inconvenience. SCO blithely states that "it would be a simple matter for them simply to attend work that day rather than attend the deposition." (SCO Mem. at 4). SCO ignores both the disruption to their schedules and the inconvenience its demand places on these witnesses, who are not employed by either party and who understandably have better things to do than appear at a deposition. Likewise, IBM's counsel has made reservations and arrangements for these depositions, along with preparing for them, all of which SCO seeks to upend at the last possible moment. SCO, in stark contrast, can suffer no harm or prejudice by proceeding with depositions noticed almost a month ago, at a time when SCO implicitly, if not explicitly, agreed was acceptable. SCO candidly admits that it has the ability to attend both the depositions and the hearing next week - "it is true that both parties could simultaneously provide counsel to cover the June 8th hearing in Utah and what are likely to be trial depositions in North Carolina and California." (SCO Mem. at 3.) SCO's lawyers, not these third party witnesses, should be required to adjust their schedules accordingly.

Conclusion

     For the foregoing reasons, IBM respectfully requests that the Court deny SCO's Expedited Motion for Protective Order.

DATED this 4th day of June, 2004.

SNELL & WILMER L.L.P.

______[signature]______

Alan L. Sullivan
Todd M. Shaughnessy

CRAVATH, SWAINE & MOORE LLP
Evan R. Chesler
David R. Marriott

Attorneys for Defendant/Counterclaim-Plaintiff
International Business Machines Corporation

Of counsel:
INTERNATIONAL BUSINESS MACHINES CORPORATION
Donald J. Rosenberg
Alec S. Berman
[address, phone]

Attorneys for Defendant/Counterclaim-Plaintiff
International Business Machines Corporation


CERTIFICATE OF SERVICE

     I hereby certify that on the 4th day of June, 2004, a true and correct copy of the foregoing was hand delivered to the following:

Brent O. Hatch
Mark F. James
HATCH, JAMES & DODGE, P.C.
[address]

and sent by U.S. Mail, postage prepaid, to the following:

Stephen N. Zack
Mark J. Heise
BOIES, SCHILLER & FLEXNER LLP
[address]

Kevin P. McBride
[address]



NOTES

(1) IBM agreed to postpone the BayStar deposition provided that BayStar was amenable to doing so. IBM tried diligently to reach BayStar to discuss this issue, but BayStar has ignored our calls and letters. SCO, on the other hand, has talked to BayStar. This morning, we finally received a message from BayStar's counsel stating that the deposition would not go forward next week. [back]

(2) SCO did not, at that time, raise any of the other issues outlined in its motion, such as inadequate time to prepare for these depositions. [back]

Exhibits/Attachments to this document have not been scanned. Please see the case file.


  


IBM's Memo in Opposition to SCO's Expedited Motion for Protective Order - as text | 130 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Corrections here Please
Authored by: Anonymous on Sunday, June 06 2004 @ 07:15 AM EDT
so PJ can find them

[ Reply to This | # ]

OT, URLs , etc.
Authored by: Anonymous on Sunday, June 06 2004 @ 07:16 AM EDT
to keep the main thread clear, all OT stuff here please

[ Reply to This | # ]

One wonders
Authored by: PeteS on Sunday, June 06 2004 @ 07:49 AM EDT
Why IBM did not raise the issue that in general, the subject of a deposition, not necessarily the parties to the case, must object to (and request a continuance, for example) a specific time and date for a depositon by subpoena.

In this case, for example, the deponents should be asking for a continuance, not TSCOG - at least, that's how it appears to me.

Indeed, in Utah Court Rules for Subpoenas it puts the onus specifically on the respondent to the subpoena to object.

Likewise, Rule 45 of the Federal Rules of Civil Procedure states quite plainly:

(c) Protection of Persons Subject to Subpoenas.

(1) A party or an attorney responsible for the issuance and service of a subpoena shall take reasonable steps to avoid imposing undue burden or expense on a person subject to that subpoena. The court on behalf of which the subpoena was issued shall enforce this duty and impose upon the party or attorney in breach of this duty an appropriate sanction, which may include, but is not limited to, lost earnings and a reasonable attorney's fee.

In addition, it appears implicit that the benefit of any doubt in this matter is given to the respondent, not the parties and their counsel, as it causes inconvenience (at the least) to appear for a deposition [and retain counsel and schedule them - something IBM did note].

Just a few thoughts.

---
Today's subliminal thought is:

[ Reply to This | # ]

OT: Can IBM sue Baystar?
Authored by: Anonymous on Sunday, June 06 2004 @ 08:38 AM EDT
Given that SCO will be bankrupt if IBM wins, can IBM start proceedings against
SCO's financial backers: Baystar and Canopy?

It seems that IBM will be due substantial damages. Especially if Darl is to be
believed "...20% of Linux installations are having second
thoughts..."

[ Reply to This | # ]

OT: A sign of things to come?
Authored by: Anonymous on Sunday, June 06 2004 @ 09:40 AM EDT

I tried to go to the MSN Money site just now and got this message, it looks like Linux take-up might be having an effect, either that or the patent tactic needs a bit more time to start working.

MSN Money is currently experiencing technical difficulties that we expect to be resolved soon. We apologize for the inconvenience, please try again later.

CPW - A user who forgot his password :o)

[ Reply to This | # ]

IBM's Memo in Opposition to SCO's Expedited Motion for Protective Order - as text
Authored by: Glenn on Sunday, June 06 2004 @ 01:32 PM EDT
Any of us who jump on someone e;se for tpyo's in there posts shood check oot
these
urb:
http://www.dilbert.com/comics/dilbert/archive/dilbert-20040606.html

(I
know, it is off topic.)

Gleenn

[ Reply to This | # ]

Deutsche Securities
Authored by: Anonymous on Sunday, June 06 2004 @ 01:33 PM EDT
Well, I'll admit things aren't looking too good for SCO right now.

But at $5, with Deutsche Securities rating it a STRONG BUY, I'm picking up as
much of this stock as I can.

I don't really care about linux, but I recognize a buy when I see one, and this
one is MAZUMA IN DA BANK.

Don't let your love of Linux get in the way of making some easy cash, people.

[ Reply to This | # ]

IBM's Memo in Opposition to SCO's Expedited Motion for Protective Order - as text
Authored by: blacklight on Sunday, June 06 2004 @ 01:44 PM EDT
SCOG's delaying tactics and the shell games it has been engaging in various
Federal Courts to help produce more delays - these manoevers are becoming more
blatant with every day that passes. I am not yet willing to say that SCOG is
desperate, but it is obvious to me that SCOG is clearly feeling the pressure.
And the pressure is telling because SCOG is bothering less and less with trying
to come up with any solid justification for the delays they are asking for.

I would suggest to Judge Kimball that his acquiescing to SCOG's demands for
delays will only open the door to more SCOG demands for more delays. And the
reason is very simple: any timing where the truth might come out is extremely
poor timing for SCOG. In this case, the best timing for SCOG would be: at no
time.

It is a given that SCOG will appeal any adverse decision no matter how well
rendered. My suggestion to Judge Kimball would therefore be to move the case
agrressively forward, and take his lumps from SCOG because he is getting them no
matter what he does.

[ Reply to This | # ]

Kimball and Wells - How does this work?
Authored by: DMF on Sunday, June 06 2004 @ 01:48 PM EDT
I'm aware that Kimball is Federal, and Wells is Utah State. But how does this
work with filings seemingly going to both courts?

In particular, Wells dealt with the Motion to Compel Discovery foofarah (but
not Kimball?). Now Kimball is dealing with scheduling and substantive filings
(cc to Wells?)

How does this work?

[ Reply to This | # ]

Motion looks hurried
Authored by: overshoot on Sunday, June 06 2004 @ 05:05 PM EDT
What struck me was that this response lacks the scalpel-like precision and heavy citation of dead-on case law of IBM's previous filings. In short, it looks hurried.

I wonder if that was the point of SCOX waiting until the last minute and then filing an expedited motion. I also wonder if the lack of polish in IBM's filing might be somewhat artful, since Judge Kimball would also note the difference and be less than amused by SCOX forcing poor preparation.

[ Reply to This | # ]

Meanwhile in Michigan
Authored by: YMHEE_BCEX on Sunday, June 06 2004 @ 06:56 PM EDT
With SCO's senior council so busy with depositions and hearings - who will handle the DCC hearing scheduled for Wednesday? And, by the way there were supposed to be two memoranda for that hearing (one from SCO and potentially a reply from DCC)... what happened with that? we are so intrigued with SCO/IBM's shots - but there might be a court order coming next week, eh? Or am I missing something?

[ Reply to This | # ]

legal meaning of "continue"
Authored by: mk270 on Sunday, June 06 2004 @ 08:34 PM EDT
For those wondering why IBM is saying it "declines to continue" the
depositions, "continue" has a special and counterintuitive meaning in
the legal context: it effectively means "postpone"

[ Reply to This | # ]

Note for IBM's lawyers
Authored by: Anonymous on Monday, June 07 2004 @ 04:07 AM EDT
> counsel for IBM responded, agreeing to all of the scheduling requests made
by SCO's counsel.

After you pat a rabid dog on the head to try and make friends with it, count
your fingers.

I know that it's *generally* a good idea to be seen to be cooperating with
opposition council, but SCO has shown bad faith so often that perhaps it's time
for IBM to just start saying "Go. To. Hell." and have everything done
in front of, and ordered by, a judge. Cooperating with SCO doesn't seem to be
expediting the case any.

[ Reply to This | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )