Waymo LLC v. Uber Technologies, Inc. et al
Filing
2006
ORDER DENYING WAYMO'S MOTION FOR UBER'S CURRENT SOURCE CODE. #1977 . Signed by Judge Jacqueline Scott Corley on October 16, 2017. (jsclc2, COURT STAFF) (Filed on 10/16/2017)
1
2
3
4
UNITED STATES DISTRICT COURT
5
NORTHERN DISTRICT OF CALIFORNIA
6
7
WAYMO LLC,
Plaintiff,
8
9
10
v.
UBER TECHNOLOGIES, INC., et al.,
Defendants.
11
United States District Court
Northern District of California
Case No.17-cv-00939-WHA (JSC)
ORDER DENYING WAYMO'S
MOTION FOR UBER'S CURRENT
SOURCE CODE
Re: Dkt. No. 1977
12
13
Discovery closed on August 24, 2017. Any new discovery sought by Waymo must be
14
approved by this Court, unless stipulated to by the parties. (Dkt. No. 1954.) Waymo seeks
15
production of Uber’s current source code, without limitation. (Dkt. No. 1977.) The Court denies
16
the request.
17
First, the request is profoundly overbroad. Waymo’s showing focuses on a need for
18
Uber’s source code with respect to motion planning and lane change decisions. Even though
19
Waymo had previously been given access to Ottomotto’s source code, Waymo contends that the
20
source code for motion planning and lane change decisions was not included. Yet Waymo’s
21
motion seeks all of Uber’s current source code without limitation. (Dkt. No. 1977 at 2 (“The
22
Court should order Uber to immediately make available its current source code repository”), 4
23
(“Waymo thus requests the current source code to compare Uber’s implementation to Waymo’s
24
source code”), 8 (“the Court should order Uber to produce the current . . . version of its source
25
code”). It is too late in the litigation for a party to make a broad, unsupported discovery request on
26
the assumption that if its broad request is not granted the Court will narrow it to an appropriate
27
scope. For this reason alone Waymo’s motion is denied.
28
Second, even if the Court were to limit Waymo’s request to Uber’s current source code for
1
motion planning and lane change decisions, Waymo has not shown sufficient cause for this new
2
discovery. A week after Waymo received the Stroz Report, it argued to the district court that the
3
material Anthony Levandowski downloaded included more than the LiDAR hardware on which
4
Waymo’s trade secret case had focused and that the Stroz Report shows that Mr. Levandowski
5
took hundreds of software files. (Dkt. No. 1723 at 77:7-13.) Waymo thus argued to the district
6
court that if it could tie what software Mr. Levandowski took to what Defendants produced in this
7
litigation “so that there’s absolutely no question that he took some software and copied it and put
8
it in” Waymo might attempt to amend its trade secret list to include such a claim. (Id. at 77:14-
9
18.)
10
Waymo’s current request, however, is untethered to the “hundreds of software files” that
United States District Court
Northern District of California
11
the Stroz Report supposedly showed Mr. Levandowski took. Instead, Waymo now contends that
12
Ex. 37 to the Stroz Report identifies what Stroz referred to as a “snippet” of source code related to
13
route planning and lane changing that was found on Mr. Levandowski’s laptop and cloud account.
14
(Dkt. No. 1977 at 3, Ex. 1.) Waymo wants Uber’s current source code to compare it to this
15
snippet and determine if this snippet made its way into Uber’s source code (actually Waymo wants
16
all of Uber’s source code, but this snippet is its justification). But as Uber’s opposition highlights,
17
this snippet is taken from a presentation that Waymo made to two different third parties. (Dkt.
18
No. 1991-1, Exs. 1-3.) The evidence suggests the snippets were used to illustrate to these third-
19
parties Google’s code revision process. (Id., Ex. 3.) In light of this evidence, and the lack of any
20
evidence from Waymo as to the significance of these “snippets,” Waymo has not persuaded the
21
Court that opening discovery into Uber’s current source code (and thus potentially into Waymo’s
22
as well) is warranted at this late stage.
23
Waymo’s reference to Otto Diligenced Employee Don Burnette does not tip the scale in
24
favor of Waymo’s request. Waymo has not identified any Waymo source code that Mr. Burnette
25
took from Waymo, other than a copy of his performance review in his gmail account that
26
discussed his source code work. This evidence does not support opening up source code
27
discovery, especially since Waymo again offers no persuasive evidence of its significance. It is
28
thus unsurprising that Waymo’s reply focuses on different Burnette evidence. It argues that his
2
1
continued deposition testimony and additional uncovered evidence supports Waymo’s belief that
2
Uber—through Burnette—used Waymo’s source code to quickly develop its own motion planning
3
and lane changing code, code that it lacked before its Ottomotto acquisition. However, there is no
4
evidence that the files Waymo questioned Mr. Burnette about contain Waymo’s trade secrets. That
5
Mr. Burnette testified that he did not know whether they were Waymo’s source code is not
6
evidence that they are. Waymo would know that information, but Waymo does not offer any such
7
evidence. Similarly, as to the notes Mr. Burnette made the day after his Waymo departure,
8
Waymo has not shown that the notes contain Waymo’s trade secrets. There is thus no need to
9
compare them with Uber’s current source code.
CONCLUSION
11
United States District Court
Northern District of California
10
Waymo seeks discovery related to an undefined source code trade secret that was not
12
included on its original list of more than 120 trade secrets. (Dkt. No. 25-7.) Waymo’s evidence
13
and argument do not persuade this Court that production of Uber’s current source code is
14
warranted. Waymo’s motion is therefore DENIED. Any objections to this Order shall be filed
15
with the district court on or before noon on Tuesday, October 17, 2017.
16
This Order disposes of Docket No. 1977.
17
IT IS SO ORDERED.
18
Dated: October 16, 2017
19
20
JACQUELINE SCOTT CORLEY
United States Magistrate Judge
21
22
23
24
25
26
27
28
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?