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

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • In-Scope Projects Project Based Information Technology (IT) Consulting Services required by an Authorized User must be obtained via a Mini-Bid process under this Contract. The Authorized User shall issue a Mini-Bid with a SOW for the required Project Based IT Consulting Services. A Mini-Bid may include, but will not be limited to, projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated customized training for IT based applications. Additional examples of in-scope projects include, but are not limited to:  Technical architecture advisory services;  Business analysis for project development;  Proprietary software application development/customization, programming and integration;  Data information management (including data migration, data conversion, data manipulation, data integration);  Project management project support services - including, but not limited to; project management, project quality assurance and control, and Independent Verification & Validation (IV&V);  Disaster recovery/business continuity and testing;  Quality assurance;  Continuity of operations planning (COOP);  Data categorization; and  Open-source software implementation. Out-of-Scope Work There are service offerings expressly excluded from the scope of these contracts. In many instances, such services and/or offerings are (or will be) covered by another OGS Centralized Contract. Examples include:  Staff augmentation services;  Time and material services;  Web hosting;  Automated network monitoring or any other service provided principally through an automated process;  Hardware maintenance and support;  Software maintenance and support;  Ongoing maintenance and support;  Services priced on a per asset basis;  Services priced on a contingency basis;  Equipment maintenance;  Prepackaged training courses;  E-Learning;  Managed services;  Acquisition of equipment (hardware)  Acquisition of software, either Commercial off-the-shelf (COTS) software or pre-existing software;  Acquisition of non-consulting services, such as network provisioning, voice services (local, long- distance), or video bridging;  Cloud based or “As a Service” offerings, including but not limited to SaaS, IaaS, PaaS, and XaaS;  Any offering that is a combination of equipment, hardware, software, cloud or “as a service offerings”; and  Consulting or other installation work which is considered Public Works is excluded from purchase under the scope of this Contract. Historically, the New York State Bureau of Public Works has maintained that installation, maintenance and repair of equipment attached to any wall, ceiling or floor or affixed by hard wiring or plumbing is public work. In contrast, installation of a piece of equipment which is portable or a “plug-in” free-standing unit would not be considered public work. Thus, this Contract does not authorize installation where the equipment becomes a permanent part of the building structure, or is otherwise incorporated into the fabric of the building (i.e. installation on a wall, ceiling or floor in a fixed location, or affixed by hard- wiring or plumbing). See Appendix A, Clause 6, Wage and Hours Provisions. For questions about whether a proposed work constitutes public work, please contact the New York State Department of Labor’s Bureau of Public Work District Office in a specific area. A listing of district offices and contact information is available at xxxx://xxx.xxxxx.xx.xxx/workerprotection/publicwork/PWContactUs.shtm. Definitions Additional definitions applicable to this Contract can be found in Appendix B. Term Definition Authorized User Agreement The document resulting from the transactional Mini-Bid process, which sets forth the specifics regarding the services to be provided by the Contractor to the Authorized User, under the Project Based Information Technology Consulting Contract. Best Value The basis for awarding all service and technology contracts to the offerer that optimizes quality, cost and efficiency, among responsive and responsible offerers. Such basis shall be, wherever possible, quantifiable (State Finance Law §163 (1) (j)). Billing Contact The name, phone number, e-mail, and billing address a customer uses on a xxxx for contact information. Consultant Disclosure Legislation Chapter 10 of the Laws of 2006 amends State Finance Law § 8 and § 163 by requiring: that the Office of the State Comptroller (OSC) include in the Consulting Services Report it compiles annually on contracts issued by state agencies for consulting services during the previous fiscal year. xxxx://xxx.xxx.xxxxx.xx.xx/agencies/guide/MyWebHelp/Content/XI/18/C.htm Deliverables All services or products created during the performance or provision of Services hereunder or identified as a “Deliverable” in an applicable Mini-Bid. A Deliverable is a building block of an overall project. For the purposes of this Solicitation and the resulting Contract, a deliverable shall not be set forth as a status report, meeting attendance, a block of staff hours, or an invoice submission. Fixed Price Authorized User Agreement An agreement pursuant to the Centralized Contract that provides for a fix cost for a defined project. Government Contract A contract let by a Federal, State, or Local governmental body within the continental United States. Government Entity An entity at the federal, state, county, city or provincial level. Joint Venture A contractual agreement joining together two or more business enterprises for the purpose of performing on a State Contract. Knowledge Transfer The transfer of knowledge from the Contractor to the Authorized User. Knowledge Transfer can include full written system documentation including all system changes, training classes, manuals and other items. Depending on the scope of the transaction, there may or may not be a deliverable cost associated. All materials will be the property of the Authorized User unless specifically negotiated during the award process. May Denotes the permissive in a contract clause or specification. Refers to items or information that the State has deemed are worthy of obtaining, but not required or obligatory. Also see “Should”. Mini-Bid A type of Bid Document used by the Authorized User to obtain Services under the Project Based IT Consulting Services Contracts. Not To Exceed Rates (NTE) Refers to the New York State contract price set forth in Appendix D. Amounts proposed by the Contractor at the transactional level shall not exceed the hourly rates provided under this Contract (which will be defined values in US Dollars). Prime Contractor For the purposes of Technical qualifications, the business entity with whom a government entity directly has a contract. Project Based IT Consulting Services An OGS Centralized Contract which will provide a set of standardized terms and conditions, guidelines, processes, and templates for the development, distribution and award of specific deliverable-based and fixed-price Information Technology projects. Project Plan A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. Retainage A portion of the Authorized User and Contractor fixed-price agreement amount that is held back by the Authorized User until the deliverable or project is satisfactorily finished. Should Denotes the permissive in a contract clause or specification. Refers to items or information that the State has deemed are worthy of obtaining, but not required or obligatory. Also see “May”. Term Definition Solicitation A non-competitive periodic recruitment solicitation (“Solicitation”) for vendors that provide Project Based Information Technology Consulting Services. Vendor An enterprise that sells goods or services. Vendor Submission The complete response to this Solicitation submitted by a Vendor to provide, as applicable , the Product and services described in the Solicitation

  • Partnership Working 7.1 Partnerships will be supported by local authorities on four levels between:

  • 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

  • Projects The Annexes attached hereto describe the specific projects and the policy reforms and other activities related thereto (each, a “Project”) that the Government will carry out, or cause to be carried out, in furtherance of this Compact to achieve the Objectives and the Compact Goal.

  • Performance Improvement Xxxxxx Permanente and the Coalition are competing in a challenging market that is characterized by a limited workforce, changes in technology, changes in clinical practice, cultural diversity, changing demographics and high demand for quality service. The parties are committed to the enhancement of organizational performance so that working in Partnership is the way Xxxxxx Permanente does business. Under this Agreement, the parties will work together to: » develop and invest in people, including the development of and investment in managers, supervisors and union stewards; » engage employees at all levels; » align the systems and processes that support the achievement of organizational and Partnership goals; » enhance the ability of Coalition unions to advance their social mission and the welfare of their members; » recognize and reduce parallel structures; » ensure joint management-union accountability for performance; » grow membership; » redesign work processes to improve effectiveness, efficiency and work environment; » develop and xxxxxx unit-based teams; » share and establish expectations regarding broad adoption of successful practices in areas such as service, attendance, workplace safety, workforce development, cost structure reduction, scope of practice and performance-based pay; and » communicate with employees on an ongoing basis regarding performance goals and targets, as well as performance results at all levels of the organization. Each regional LMP council shall develop approaches aimed at reducing variation between medical centers, facilities and departments in the resources available for partnership. In particular, such a plan should: » ensure at a regional level there is adequate time for teams to review performance, identify opportunities for improvement, and develop and test changes to drive improvement; and » provide regional or facility support to departments as needed to cross-cover or backfill and jointly determine the most cost-effective manner to provide the support.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

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

  • Vendor Development Rights To the extent not inconsistent with Customer’s rights in the Work Product or as set forth herein, nothing in this Contract shall preclude Vendor from developing for itself, or for others, materials which are competitive with those produced as a result of the Services provided hereunder, provided that no Work Product is utilized, and no Intellectual Property Rights of Customer therein are infringed by such competitive materials. To the extent that Vendor wishes to use the Work Product, or acquire licensed rights in certain Intellectual Property Rights of Customer therein in order to offer competitive goods or services to third parties, Vendor and Customer agree to negotiate in good faith regarding an appropriate license and royalty agreement to allow for such.

Time is Money Join Law Insider Premium to draft better contracts faster.