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. 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. 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 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.
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: ● 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 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 at every point in time. ○ Having automated testing in place. 10 xxxxx://xxxxxxxxxx.xxx.xx/display/EGIPP/EGI+Policies+and+Procedures+Home 11 xxxxx://xxxxxxxxxx.xxx.xx/display/EGIBG/Operations+Management+Board 12 xxxx://xxx.xxx.xx/ 13 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 14 xxxxx://xxxxxx.xxx/EGI-Federation ○ 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:
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:
Software Compliance. In addition to the warranties specified within this Contract, the Contractor warrants that any equipment, internal or external component, device, or software products supplied under this Contract that process any date-time data will continue to function accurately to process the date-time data. In the event of any breach of warranty, the Contractor shall restore the products to the same level of performance as stated herein, or repair or replace the products with conforming products so as to minimize interruption to the use of the Goods, time being of the essence, at Contractor’s sole cost and expense.
Software Compliance. Ensure software compliance and compatibility with MDE/OGS 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 will 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 data/time data. Failure to provide required data will constitute a material breach of the Grant Agreement.
