throbber
Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 1 of 6 PageID #: 14669
`
`
`
`IN THE UNITED STATES DISTRICT COURT FOR
`THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`CASE NO. 2:17-cv-514-JRG
`(Lead Case)
`
`JURY TRIAL DEMANDED
`
`CASE NO. 2:17-CV-515-JRG
`(Member Case)
`
`JURY TRIAL DEMANDED
`
`§§§§§§§§§
`
`§§§§§§§§§
`
`AGIS SOFTWARE DEVELOPMENT, LLC
`
`Plaintiff,
`
`v.
`
`HTC CORPORATION, et al.
`
`Defendant.
`AGIS SOFTWARE DEVELOPMENT, LLC
`
` Plaintiff,
`
`v.
`
`LG ELECTRONICS INC.
`
` Defendant.
`
`DECLARATION OF SEAN CALLAGY IN SUPPORT OF DEFENDANT LG
`ELECTRONICS INC.’S OPPOSITION TO AGIS’S MOTION TO STRIKE THE
`JANUARY 11, 2019 EXPERT REPORT OF EDWARD R. TITTEL
`
`I, Sean Callagy, state and declare as follows:
`
`1.
`
`I am a partner in the law firm Arnold & Porter Kaye Scholer, LLP (“Arnold &
`
`Porter”), and counsel of record for Google LLC (“Google”) in the above-captioned matter. I am
`
`a member of the Bar of the States of Texas and California, and have been admitted to practice in
`
`the United States District Court for the Eastern District of Texas (“EDTX”). I provide this
`
`declaration in support of Defendant LG Electronics Inc.’s Opposition to AGIS’s Motion to Strike
`
`the January 11, 2019 Expert Report of Edward R. Tittel. I have personal knowledge of the
`
`matters stated in this declaration and would testify competently and truthfully to them if called
`
`upon to do so.
`
`1
`
`

`

`Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 2 of 6 PageID #: 14670
`
`
`
`2.
`
`AGIS Software Development LLC (“AGIS”) issued a subpoena for documents
`
`and deposition testimony to Google on August 29, 2018. Google timely served objections and
`
`responses to the subpoena. In the objections and responses, Google offered to meet and confer
`
`concerning the documents and topics of deposition testimony sought by the subpoena. Counsel
`
`for AGIS contacted me and, as detailed below, we engaged in meet-and-confer discussions.
`
`Following several such discussions with counsel for AGIS, Google made available for AGIS’s
`
`inspection source code for the applications accused of infringement.
`
`3.
`
`On November 12, 2018, Arnold & Porter’s IT Support Analyst, Stefan Froese,
`
`working at my instruction, arranged for the loading of Google source code on a review machine
`
`hosted in Arnold & Porter’s Silicon Valley office for this case in response to the AGIS subpoena.
`
`We thereupon informed AGIS that the source code was available for review. At various times
`
`from November 2018 to December 2018, AGIS sent reviewers to inspect the source code files.
`
`4.
`
`5.
`
`6.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2
`
`

`

`Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 3 of 6 PageID #: 14671
`
`7.
`
`8.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`9.
`
`On or around January 11, 2019, at my instruction, Mr. Froese downloaded the
`
`source code for
`
` and installed it on the source code review machine in Arnold &
`
`Porter’s Silicon Valley office. Google made this code available following discussions with
`
`AGIS concerning the responsiveness of certain portions of Google’s source code production.
`
`This additional source code was made available for AGIS’s inspection on January 13, 2019.
`
`10.
`
`
`
`
`
`
`
`
`
`
`
`
`
`3
`
`

`

`Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 4 of 6 PageID #: 14672
`
`
`
`11.
`
`AGIS sent a reviewer to Arnold & Porter’s Silicon Valley office to review the
`
`supplemental source code production for
`
` on January 18, 2019, and requested
`
`additional source code printouts from Google at such time.
`
`12.
`
`Attached hereto as Exhibit C is a true and correct copy of correspondence
`
`between myself as counsel for Google and counsel for LGEKR, memorializing that Google had
`
`provided printouts of source code files requested by AGIS, HTC, and LGEKR, and has marked
`
`such documents with the bates stamp range GOOGLE_SC_00000494 -
`
`GOOGLE_SC_00000563.
`
`13.
`
`Attached hereto as Exhibit D is a true and correct copy of the document and
`
`deposition subpoena referenced above, which indicates that it was issued by AGIS to Google on
`
`or about August 29, 2018.
`
`14.
`
`Attached hereto as Exhibit E is a true and correct copy of Google’s Objections
`
`and Responses to AGIS’s deposition and document subpoenas, served in the related litigation
`
`AGIS Software Development, LLC v. Huawei Device USA Inc., et al., Case No. 2:17-cv-513, on
`
`September 7, 2018.
`
`15.
`
`Attached hereto as Exhibit F is a true and correct copy of Google’s Objections
`
`and Responses to AGIS’s deposition and document subpoenas, served in the instant case on
`
`September 13, 2018. These objections and responses to AGIS’s deposition and document
`
`requests are substantively identical to the Objections and Responses to AGIS’s deposition and
`
`document subpoenas served in the related case against Huawei defendants.
`
`16.
`
`I first telephonically met and conferred with counsel for AGIS regarding the
`
`objections and responses to AGIS’s subpoenas on September 13, 2018. I had numerous
`
`subsequent discussions with counsel for AGIS on this matter as well.
`
`4
`
`

`

`Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 5 of 6 PageID #: 14673
`
`
`
`17.
`
`The meet-and-confer process continued for several months. This entailed several
`
`email exchanges, as well as several subsequent telephonic discussions. Throughout this process,
`
`counsel for AGIS only raised AGIS’s requests for documents, with virtually all of the discussion
`
`focusing on the source code that Google produced. During these discussions, counsel for AGIS
`
`never asked to discuss AGIS’s deposition subpoena topics or Google’s responses thereto
`
`(including Google’s offer to meet and confer about such topics). Counsel for AGIS likewise
`
`never asked for a date for a deposition of any Google witness, nor that I identify witnesses who
`
`might testify on behalf of Google should a deposition proceed.
`
`18.
`
`On December 7, 2018, which I understood to be the final day for parties to seek to
`
`compel discovery responses, I discussed the status of Google’s production of source code with
`
`counsel for AGIS. During the call, it was agreed among myself and counsel for AGIS that
`
`
`
`
`
`
`
`
`
` Notably, no part of my discussion with counsel for AGIS entailed a
`
`request or demand from AGIS to obtain deposition testimony, or follow-up from the offer to
`
`meet and confer by Google or any reservation of rights by AGIS to seek deposition testimony
`
`after the Court’s deadline to move to compel further responses to fact discovery requests.
`
`19.
`
`As indicated by the foregoing, given AGIS’s apparent decision not to pursue its
`
`request for deposition testimony at any point in the meet-and-confer process, AGIS never
`
`deposed a Google witness with respect to the instant litigation.
`
`5
`
`

`

`Case 2:17-cv-00514-JRG Document 166-1 Filed 02/13/19 Page 6 of 6 PageID #: 14674
`
`
`
`I declare under penalty of perjury that the foregoing is true and correct. Executed in San
`
`Francisco, California on February 11, 2019.
`
`/s/ Sean Callagy
`Sean Callagy
`Attorney for Google LLC
`
`6
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket