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
Declaration of Roger C. Swanson - as text
Saturday, November 06 2004 @ 11:58 PM EST

Here's the Declaration of Roger C. Swanson [PDF], transcribed for us by thpr. It is yet another in the group of declarations IBM submitted in support of its motion for partial summary judgment on breach of contract claims.

Mr. Swanson was a Sequent guy, "the manager of the organization responsible for developing Sequent's Dynix and Dynix/ptx products", involved in negotiating the Sequent licenses, and he agrees with all the other IBM declarants that he didn't understand Section 2.01 to give AT&T the right to assert ownership or control over modifications or derivative works, only over any UNIX System V code used in such modifications or derivative works.

He isn't just testifying to his own inner thoughts and understandings, however. He tells us that he can "recall having discussions with AT&T Technologies at the time to clarify that Sequent would own whatever source code we developed. . . . I never would have agreed to a contract that would grant AT&T Technologies rights in Sequent's proprietary code, as that source code was the core of Sequent's software business." And what did AT&T tell him in these discussions?

"As AT&T Technologies explained the agreements to me, Sequent was free to use, export, disclose or transfer all of the code contained in any modifications or derivative works of UNIX System V developed by Sequent, provided that Sequent did not improperly use, export, disclose or transfer any portion of the UNIX System V code we were licensing from AT&T Technologies (except as otherwise permitted by the licensing agreements)."

Even if SCO's legal team could break down one of these declarants, what in the world can they do to all of them? The only question now is whether the judge views a solitary declarant or two on the other side, one of whom was apparently not involved in the complete IBM-AT&T license negotiations and the other who doesn't seem to fully contradict IBM's declarants regarding the Sequent license, as being meaningful enough to keep the breach of contract claims going a little longer. But if it does go to a jury -- and I ask you to imagine yourself a juror -- after reading all the declarations on both sides, at this point, how would you rule?

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

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

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

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,

-against-

INTERNATIONAL BUSINESS
MACHINES CORPORATION,

Defendant/Counterclaim-Plaintiff.

Civil No. 2:03CV-0294 DAK

Honorable Dale A. Kimball

Magistrate Judge Brooke C. Wells

______________________________________

DECLARATION OF ROGER C. SWANSON

I, Roger C. Swanson, declare as follows:

1. I was employed by Sequent Computer Systems, Inc. ("Sequent") from January 1983 through late 1999. For a short period of time after Sequent was acquired by International Business Machines Corporation ("IBM") in 1999, I was employed by IBM, until April 2000.

2. From January 1983 until late 1988, I served as Sequent's Director of Software Engineering. As Director of Software Engineering, I was involved in negotiating several agreements with AT&T Technologies, Inc. ("AT&T Technologies") for the licensing of certain UNIX software and related materials. I reported to David Rodgers, Sequent's Vice President of Engineering, during this time.

3. In particular, I was responsible for negotiating, on Sequent's behalf, the following agreements between Sequent and AT&T Technologies:

• the Software Agreement (Agreement Number SOFT-00321) dated April 18, 1985 (the "Software Agreement"),

• the Sublicensing Agreement (Agreement Number SUB-00321A) dated January 28, 1986 (the "Sublicensing Agreement"),

• the Substitution Agreement (Agreement Number XFER-000321B) dated January 28, 1986 (the "Substitution Agreement").

True and correct copies of these agreements, referred to herein as the "AT&T Agreements", are attached as Exhibits 1, 2, and 3 to this Declaration.

4. This declaration is submitted in connection with the lawsuit entitled The SCO Group, Inc. v. International Business Machines Corporation, Civil Action No. 2:03CV-0294 DAK (D. Utah 2003). Except as stated otherwise, this declaration is based upon personal knowledge.

5. Based on my role in negotiating the AT&T Agreements with representatives of AT&T Technologies, I believe I have personal knowledge of the parties' understanding of, and intent behind, the terms and conditions of the agreements.

6. It was my understanding from the AT&T Technologies representatives with whom I negotiated (including Ira Kistenberg) that the licensing agreements Sequent entered into were standard form agreements used by AT&T Technologies to license UNIX System V software products to its users.

7. The standard "Software Agreement" that AT&T Technologies used to license UNIX System V source code and related materials -- which are referred to as the "SOFTWARE PRODUCT" or "SOFTWARE PRODUCTS" in the agreement -- granted licensees such as Sequent the right to use such code subject to various restrictions.

