Software Compliance Sample Clauses
The Software Compliance clause establishes requirements for ensuring that all software used or provided under the agreement adheres to applicable laws, regulations, and licensing terms. Typically, this clause obligates the party supplying software to confirm that it is properly licensed, free from unauthorized code, and does not infringe on third-party intellectual property rights. By including this clause, the agreement aims to prevent legal disputes, protect against unlicensed or malicious software, and allocate responsibility for compliance, thereby reducing the risk of regulatory or legal violations.
POPULAR SAMPLE Copied 2 times
Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (e.g. MIT, BSD, Apache 2.0,...). ● Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI Federation. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub14.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users.
Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.
Software Compliance. Ensure software compliance and compatibility with the Department’s data systems for activities provided under this Agreement, including but not limited to stored data, databases and interfaces for the production of work products and reports. All required data under this Agreement must be provided in an accurate and timely manner without interruption, failure or errors due to the inaccuracy of the Grantee’s business operations for processing data. All information systems, electronic or hard copy, that contain state or federal data must be protected from unauthorized access.
Software Compliance. The Contractor must ensure software compliance and compatibility with the Department’s data systems for services provided under this agreement including, but not limited to: stored data, databases, and interfaces for the production of work products and reports. All required data under this agreement shall be provided in an accurate and timely manner without interruption, failure or errors due to the inaccuracy of the Contractor’s business operations for processing date/time data.
Software Compliance. The Grantee must ensure software compliance and compatibility with the Department’s data systems for services provided under this agreement including, but not limited to: stored data, databases, and interfaces for the production of work products and reports. All required data under this agreement shall be provided in an accurate and timely manner without interruption, failure or errors due to the inaccuracy of the Grantee’s business operations for processing date/time data.
Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should:
Software Compliance. Ensure software compliance and compatibility with the Department’s data systems for activities provided under this Agreement, including but not limited to stored data, databases and interfaces for the production of work products and reports. All required data under this Agreement must be provided in an accurate and timely manner without interruption, failure or errors due to the inaccuracy of the Grantee’s business operations for processing data. All information systems, electronic or hard copy, that contain state or federal data must be protected from unauthorized access. State or federal data includes data and information provided to Grantee or Grantee’s Subcontractor by or on behalf of the State or federal government, and all data and information derived therefrom, is the exclusive property of the State or federal government.
Software Compliance. 22.01 The Grantee must ensure software compliance and compatibility with the SCAO’s data system for Services provided including, but not limited to: stored data, databases and interfaces for the production of work products and reports. All required data under this Agreement shall be provided in an accurate and timely manner without interruption, failure, or errors due to the inaccuracy of the Grantee’s business operations for processing date/time data.
Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive licence (e.g. MIT, BSD, Apache 2.0,...). ● Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI Federation. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub17.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. 13 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIPP/EGI+Policies+and+Procedures+Home 14 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIBG/Operations+Management+Board 15 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 16 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 17 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Federation ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible or Puppet, .... ○ Taking security aspects into consideration at every point in time. ○ Having automated testing in place. ○ Using code reviewing. ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users.
Software Compliance. End-users shall use software in accordance with terms of license agreements and copyright laws. CMU does not have the right to reproduce software or related documentation without proper written authorization. The unauthorized copying or redistribution of copyrighted software is illegal. CMU reserves the right to impose disciplinary and/or legal action as deemed appropriate. Prohibited Use includes, but is not limited to: