Common use of Software Compliance Clause in Contracts

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. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive licence (e.g. like 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.) GitHub18). All releases should be appropriately tagged. ● Adopt best practicespractises: ○ Defining and enforcing code style guidelines. 13 ; ○ Using Semantic Versioning; ○ Using a Configuration Management frameworks such as Ansible; 14 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIPP/EGI+Policies+and+Procedures+Home 14 15 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIBG/Operations+Management+Board 15 16 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 16 17 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 17 18 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Federation ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible or Puppet, .... ○ 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 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 GitHub17GitHub14.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. 13 ○ 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 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIPP/EGI+Policies+and+Procedures+Home 14 11 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/display/EGIBG/Operations+Management+Board 15 12 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 16 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 17 14 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/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.