Release of Source Code Sample Clauses
The Release of Source Code clause defines the circumstances under which a party must provide access to the underlying source code of a software product. Typically, this clause specifies triggers such as breach of contract, bankruptcy, or failure to provide ongoing support, at which point the source code is released to the other party or placed in escrow. Its core practical function is to protect the licensee or customer by ensuring they can maintain or modify the software if the original provider is unable or unwilling to do so, thereby mitigating operational risks.
POPULAR SAMPLE Copied 15 times
Release of Source Code. The source code will be released to the District in accordance with the Escrow Agreement upon the occurrence of one or more of the following conditions:
(i) Contractor's failure to carry out obligations imposed on it by the Contract or any agreement between the District and Contractor relating to the use of the Products;
(ii) Contractor's announcement or acknowledgement that it will no longer support the version of the Products then being used by the District;
(iii) Contractor's failure to continue to do business in the ordinary course; and
(iv) Contractor is subject to voluntary or involuntary bankruptcy.
Release of Source Code. In the event that any Source Code deposited pursuant to Clause 9.6 is released in accordance with the applicable escrow terms, the Contractor shall ensure that the licence referred to in Clause 8.7 (Third Party IP) shall include all IP subsisting in such Source Code.
Release of Source Code. Except as listed in Section 3.13(j)(ii) of the Company Disclosure Schedule, the Company has not put source code for any of the Company Products into escrow for the benefit of any beneficiary or licensee of the Company. To the extent that any source code escrow arrangements are listed in Section 3.13(j)(ii) of the Company Disclosure Schedule, such list identifies the agreement and beneficiary of such escrow agreement and the Company has made such agreements available for Buyer’s inspection and review. No source code for any of the Company Products or for the Company Intellectual Property has been disclosed by the Company to any Third Party except as disclosed in Section 3.13(j)(ii) of the Company Disclosure Schedule.
Release of Source Code. 20.5.1 If, after Buyer requests possession of the Source Code or Object Code following the occurrence of any event requiring release of the Source Code, Company disputes whether such event has occurred, Buyer may immediately initiate any legal action it deems necessary in response to such dispute without regard to the Dispute Resolution provisions of Article 24.
20.5.2 If an event occurs requiring release of the Source Code or Object Code and Buyer does not receive the Source Code or Object Code from the Escrow Agent such that the Escrow Agent or Company is in breach of the Escrow Agreement, upon Buyer’s request to Company, Company shall promptly provide the Source Code and related documentation to Buyer.
Release of Source Code. Upon occurrence of the conditions described in the Escrow Agreement (each, a “Release Condition”), the source code placed in escrow will be delivered to T-Mobile for use, copying and modification of the Provider Software in accordance with its rights hereunder. The Release Conditions in each Escrow Agreement will include any Provider Material Adverse Change, as well as, in the case of Provider Third Party Software, any liquidations of the applicable Third Party Software Providers. Provider shall obtain any Required Consents from Third Party Software Providers necessary to fulfill its obligations in this Section 14.12 (Escrow of Source Code).
Release of Source Code. 18.1 Infinity agrees to deliver the Source Code for its e-Warehouse software to Infonet if Infinity (i) avails itself of, or is subjected to by any third party, a proceeding in bankruptcy in which Infinity is the named debtor; an assignment by Infinity for the benefit of its creditors; the appointment of a receiver for Infinity; or any other proceeding involving insolvency or the protection of or from creditors, and the same has not been discharged or terminated without any prejudice to Infonet's rights or interests under this Agreement within thirty (30) days; or (ii) is dissolved or ceases its ongoing business operations. Upon receipt of such Source Code pursuant to this Section, Infonet shall have a non-exclusive license to use such Source Code for the limited purpose of performing any of Infinity's obligations under this Agreement.
Release of Source Code. The Escrow Agent shall release copies of the Source Code deposited in escrow pursuant to this Agreement only in accordance with the terms of this Agreement.
Release of Source Code. The source code will be released to the District in accordance with the Escrow Agreement upon the occurrence of one or more of the following conditions: Contractor's failure to carry out obligations imposed on it by the Contract or any agreement between the District and Contractor relating to the use of the Products; Contractor's announcement or acknowledgement that it will no longer support the version of the Products then being used by the District; Contractor's failure to continue to do business in the ordinary course; and Contractor is subject to voluntary or involuntary bankruptcy. Definition of deposit materials. Materials to be deposited with each deposit are: Source code, including any customizations for District; All related technical documentation; A list of names and contact information for personnel who have been supporting the source code; A list of third party code, including open source, needed to run the software and available from other sources; and Compilers.
Release of Source Code. The source code will be released to the District in accordance with the Escrow Agreement upon the occurrence of one or more of the following conditions:
Release of Source Code. Each Party agrees, with respect to Applicable Stablecoins for which it is the Issuer Party, to, prior to use in production following the Effective Date, publicly release the Covered Source Code under the Apache 2.0 license, the MIT license, or another open source Permissive License reasonably chosen by the Issuer Party; provided that if a portion of the Covered Source Code is licensed to the Issuer Party under a license that is not a Permissive License, the Issuer Party may, to the extent permitted under such license, publicly release the Covered Source Code under the same license under which it receives such portion. A “Permissive License” is an open source license that does not require that the licensed software or other software incorporated into, derived from, linked to or distributed with such licensed code (i) be disclosed or distributed in source code form, (ii) be licensed for the purpose of making derivative works or (iii) be redistributable at no charge. Circle represents and warrants that it has released the Covered Source Code in existence as of the Effective Date for USDC on the GitHub repositories listed on Schedule A.
