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 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. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub17.) 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. Ansible or Puppet, .... ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 ○ Treating documentation as code. 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 14 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 15 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 16 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 17 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, 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 e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub15.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. 11 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 12 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 13 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 14 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 15 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ 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, 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 e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub17.) 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. Ansible or Puppet, .... ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users. 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 14 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 15 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 16 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 17 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Foundation

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 GitHub13GitHub14.) 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 ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users. 10 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 11 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 12 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 14 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Foundation

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 e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub14.) 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 ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users. 10 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 11 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 12 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 14 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Federation

Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license licence (like e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users. 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.Foundation

Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license licence (like MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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/display/OMB EGIBG/Operations+Management+Board 11 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation Federation ○ 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 license (like MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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.) GitHub18). All releases should be appropriately tagged. ● Adopt best practicespractises: ○ 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 ; 14 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 15 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 16 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 17 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 18 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ 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, 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 e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub12.) 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 ○ 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, 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 licence (like MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 ○ 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 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 GitHub13GitHub14.) All releases should be appropriately tagged. ● Adopt best practices: 10 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 11 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 12 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 14 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ 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, 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 licence (like e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub15.) All releases should be appropriately tagged. ● Adopt best practicespractises: ○ 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 ○ Treating documentation as code. 12 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/wiki/display/OMB 11 EGIBG/Operations+Management+Board 13 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 14 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 15 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, 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.) GitHub17). 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. 9 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 14 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 15 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 16 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 17 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Foundation

Software Compliance. Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license licence (like MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access rights to the EGI communityFederation. 11 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 12 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 13 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 14 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 ● 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 GitHub13GitHub15.) All releases should be appropriately tagged. ● Adopt best practicespractises: ○ 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, 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 e.g. MIT, BSD, Apache 2.0,...). ● The license should Unless otherwise agreed, be licensed to provide unlimited access and exploitation rights to the EGI communityFederation. ● 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 GitHub13GitHub12.) 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. 9 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 10 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 11 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 12 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Foundation

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 GitHub13GitHub16.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioninga Versioning schema. ○ 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 ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators and end users. 12 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 13 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 14 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 15 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 16 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.Foundation

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 GitHub13GitHub14.) 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 10 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/about/policy/policies_procedures.html 10 11 ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/OMB 11 12 ▇▇▇▇://▇▇▇.▇▇▇.▇▇/ 12 13 ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/portal/index.php?Page_Type=NGI&id=4 13 14 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/EGI-Foundation ○ Having automated testing in place. ○ Using code reviewing. ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, administrators and end users.