Synopsys, Inc. v. Atoptech, Inc
Filing
846
ORDER by Magistrate Judge Donna M. Ryu re: Synopsys' motion to compel production of paper copies of portions of ATopTech's source code 816 , 845 . (dmrlc3, COURT STAFF) (Filed on 9/16/2016)
1
2
3
4
UNITED STATES DISTRICT COURT
5
NORTHERN DISTRICT OF CALIFORNIA
6
7
SYNOPSYS, INC.,
Case No. 13-cv-02965-MMC (DMR)
Plaintiff,
8
v.
9
10
ATOPTECH, INC,
Defendant.
ORDER DENYING SYNOPSYS'
MOTION TO COMPEL PRODUCTION
OF PAPER COPIES OF PORTIONS OF
ATOPTECH'S SOURCE CODE
Re: Dkt. No. 816, 845
United States District Court
Northern District of California
11
12
Synopsys previously moved to compel ATopTech to provide paper copies of portions of its
13
source code. Motion to Compel Production of Paper Copies of ATopTech’s Source Code (“June
14
21, 2016 MTC”) [Docket No. 769]. Synopsys originally requested 36,000 lines of source code,
15
totaling 786 pages of printed source code. June 21, 2016 MTC at 3. ATopTech opposed the
16
motion, arguing that the request was excessive and did not comply with the Protective Order. Id.
17
The Parties’ Stipulated Protective Order provides that a “Receiving Party is permitted to
18
request paper copies of limited portions of Source Code that are reasonably necessary for the
19
preparation of court filings, pleadings, expert reports, or other papers, or for deposition or trial.”
20
Stipulated Protective Order [Docket No. 209] at ¶ 9(d). Challenges to the amount of source code
21
requested by a “Receiving Party” are governed by the dispute resolution process set out in
22
Paragraph 6 of the Protective Order. Id. As the Receiving Party, Synopsys bears the burden of
23
persuasion regarding the propriety of the amount of source code requested. Id. (The Receiving
24
Party is the “Designating Party” for purposes of dispute resolution); Id. at ¶ 6.3 (Where judicial
25
intervention is sought, the burden of persuasion shall be on the Designating Party).
26
The court held a telephonic hearing on Synopsys’s original motion on July 20, 2016, and
27
denied that motion without prejudice. July 20, 2016 Minute Order [Docket No. 800]. At the
28
hearing, the court provided specific guidance to the parties and instructed Synopsys that it must
1
provide a more narrowly tailored request, and make an effort to demonstrate that the requested
2
portions of the source code are “reasonably necessary” for one of the purposes allowed under the
3
Protective Order.
Synopsys filed a subsequent motion to compel production of paper copies of portions of
4
5
ATopTech’s source code [Docket No. 816] (“MTC”). The court has reviewed this motion and
6
finds it suitable for determination without further oral argument. Civil L.R. 7-1(b).
7
As an initial matter, the parties dispute the amount of source code that Synopsys is
8
requesting in paper form. Synopsys contends that it moves to compel ATopTech to produce paper
9
copies of approximately 11,762 lines of source code, totaling 256 pages of printed source code,
whereas ATopTech states that Synopsys is still seeking 36,058 lines of code, or the equivalent of
11
United States District Court
Northern District of California
10
786 printed pages. Compare MTC at 1, 3.
In light of this glaring factual discrepancy, the court requested clarification. [Docket No.
12
13
844.] However, the parties are still unable to agree on the amount of source code Synopsys
14
requests in paper form, and whether it has been narrowed from Synopsys’ original June 2016
15
request. September 13, 2016 Letter [Docket No. 845]. Synopsys cryptically states that “[r]ecent
16
developments narrowed Synopsys’ request for paper copies of source code,” and explains that
17
ATopTech has already produced 182 pages (approximately 8,700 lines) of source code from
18
version 15.02.rel.2, and that the parties have agreed to dismiss claims of infringement for the ’348
19
patent. Id. at 1. ATopTech contends that Synopsys has essentially confirmed that its July 25 letter
20
brief sought the same 36,000 lines that it initially requested, despite the Court’s order to confer
21
further. Id.
ATopTech argues that Synopsys’s current request is still excessive and does not comply
22
23
with the Protective Order. ATopTech represents that it has offered to provide limited portions of
24
the source code to Synopsys immediately for permitted purposes, and Synopsys does not dispute
25
that ATopTech has already provided 182 pages of printed source code, as well as 8,686 printed
26
pages of test script files.1 Id.
27
1
28
Synopsys does not dispute that ATopTech has provided the 8,686 printed pages of test script
files, however it disputes whether or not these test script files constitute “source code.” Sept. 13
2
1
Despite the court’s clear instruction to Synopsys at the July 20, 2016 hearing that it must
2
more narrowly tailor its request for source code and show how the requested portions are
3
“reasonably necessary” for one of the allowable purposes under the Protective Order, Synopsys
4
yet again has provided insufficient information for the court to be able to determine whether its
5
request is reasonably necessary for its stated purposes. Synopsys makes almost no effort to tether
6
its broad request for source code to specific purposes allowed under the Protective Order, nor does
7
Synopsys provide any explanation of why the amount of requested portions is “reasonably
8
necessary.”
9
Synopsys has failed to meet its burden of persuasion to show that all of the requested
portions of the source code are reasonably necessary for a purpose allowed under the Protective
11
United States District Court
Northern District of California
10
Order. Therefore, Synopsys’s motion to compel [Docket No. 816] is denied. This does not mean
12
that Synopsys is foreclosed from seeking any further paper copies of source code. Today the court
13
rules that Synopsys has not met its burden under the Protective Order to support its current
14
request.
15
16
IT IS SO ORDERED.
Dated: September 16, 2016
______________________________________
Donna M. Ryu
United States Magistrate Judge
17
18
19
20
21
22
23
24
25
26
27
28
Letter at 1.
3
Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.
Why Is My Information Online?