ON DOCUMENTATION Sample Clauses

ON DOCUMENTATION. Long-term sustainability of an open source project is promoted through effective communication of long-term vision of goals and plan for how the project will evolve over time. Such longevity is supported through a number of means, including: provision of roadmaps (and other documentation and information) tailored for different stakeholder groups; and documentation of source code and associated digital assets. For additional information on these means, please see deliverable D4.3. For provision of roadmaps and associated information from each open source project it is essential to address: potential code contributors (external and independent of the PREFORMA project) with relevant information in order to attract interest and code contributions from external contributors. Similarly, information from each open source project also needs to address potential external users (and contents of roadmaps need to be tailored accordingly). Relevant information includes information concerning conditions for active participation. Similarly, relevant information also includes conditions for use and distribution of software. Further, conditions for involvement and handling of (and potential transfer of) copyright, trademarks, patents, and other aspects which impact on the extent to which it is possible to attract contributions for open source projects need to be addressed. Governance issues and organisation of long-term management for each open source project needs to be properly addressed (e.g. foundations4 and other forms of organisational entities should be considered). The scope for roadmaps need to cover strategic plans and releases planned for software from each open source project at least for the time period until December 2020.
AutoNDA by SimpleDocs

Related to ON DOCUMENTATION

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Legal Documentation Pursuant to The DMB Act (Public Act 431, as amended) all leases must be approved as to legal form by the Attorney General’s office, which includes the submission of documentation necessary to evidence legal authority of Bidder to enter into the lease agreement, including the signatory’s authority to bind. For your convenience, a guideline indicating necessary legal documentation is included with this RFP. Failure to provide appropriate legal documentation may result in your proposal being rejected.

  • Construction Documents The architectural and engineering documents setting forth the design for the Project prepared by the Design Professional. Construction Documents include, but are not limited to, the Specifications, the Drawings, the Supplementary Conditions, the General Conditions, and all Addenda.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Construction Document Phase 1.4.1 Based on the approved Design Development Documents, Guaranteed Maximum Price, coordinated models and any further adjustments in the scope or quality of the Project or in the Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Construction Documents consisting of Drawings, Schedules and Specifications derived from the model(s) in accordance with Owner’s written requirements setting forth in detail the requirements for construction of the Project, including, without limitation, the BIM Execution Plan and “Facility Design Guidelines”. The Plans, Drawings and Specifications for the entire Project shall be so prepared that same will call for the construction of the building and related facilities, together with its built-in permanent fixtures and equipment which will cost not more than the Guaranteed Maximum Price accepted by Owner, or the Amount Available for the Construction Contract established by Owner if no Guaranteed Maximum Price proposal has been accepted by Owner. The Architect/Engineer will be responsible for managing the design to stay within such Guaranteed Maximum Price proposal or Amount Available for the Construction Contract. The Architect/Engineer shall review the Construction Documents as they are being prepared at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Construction Documents. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner.

  • Tender Documentation 1. A procuring entity shall promptly make available or provide on request to any interested supplier tender documentation that includes all information necessary to permit the supplier to prepare and submit a responsive tender. Unless already provided in the notice of intended procurement, that tender documentation shall include a complete description of:

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

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