Use of Open Source Software. 9.1 In the event that Open Source Software is provided in or in connection with any Software, Supplier shall:
(a) set out in the relevant Supply Order full details of the Open Source Software used including the name, the range, application and description of the Open Source Software that is used;
(b) notify the UBS Contract Manager with the details specified in clause 9.1(a) above in the event that Supplier wishes to use any Open Source Software in any Update, Upgrade or Support Modification or as part of any other Services; and
(c) ensure that any such use of Open Source Software does not result in any non-trivial adverse impact to, or create any obligations in respect of: (i) UBS’s IP Rights, UBS Systems or UBS Materials; and (ii) on any warranty or license or right granted under this Agreement.
9.2 Breach of clause 9.1(c) will constitute an irremediable material breach for the purposes of clause 10.3(e) (Termination) of the General Terms and Conditions.
Use of Open Source Software. 8.1 In the event Open Source Software is included in or used in connection with the Cloud Services, Supplier shall on request provide full details, including the name, application and description of the Open Source Software, and any applicable terms of use.
Use of Open Source Software. Except with respect to open source software provided or made available to Contractor by County (or except further to the extent Contractor was otherwise directed by County to use open source software), Contractor represents and warrants that: (a) the performance of any Services, the delivery of any deliverables pursuant to this Contract, or the use of the VSAP Solution will not cause County to be in violation of any open source licenses or otherwise require the publication of any software pursuant to the terms of such open source licenses; and (b) provided that County uses the VSAP Solution in accordance with the applicable licenses and/or notices given to County by Contractor, including, without limitation, providing appropriate licenses and/or notices with any distribution of the VSAP Solution, in the form and to the extent such licenses and/or notices were provided by Contractor to County, County's use of the VSAP Solution under this Contract does not, or will not with the passage of time, violate any open source licenses or otherwise require the publication of any software pursuant to the terms of such open source licenses. As County's exclusive remedy for a breach of this Sub- paragraph 2.1.5.1, Contractor will either obtain a license for County's use (as permitted under this Contract) of the affected open source software without publication, or provide a functionally equivalent replacement that would not cause a breach of this Sub-paragraph 2.1.5.1 or publication of such software. For the avoidance of doubt, the immediately preceding sentence does not limit any obligations of Contractor in respect of third-party claims and losses under Sub- paragraph 8.23 (Indemnification).
Use of Open Source Software. (i) Schedule 4.12(m)(i) accurately identifies and describes each item of Open Source Software that is or has been included, incorporated or embedded in, linked to, combined, distributed or made available with, or used in the development, delivery or provision of any Company Product and the manner in which such Open Source Software is or has been included, incorporated or embedded in, linked to, combined, distributed or made available with, or used in the development, delivery or provision of such Company Product (such description shall include whether (and if so, how) the Open Source Software was modified and/or distributed by the Company.
(ii) No Open Source Software is or has been included, incorporated or embedded in, linked to, combined, distributed or made available with or used in the development, delivery, or provision of any Company Product, in each case, in a manner that: (A) subjects any Company IP, or part thereof, to any Copyleft License (other than Copyleft Licenses governing the Open Source Software listed in Schedule 4.12(m)(i); (B) creates obligations for the Company with respect to Company IP or grants to any Person any rights or immunities under Company IP (other than the licenses governing Open Source Software listed in Schedule 4.12(m)(i)); or (C) otherwise imposes any limitation, restriction or condition on the right or ability of the Company to use or distribute any Company Product or Company IP (other than the limitations, restrictions, or conditions contained in the licenses governing the Open Source Software listed in Schedule 4.12(m)(i)).
(iii) The Company has materially complied with all of the terms and conditions of each applicable license for Open Source Software, including all requirements pertaining to attribution and copyright notices.
(iv) Schedule 4.12(m)(iv) sets forth an accurate and complete list of each third party project relating to Open Source Software to which Company has made contributions, commitments or submissions and, for each project: (A) the license under which such contribution, commitment or submission was made; and (B) whether a corporate contribution license agreement was executed on behalf of Company in connection with such project.
Use of Open Source Software. (i) Section 3.10(j)(i) of the Disclosure Schedule accurately identifies and describes each item of Open Source Software that is or has been included, incorporated or embedded in, linked to, combined, distributed or made available with any of the Company Intellectual Property or in any Company Product. The Company has complied with all of the terms and conditions of each applicable license for Open Source Software, including all requirements pertaining to attribution and copyright notices.
(ii) Except as set forth in Section 3.10(j)(ii) of the Disclosure Schedule, no Open Source Software is or has been included, incorporated or embedded in, linked to, combined, distributed or made available with, any of the Company Intellectual Property or in any Company Product, in each case, in a manner that (A) subjects any of the Company Intellectual Property to any Copyleft License, (B) creates obligations for the Company with respect to the Company Intellectual Property or grants to any Person any rights or immunities under the Company Intellectual Property or (C) otherwise imposes any limitation, restriction or condition on the right or ability of the Company to use or distribute any of the Company Intellectual Property.
Use of Open Source Software. (i) Seller and each Related Contracting Party (in the case of each Related Contracting Party, solely with respect to the University-Owned Software and University Products) are in compliance with the terms and conditions of each license applicable to each Open Source Software component: (i) that is embedded in, linked with, or otherwise interfaced with University-Owned Software and University Products; (ii) that Seller runs, uses, or otherwise relies upon as part of its University IT Systems; or (iii) that Seller otherwise uses in connection with the operations of the University as currently conducted.
(ii) No University-Owned Software or University Product contains, is distributed or made available with, is being or has been modified or developed using, or is derived from Open Source Software in a manner that imposes or would impose a requirement or condition that Seller or any Related Contracting Party grant a license under or refrain from enforcing any of its Intellectual Property, or that the source code of any of the University-Owned Software or University Product or part thereof (A) be disclosed or distributed in source code form, (B) be licensed for making modifications or derivative works or (C) be redistributable at no or nominal charge.
Use of Open Source Software. 10.5.1 The User is aware and agrees that when using the Service and Access Software, Open Source Software (“OSS”) may be used, which is provided in association with ADS-TEC’s Service. Any OSS provided within the association may be subject to separate terms and conditions, which must be applied in whole or in part to the OSS (“Open Source License Terms”). In this case, OSS will be subject to the respective separate Open Source License Terms in addition to these Terms of Use.
Use of Open Source Software. 4.1 It is acknowledged that Agency may use Open Source Software as part of the Deliverables provided that: (i) Agency shall have supplied to Client details of which Deliverable(s) and/or part(s) thereof it is proposed shall include such Open Source Software and in what manner, together with full details of which licence(s) apply to such Open Source Software; and (ii) Client has approved same, such approval not to be unreasonably withheld or delayed.
Use of Open Source Software. Aeris may use Open Source software under the MIT licence in the Services and Deliverables. For any Open Source requiring a different license, Aeris will obtain the Customer’s prior written consent.
Use of Open Source Software. Executive Director assures that without the approval of the Company, either in writing or by email, he does not incorporate any software into the products or services of the Company in such a way as would necessitate the publication or licensing of the source codes of the software of the Company under any applicable GNU General Public License, a Lesser General Public License or a similar license. § 7 CONFLICTS OF INTEREST. Executive Director confirms that his work at the Company is not in conflict with any agreement with a former employer or with any agreement with a third party. § 8
