ON ACHIEVING SUSTAINABLE OPEN SOURCE PROJECTS Sample Clauses

ON ACHIEVING SUSTAINABLE OPEN SOURCE PROJECTS. Long-term sustainability of a vibrant business ecosystem presupposes sustainable open source projects and associated communities. There are a number of business models used by companies involved in open source projects and fundamental to most is adherence to and appreciation of values and norms established in open collaborations. There are a number of factors which impact on establishment of successful and long-term sustainable open source communities. It has been noted that establishment of long-term sustainable communities is a challenge and some even consider it as an art8. For example, the extent to which an open source project successfully manages to attract and maintain contributions from talented contributors has shown to be an important aspect9. Previous research has shown mixed success for different open source projects concerning establishment of vibrant communities10. Similarly, another important aspect is collaboration between communities for a file format standard and communities for its implementation in open source software11. Further, an open source project needs to recognise and be adaptive to that there may be a number of different motivations for external contributors12. Use and reuse of software from different open source projects need to recognise and adhere to licensing and other (technical, legal, and cultural) conditions. For long-term sustainable open source projects (including software from PREFORMA) it is critical to adhere to all such conditions in order to successfully achieve intended goals. This includes strict adherence to licensing requirements when software is to be integrated with software from other projects. For example, if supplier A in PREFORMA wishes to integrate software from supplier B and C it is critical that all software strictly adheres to the same licensing requirements in order to allow for integration, distribution, and redistribution of integrated software. For further information concerning achieving sustainable open source projects, please see deliverable D4.3.
AutoNDA by SimpleDocs

Related to ON ACHIEVING SUSTAINABLE OPEN SOURCE PROJECTS

  • Performance Improvement Plan timely and accurate completion of key actions due within the reporting period 100 percent The Supplier will design and develop an improvement plan and agree milestones and deliverables with the Authority 3.2 The Authority may from time to time make changes to the KPIs measured as set out in paragraph 3.1 above and shall issue a replacement version to the Supplier. The Authority shall give notice In Writing of any such change to the KPIs measured and shall specify the date from which the replacement KPIs must be used for future reports. Such date shall be at least thirty (30) calendar days following the date of the notice to the Supplier.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • 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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Condominiums/Planned Unit Developments If the Mortgaged Property is a condominium unit or a planned unit development (other than a de minimis planned unit development) such condominium or planned unit development project such Mortgage Loan was originated in accordance with, and the Mortgaged Property meets the guidelines set forth in the Originator's Underwriting Guidelines;

  • 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.

  • Project Goals The schedule, budget, physical, technical and other objectives for the Project shall be defined.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). 2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance. 2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks. 2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

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