Oracle America, Inc. v. Google Inc.

Filing 65

ORDER RE PROPOSED PROTECTIVE ORDERS re #64 Notice (Other), Notice (Other) filed by Google Inc., Oracle America, Inc.. Signed by Judge Alsup on December 14, 2010. (whalc1, COURT STAFF) (Filed on 12/14/2010)

Download PDF
Oracle America, Inc. v. Google Inc. Doc. 65 1 2 3 4 5 6 7 8 9 10 ORACLE AMERICA, INC., Plaintiff, v. GOOGLE INC., Defendant. / ORDER RE PROPOSED PROTECTIVE ORDERS No. C 10-03561 WHA IN THE UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF CALIFORNIA United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Pursuant to the Case Management Scheduling Order, the parties were to submit a jointly agreed protective order by December 10, 2010. On that date, the parties filed a submission indicating that they had reached an impasse regarding two provisions of the protective order: (1) whether any in-house counsel would have access to information of the highest designation; and (2) whether a prosecution bar would attach to persons accessing designated information. The parties requested the Court's assistance in resolving these issues. With respect to the first dispute, the Court is of the view that neither party has any need to have in-house counsel review any source code belonging to the other party, much less have five in-house counsel do so. Instead, the experts can review source code from both parties and make any necessary comparisons. If and when any settlement discussions require final sign-off or input from in-house-counsel based on the other party's source code, the court would consider making an ad hoc exception at that time. With respect to the second dispute, there should be a prosecution Dockets.Justia.com 1 2 3 4 5 6 7 8 9 10 bar, but the one proposed by Google Inc. seems overbroad in that it applies to all patents or patent applications "relating to Java, Android, mobile platforms and devices, or virtual machines." The Court understands the need to keep source code confidential, but both sides should be aware that overclassification of documents produced in discovery may lead to declassification of large swathes of improperly classified material. The views set forth in this order have been made based upon the Court's experience in similar cases. If either party cannot live with these rulings, however, a formal motion may be made on the compressed schedule set forth below, and the Court will give the motion fresh consideration with a full record. In the meantime, no discovery should be withheld on the ground of the parties' inability to agree to a protective order, and all source code shall be maintained in strict confidentiality as "Attorneys' Eyes Only" material, meaning only outside counsel of record may access and view it. If the parties will acquiesce in the Court's rulings, they shall submit a revised jointly agreed protective order by NOON ON DECEMBER 17, 2010. If the parties still cannot resolve these issues, a party desiring to add a provision to the jointly agreed protective order may file a motion to do so and notice a hearing on the motion for 8:00 A.M. ON JANUARY 6, 2011. Any such motion must be filed by NOON ON DECEMBER 20, 2010. Any opposition to such motion must be filed by NOON ON DECEMBER 27, 2010. Any reply in support of such motion must be filed by NOON ON DECEMBER 30, 2010. United States District Court 11 For the Northern District of California 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 IT IS SO ORDERED. Dated: December 14, 2010. WILLIAM ALSUP UNITED STATES DISTRICT JUDGE 2

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?