EGI-Engage:Software and services

From EGIWiki
Jump to: navigation, search
EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures

Help and support:

This page provides all rules and guides regarding software and services created under the EGI-Engage project.



Quality of services produced within EGI-Engage project will be ensured by the adoption of the EGI Services management standard FitSM, a international standard developed by the FedSM project.

Instruction for Tools teams can be found under Instructions Tools teams


The software produced within the project will follow the well established Software provisioning process that has been adopted since 2010, based on the definition of quality criteria, quality verification and software validation in a controlled production environment of the federated EGI infrastructure.

The development activities within the project will augment capabilities of existing open source software. The resulting software code, tools and interfaces developed as part of EGI-Engage will be released as open source code and the full access will be provided via publicly available source code repositories such as GitHub, SourceForge, Subversion (SVN), Concurrent Version System (CVS) etc. Software developers will be able to choose their preferred source code repository to better integrate with existing practices, nevertheless they will need to

  • ensure that the contribution is openly accessible,
  • add the metadata information needed to enable reuse,
  • communicate the URL to the consortium.

Software deliverable/milestone testing

This procedure is part of Review process for deliverables and milestones It describe how quality check is done for SW deliverables and can be found under


  • New developed software: An OSI-approved license (, for any new software developed within the Project;
  • Further develop software: In order to comply with the open access policy and maximise possibility for reuse of results, EGI-Engage partners, together, agree not to further develop software released with a non-open license and which cannot be re-released using an OSI-approved license.
  • Existing software: If no existing OSI license is being used for existing software, the adoption of the Apache 2.0 license is possible.

Source Code

In order to comply with the open access policy and maximise possibility for reuse of results, EGI-Engage software code, tools and interfaces that fall under the joint ownership will be published under an OSI-approved license . If no existing OSI license is being used, we propose the adoption of the Apache 2.0 license. Free and unrestricted access to research result is a measurable barrier to uptake by SME’s and can slow down innovation in measurable terms , and the consortium will make it a priority to comply with the Horizon 2020 Mandate in full support of Europe 2020 Initiative’s Economic Growth Agenda.

The work represented by this source file was partially or entirely funded by the EGI-Engage project co-funded by the European Union (EU) Horizon 2020 program under Grant number 654142.

Copyright [yyyy] [name of copyright owner]

Licensed under the [license name] (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at [link to license]

Unless required by applicable law or agreed to in writing, software 
distributed under the License is distributed on an "AS IS" BASIS, 
See the License for the specific language governing permissions and 
limitations under the License.

Acknowledgement for websites

Acknowledgement should be visible at the portals and source code public repositories.
Please contact quality @ for customized version of banner

To acknowledge EGI-Engage (Service co-funded by EGI-Engage)

Template: Tool acknowledgment4.png

To acknowledge EGI-Engage (Service co-funded by and EGI-Engage)

Template: Tool acknowledgment3.png