Code Repository Clause Samples

Code Repository. ‌ The codebase used in ▇▇▇▇▇, whether it comprises its software stack or the sources used to develop the Use Cases, are made public under the ”ict-▇▇▇▇▇” organisation in the GitHub site. During Y3 we have undergone a migration to this new organisation [25] and structure in an attempt to provide a centralised and clear set of repositories for all ▇▇▇▇▇-related developments, which will be left to the public to access after the project lifetime.
View Source
Code Repository. Contractor shall: 1. Enable and configure a tool to host ▇▇.▇▇▇ code associated with Developed Materials 2. Develop a method for State Entity Users to obtain and use the available code 3. Create and maintain a list with associated description of available source code 4. Publish updates with newly available code every quarter 5. Prior to code being added to the repository, the Contractor will conduct quality checks to ensure there are no outstanding defects that need to be corrected. The Contractor shall not be responsible for assisting State Entity Users with installation and troubleshooting once the State Entity Users has downloaded the code 6. If Contractor becomes aware of a defect after publishing source code Contractor will correct and republish with a note in the associated description that a new version has been published
View Source
Code Repository. Another important part of the community building effort is the creation of a specific area for sharing source code, project ideas, as well as to manage and promote cross-project development between the partners of the Mixed-Criticality community. For this reason there is a direct need to incorporate a Version Control System with complementing features integrated together with the website. This infrastructure will enable the community to collaborate together and manage in a meaningful way shared ideas and projects, through a multi-purpose Community Repository with many extensions that will be showcased in Chapter 5 with more details. In overview, the Community Repository is based on the Git distributed revision control system as the main facilitation for source code management. On top of Git, a feature-rich repository management solution is used called GitLab, which includes advanced user and group creation policies, source code reviews, issue tracking, wikis and many other enhancements useful for collaborating content creation.
View Source

Related to Code Repository

  • Money Market Fund Compliance Testing and Reporting Services Subject to the authorization and direction of the Trust and, in each case where appropriate, the review and comment by the Trust’s independent accountants and legal counsel, and in accordance with procedures that may be established from time to time between the Trust and the Administrator, the Administrator will:

  • Safety Procedures The Contractor shall: (a) comply with all applicable safety regulations according to Attachment H; (b) take care for the safety of all persons entitled to be on the Site; (c) use reasonable efforts to keep the Site and Works clear of unnecessary obstruction so as to avoid danger to these persons; (d) provide fencing, lighting, guarding and watching of the Works until completion and taking over under clause 10 [Employer's Taking Over]; and (e) provide any Temporary Works (including roadways, footways, guards and fences) which may be necessary, because of the execution of the Works, for the use and protection of the public and of owners and occupiers of adjacent land.

  • Monitoring and Risk Assessment of Securities Depositories Prior to the placement of any assets of the Fund with a non-U.S. Securities Depository, the Custodian: (a) shall provide to the Fund or its authorized representative an assessment of the custody risks associated with maintaining assets within such Securities Depository; and (b) shall have established a system to monitor the custody risks associated with maintaining assets with such Securities Depository on a continuing basis and to promptly notify the Fund or its Investment Adviser of any material changes in such risk. In performing its duties under this subsection, the Custodian shall use reasonable care and may rely on such reasonable sources of information as may be available including but not limited to: (i) published ratings; (ii) information supplied by a Subcustodian that is a participant in such Securities Depository; (iii) industry surveys or publications; (iv) information supplied by the depository itself, by its auditors (internal or external) or by the relevant Foreign Financial Regulatory Authority. It is acknowledged that information procured through some or all of these sources may not be independently verifiable by the Custodian and that direct access to Securities Depositories is limited under most circumstances. Accordingly, the Custodian shall not be responsible for errors or omissions in its duties hereunder provided that it has performed its monitoring and assessment duties with reasonable care. The risk assessment shall be provided to the Fund or its Investment Advisor by such means as the Custodian shall reasonably establish. Advices of material change in such assessment may be provided by the Custodian in the manner established as customary between the Fund and the Custodian for transmission of material market information.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).