Git Repository Sample Clauses

Git Repository. The Contractor will use the County Git repository during the entire lifecycle of the project from inception to final delivery. The Contractor will create and document design documents, Data flow diagrams, security diagrams, configuration settings, software or hardware requirements and specifications, attribution to third-party code, libraries and all dependencies, and any other documentation related to all County Source Code and corresponding version-controlled documentation within the Git repository. This documentation must include an Installation Guide and a User Guide for the final delivered source code such that County may download, install, and make full functional use of the delivered code as specified and intended. BACKGROUND CHECK FORM Definitions See Appendix O (Glossary and Acronyms) INTENTIONALLY OMITTED INTENTIONALLY OMITTED
AutoNDA by SimpleDocs
Git Repository. The Contractor will use the County Git repository during the entire lifecycle of the project from inception to final delivery. The Contractor will create and document design documents, Data flow diagrams, security diagrams, configuration settings, software or hardware requirements and specifications, attribution to third-party code, libraries and all dependencies, and any other documentation related to all County Source Code and corresponding version-controlled documentation within the Git repository. This documentation must include an Installation Guide and a User Guide for the final delivered source code such that County may download, install, and make full functional use of the delivered code as specified and intended.
Git Repository. The Contractor will use the County Git repository during the entire lifecycle of the project from inception to final delivery. The Contractor will create and document design documents, Data flow diagrams, security diagrams, configuration settings, software or hardware requirements and specifications, attribution to third-party code, libraries and all dependencies, and any other documentation related to all County Source Code and corresponding version-controlled documentation within the Git repository. This documentation must include an Installation Guide and a User Guide for the final delivered source code such that County may download, install, and make full functional use of the delivered code as specified and intended. DMH CONTRACTOR’ S COMPLIANCE WITH INFORMATION SECURITY REQUIREMENTS Contractor Agency Name: Contractor shall provide information about its information security practices by completing this Exhibit annually. By submitting this Exhibit, Contractor certifies that they will be compliant with Los Angeles County Board of Supervisors Policies and attest that it has implemented adequate controls to meet the following expected Information Security minimum standards, at the commencement and during the term of any awarded Contract. Contractor must be prepared to provide supporting evidence upon request. The completed forms must be returned to the DMH Information Security Officer (DISO) for approval within 10 business days from receipt. Any significant changes during the term of the Contract must be reported within 10 business days of implementation. Depending on the change(s), Contractor may be asked to re-submit this Exhibit. COMPLIANCE QUESTIONS YES NO N/A YES NO ☐ ☐ ☐ ☐ ☐ YES ☐ NO ☐ N/A ☐ YES ☐ NO ☐ YES ☐ NO ☐ N/A ☐ YES ☐ NO ☐ YES ☐ NO ☐ N/A ☐ YES ☐ NO ☐ YES NO N/A YES NO ☐ ☐ ☐ ☐ ☐ YES NO N/A YES NO ☐ ☐ ☐ ☐ ☐ YES ☐ NO ☐ N/A ☐ YES ☐ NO ☐ YES ☐ NO ☐ N/A ☐ YES ☐ NO ☐ 1 Will County’s non-public data stored on your workstation(s) be encrypted? If “NO” or N/A, please explain. 2 Will County non-public data stored on your laptop(s) be encrypted? If “NO” or N/A, please explain. 3 Will County’s non-public data stored on removable media be encrypted? If “NO” or N/A, please explain. 4 Will County non-public data be encrypted when transported? If “NO” or N/A, please explain. 5 Will any validation/attestation reports generated by the encryption tools be maintained? If “NO” or N/A, please explain. 6 Will County’s non-public data be stored on remote servers*? *C...

Related to Git Repository

  • CREDIT REPORTING For each Mortgage Loan, the Company shall accurately and fully furnish, in accordance with the Fair Credit Reporting Act and its implementing regulations, accurate and complete information on its borrower credit files to each of the following credit repositories: Equifax Credit Information Services, Inc., TransUnion, LLC and Experian Information Solution, Inc. on a monthly basis.

  • Credit Reports Borrower authorizes Lender to obtain a credit report on Borrower at any time.

  • Audit Report 38 10.1.2 Quarterly Reports.............................................................................38 10.1.3 Monthly Reports...............................................................................39 10.1.4

  • Single Audit Report A. The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Reporting and Payment Procedures Risk Summary Sheets for each risk and a monthly bordereau of all risks ceded shall be submitted to the Reinsurer within (twenty) 20 working days after the last day of each month. Any premium amounts due the Reinsurer shall be paid with the bordereau. Risk Summary Sheets for each insured shall include the following information:

  • Audit Reports promptly upon receipt thereof, one copy of each other financial report and internal control letter submitted to the Company by independent accountants in connection with any annual, interim or special audit made by them of the books of the Company.

  • Reporting and Record Keeping CONTRACTOR shall comply with all program and fiscal reporting requirements set forth by appropriate Federal, State and local agencies, and as required by the COUNTY. (c) CONTRACTOR agrees to provide to COUNTY, to any Federal or State department having monitoring or review authority, to COUNTY's authorized representatives, and/or their appropriate audit agencies upon reasonable notice, access to and the right to examine all records and documents necessary to determine compliance with relevant Federal, State, and local statutes, rules and regulations, and this Agreement, and to evaluate the quality, appropriateness and timeliness of services performed.

  • FAILURE TO MEET REPORTING OBLIGATIONS 14.1 Should the Licensee fail to furnish the Licence Parameter Return referred to in clause 13.1 above within the required time period, SAMRO will be entitled to invoice the Licensee based on the licence parameters upon which the preceding invoice was based.

  • Procurement procedures 11.1 The Recipient must secure the best value for money and shall act in a fair, open and non-discriminatory manner in all purchases of goods and services.

  • AUDIT REPORT SUBMISSION Audit reports must be submitted no later than 150 days following cancellation, termination or expiration of this Agreement.

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