8. The Software Agreement that Sequent entered into with AT&T Technologies contains the following provisions, for example:

• Section 2.01 granted licensees a "personal, nontransferable and nonexclusive right to use in the United States each SOFTWARE PRODUCT identified in the one or more Supplements hereto, solely for LICENSEE's own internal business purposes."

• Section 2.05 provided: "No right is granted by this Agreement for the use of SOFTWARE PRODUCTS directly for others, or for any use of SOFTWARE PRODUCTS by others."

• Section 4.01 provided: "LICENSEE agrees that it will not, without prior written consent of AT&T, export, directly or indirectly, SOFTWARE PRODUCTS covered by this Agreement to any country outside of the United States."

• Section 7.06(a) provided: "LICENSEE agrees that it shall hold all parts of the SOFTWARE PRODUCTS subject to this Agreement in confidence for AT&T."

• Section 7.10 provided: "Except as provided in Section 7.06(b), nothing in this Agreement grants to LICENSEE the right to sell, lease, or otherwise transfer or dispose of a SOFTWARE PRODUCT in whole or in part."

As I understood these provisions from my discussions with AT&T Technologies, they set forth the terms that Sequent had to follow with respect to the UNIX System V source code we were licensing from AT&T Technologies. I did not understand the Software Agreement to restrict Sequent's use, export, disclosure or transfer of anything other than such UNIX System V code, and certainly not any code written by Sequent for any of its own software programs.

9. The Software Agreement also granted Sequent the right to modify and to prepare derivative works based upon UNIX System V source code. Section 2.01 of the Software Agreement states that Sequent's "right to use includes the right to modify such SOFTWARE PRODUCT and to prepare derivative works based on such SOFTWARE PRODUCT, provided that the resulting materials are treated hereunder as part of the original SOFTWARE PRODUCT."

10. I did not understand this language in Section 2.01 to give AT&T Technologies the right to assert ownership or control over modifications or derivative works based on UNIX System V prepared by Sequent, except for the licensed UNIX System V code that was included in such modifications or derivative works. In fact, I recall having discussions with AT&T Technologies at the time to clarify that Sequent would own whatever source code we developed.

11. As a small company at the time, it would not have made any sense for Sequent to have entered into an agreement that gave AT&T Technologies control over the source code that we developed for our own software programs. I never would have agreed to a contract that would grant AT&T Technologies rights in Sequent's proprietary code, as that source code was the core of Sequent's software business.

12. As AT&T Technologies explained the agreements to me, Sequent was free to use, export, disclose or transfer all of the code contained in any modifications or derivative works of UNIX System V developed by Sequent, provided that Sequent did not improperly use, export, disclose or transfer any portion of the UNIX System V code we were licensing from AT&T Technologies (except as otherwise permitted by the licensing agreements).

13. I was the manager of the organization responsible for developing Sequent's Dynix and Dynix/ptx products, but I was not one of the software developers who had hands-on involvement with the source code for Dynix or Dynix/ptx. In any case, as I understood the AT&T Agreements, Sequent was free to use the original source code it developed by Dynix and Dynix/ptx in any way it desired, provided that Sequent treated any UNIX System V source code that might be contained therein consistent with the terms of the AT&T Agreements.

14. I declare under penalty of perjury that the foregoing is true and correct.

Executed: July 28, 2004.

Portland, Oregon

____[signature]____
Roger C. Swanson


  


Declaration of Roger C. Swanson - as text | 92 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
A jury? Let's hope not.
Authored by: Anonymous on Sunday, November 07 2004 @ 01:04 AM EST
The idea that any judge would let this case get in front of a jury is offensive
at best. Any five year old can see that there is no case here, no evidence, no
theory of law, nothing, nada, zip.

If this judge does not throw this case out after accomodating SCO for two years
the American legal system is broken beyond repair.

Disgusting that it has two years already.

