Intermediate Builds Sample Clauses

Intermediate Builds. If Licensee generally uses a bona fide open source software development methodology and does so to develop the Product, then, notwithstanding the limited license grant set forth in Section 2.1(a) or the additional limitation set forth in Section 2.1b(v), Licensee may make "Intermediate Builds" available subject to the following conditions: i. such Build is marked with the word "UNTESTED" or "INCOMPATIBLE" or "UNSTABLE" or "BETA" in any list of available builds and in every link initiating its download, where the list or link is under Licensee’s control; ii. Licensee displays the following notice in such a manner that anyone downloading the Intermediate Build must see the notice before commencing the download: "This is an intermediate build made available for testing purposes only. The code is untested and presumed incompatible with the <name of Java Specification>. You should not deploy or write to this code, but instead use the tested and certified <name of Java Specification> compatible version of the code that is available at [include a url and a link]. Redistribution of any Intermediate Build must retain this notice." Licensee must also include the same notice as a README.<shorthand name of specification> file with any source code bundle (e.g. tarball) download that corresponds to the Intermediate Build; iii. Moreover, Licensee shall not distribute (except as a passive download as provided above), market or promote Intermediate Builds, including without limitation in connection with providing any goods or services. iv. After making its initial release of a Product available, for any Intermediate Build subsequently made available by Licensee that is for the same context or environment (e.g. described by the same hardware architecture, operating system and version, and Java Virtual Machine version). Licensee must at all times also make the corresponding Product available. The link to such Product must be prominent and in close proximity to any corresponding Intermediate Build in any list of available builds or downloads. v. Licensee must include the following README.<shorthand name of specification> file in the root directory of any source code it may make available through access to a revision control system (e.g. CVS): "This version of [Project name] source code is made available in support of the open source development process. Some numbered or tagged revisions of this source have been tested and found to pass the <name of Java Specification> Compati...
AutoNDA by SimpleDocs

Related to Intermediate Builds

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Verizon OSS Facilities Any gateways, interfaces, databases, facilities, equipment, software, or systems, used by Verizon to provide Verizon OSS Services to ICG.

  • Site Visits ‌ The Commission may visit the School at any time and may, at its discretion, conduct site visits and monitoring. When appropriate, the Commission shall make reasonable efforts to provide notice of visits. Such site visits may include any activities reasonably related to fulfillment of the Commission’s oversight responsibilities including, but not limited to, inspection of the facilities; audit of financial books and records; inspection of records maintained by the School; interviews and observations of the principal, staff, school families, staff of an affiliated nonprofit or educational service provider and community members; and observation of classroom instruction.

  • DISADVANTAGED BUSINESS ENTERPRISE OR HISTORICALLY UNDERUTILIZED BUSINESS REQUIREMENTS The Engineer agrees to comply with the requirements set forth in Attachment H, Disadvantaged Business Enterprise or Historically Underutilized Business Subcontracting Plan Requirements with an assigned goal or a zero goal, as determined by the State.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • Site Visit 7.1 The Tenderer, at the Tenderer's own responsibility and risk, is encouraged to visit and examine and inspect the Site of the Required Services and its surroundings and obtain all information that may be necessary for preparing the Tender and entering in to a contract for the Services. The costs of visiting the Site shall beat the Tenderer's own expense.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!