[ Reply to This | # ]

Declaration of Roger C. Swanson - as text
Authored by: Anonymous on Sunday, November 07 2004 @ 01:13 AM EST
<i>after reading all the declarations on both sides, at this point, how
would you rule? </i><br>
SCO, guilty as charg... oops my bad... They're the plaintiffs :p

[ Reply to This | # ]

Corrections here as usual
Authored by: Anonymous on Sunday, November 07 2004 @ 01:32 AM EST
Loïc

[ Reply to This | # ]

OT -- Off Topic
Authored by: Anonymous on Sunday, November 07 2004 @ 01:34 AM EST
Loïc

[ Reply to This | # ]

Is Novell's waiver(s) null and void or what?
Authored by: one_penguin on Sunday, November 07 2004 @ 01:43 AM EST

What bothers me most, is from my perspective SCO doesn't have standing to bring
various charges against IBM in the first place. Specifically, System V contract
issues and IBM's continued distribution of AIX on account of Novell's
waiver(s).

Is Novell's waiver null and void or what?

[ Reply to This | # ]

Only a heaping plate of steaming hot FUD...
Authored by: John M. Horn on Sunday, November 07 2004 @ 02:26 AM EST
PJ wrote:
"But if it does go to a jury -- and I ask you to imagine yourself a juror
-- after reading all the declarations on both sides, at this point, how would
you rule?"

I were a juror presented with the evidence available to the public as of today,
I would have no alternative but to rule in favor of IBM, hands down. In
aggregate, the evidence is so overwhelmingly in favor of IBM, I can't even
imagine deliberations taking a full day.

I am becoming increasingly skeptical that there could possibly be anything of
merit in the sealed documents submitted to the court by SCO that could
significantly mitigate the evidence that has been publicly presented by IBM.

I am left to wonder what is served by SCO's continued pursuit of this case,
certainly not SCO, nor in any obvious way is Canopy served. Unless, that is,
this entire fiasco was part of a comprehensive 'pump and dump' scam from the
beginning. If so, I can only hope that the SEC will conduct a thorough
investigation when this court case is at an end.

Alternatively, it appears obvious that a certain corporation in Redmond
Washington has been well served by this litigation, if in no other way than by
muddying the Linux adoption waters and by liberally spreading an ample quantity
of FUD.

Thanks to Groklaw though, that heaping plate of steaming hot FUD appears to have
been served directly into the garbage disposal.

Good work PJ!

[ Reply to This | # ]

This mess is passing into pathetic.
Authored by: mobrien_12 on Sunday, November 07 2004 @ 03:50 AM EST
We need all of these declarations and expensive attourney's costs in order to
determine what is obvious to any reasonable person.



[ Reply to This | # ]

Contradictory Declarations
Authored by: Anonymous on Sunday, November 07 2004 @ 05:00 AM EST
What I don't understand is why IBM provides two categories of Declarations.
One category strictly limits the scope of SCO control rights to UNIX SysV code,
while the other category of declarations expands this scope to include
modifications and derivative works containing such UNIX SysV code.

Any help in trying to understand welcome.
TIA.

[ Reply to This | # ]

Declaration of Roger C. Swanson - as text
Authored by: blacklight on Sunday, November 07 2004 @ 05:24 AM EST
We can cross Ed Chatlos and Martin Pfeffer and break both of them:

(1) Why is Ed Chatlos contradicting just about everyone else and contradicting
the plain text of the Novell APA - one would think that there should be a chain
of continuity between the APA he purported to be negotiating and the APA that
his successors ended up with ?

(2) What does Martin Pfeffer really know about the terms of the AT&T
contract, compared to the others who were directly involved?

[ Reply to This | # ]

Declarations and PSJs
Authored by: Khym Chanur on Sunday, November 07 2004 @ 05:50 AM EST
I remember reading SCO saying something along the lines that declarations/affidavits deal with matters of fact, and thus isn't something that the judge can use to decide in favor of a PSJ, since that's a matter of law. Or maybe SCO said that IBM's declarations showed that there was dispute as to the facts of the case? So if IBM is submitting these declarations in support of their PSJ, then SCO must be (yet again) full of it.

---
Give a man a match, and he'll be warm for a minute, but set him on fire, and he'll be warm for the rest of his life. (Paraphrased from Terry Pratchett)

[ Reply to This | # ]

Derived Work
Authored by: Anonymous on Tuesday, November 09 2004 @ 01:54 AM EST
What is seen as 'derived' software? At what point did the software that IBM and
sequent developed become derived and AT&T loose control over it according to
the agreement / license?

<b>For example:</b> If I take the System V code and change one line
of it does this make it a derived piece of code or not. If not then the it still
falls under the agreement and must be treated as such.

Ok on the other side. If I take the System V code and develop a file system that
can interact with it. Now this does not necesarily contain System V code. SO it
would propably be classified as derived.

And if I start with a clean slate but use the ideas and concepts from System V
to create my own operating system...

hmmmm..... wonder if either side will touch on this.

[ 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 )