Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-Engage:Software and services"

From EGIWiki
Jump to navigation Jump to search
 
(22 intermediate revisions by the same user not shown)
Line 7: Line 7:
<br> This page provides all rules and guides regarding software and services created under the EGI-Engage project.  
<br> This page provides all rules and guides regarding software and services created under the EGI-Engage project.  


<br> '''Any software created under EGI-Engage should be listed and described (license, source code repository, copyright owner) under <big>[[EGI-Engage:Software and services#Software_and_services_list|Software Copyrights and Licenses]]</big>'''
<br>  


== Quality  ==
= Quality  =


=== Services  ===
== Services  ==


'''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 [http://fitsm.eu FedSM 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 [http://fitsm.eu FedSM project].  
Line 19: Line 19:
<br>  
<br>  


=== Software  ===
== Software  ==


'''The software produced''' within the project will follow the well established [[EGI Software Component Delivery|'''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 software produced''' within the project will follow the well established [[EGI Software Component Delivery|'''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.  
Line 31: Line 31:
<br>  
<br>  


=== Procedure for quality assessment <br>  ===
== Software deliverable/milestone testing<br>  ==
 
This procedure is part of [[EGI-Engage:Quality_Plan#Review_process_for_deliverables_and_milestones|Review process for deliverables and milestones]]
It describe how quality check is done for SW deliverables.
 
'''Requirement:'''
 
*Production tools should have a production and a testing/devel instance (at least 2 instances in total)
 
'''Testing Options:'''
 
*Each product team should choose between two possible ways to verify the quality of its release:
*#Manual test
*#(Semi-)Automatic internal procedure to test the release
 
In both cases, tests and short document must be finished by the deliverable deadline in the DoA. Similar procedures can be applied to internal EGI-Engage releases (between to SW deliverables) or to releases related to the core service activities. In these cases the short document is not strictly needed although storing a test report would be useful.
 
<br> '''1. Manual Test:'''
 
#as for the classical deliverables (the documents), 3 reviewers (1 moderator + 2 reviewers) will be assigned to each software deliverable. The WP manager has the responsibility to identify the reviewers.
#The reviewers will perform the validation tests on the candidate release
#In the case of deliverables containing more than 1 software releases, we will have 3 reviewers for deliverable plus supporting testers
#The candidate release should be installed on the testing/devel instance
#Tests will be executed within a week. During this period the testing/devel instance should not be updated. Reviewers and developers should agree on the week to perform the tests
#Outcome of the testing process will be part of the short document describing the software release
 
'''2. (Semi-)Automatic Internal Testing procedure:'''
 
#the PT should propose to its work package leader a (semi-)automatic procedure to verify the quality of its releases. An example of this procedure is a continuous integration system with a set of automatic/manual tests executed against each built.
#this procedure should be properly documented.
#the document at point 2) should:
##describe the process adopted by the PT to create a new release
##describe the quality tests performed against each release
##contain instructions to rollback to the previous release in case of issues in production and describe how the risk of data loss (e.g. for A/R and accounting) is managed
#the WP manager, in collaboration with the project management, should validate and approve the procedure verifying it can guarantee a good level of quality assessment. 5) Outcome of this (Semi-)Automatic Internal Testing procedure should be reported in the short document describing the software release (including a reference to the document at point 2))


<br>
This procedure is part of [[PROC01 Deliverables and milestones review|Review process for deliverables and milestones]] It describe how quality check is done for SW deliverables and can be found under [https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing]


== Licenses  ==
= Licenses  =


*'''New developed software:''' An OSI-approved license (http://opensource.org/licenses), for any new software developed within the Project;  
*'''New developed software:''' An OSI-approved license (http://opensource.org/licenses), for any new software developed within the Project;  
Line 75: Line 41:
*'''Existing software:''' If no existing OSI license is being used for existing software, the adoption of the Apache 2.0 license is possible.
*'''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  ==
= 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.  
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.  
Line 95: Line 61:


</pre>  
</pre>  
== Acknowledgement for websites  ==
= Acknowledgement for websites  =


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


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


Template: [[Image:Tool acknowledgment4.png|500px|Tool acknowledgment4.png]]  
Template: [[Image:Tool acknowledgment4.png|500px|Tool acknowledgment4.png]]  


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


Template: [[Image:Tool acknowledgment3.png|500px|Tool acknowledgment3.png]]  
Template: [[Image:Tool acknowledgment3.png|500px|Tool acknowledgment3.png]]  
Line 109: Line 75:
<br>  
<br>  


== Software and services list  ==
The following gives an overview about copyright and licenses used and granted in the EGI-Engage project.
<br>
{| class="wikitable sortable"
|-
! valign="top" rowspan="2" | Work Package/EGI
! colspan="2" | Application / Tool
! valign="top" rowspan="2" | 3<sup>rd</sup> party tool
! valign="top" rowspan="2" | Source Code Repository (URL)
! valign="top" rowspan="2" | Copyright owner
! valign="top" rowspan="2" | License
! valign="top" rowspan="2" | Remarks
|-
! EGI Application
! <br>
|-
| WP4<br>
| colspan="2" | rOCCI-* (core, api, cli, server)<br>
| <br>
| [https://github.com/EGI-FCTF/rOCCI https://github.com/EGI-FCTF/rOCCI ]<br>
| CESNET<br>
| Apache License, Version 2.0<br>
| <br>
|-
| <span style="font-size: 13.2799997329712px;">WP4</span>
| colspan="2" | oneacct-export<br>
| <br>
| [https://github.com/EGI-FCTF/oneacct_export https://github.com/EGI-FCTF/oneacct_export]<br>
| CESNET
| MIT License<br>
| <br>
|-
| WP4<br>
| colspan="2" | jOCCI-* (core, api)<br>
| <br>
|
[https://github.com/EGI-FCTF/jOCCI-api https://github.com/EGI-FCTF/jOCCI-api<br>][https://github.com/EGI-FCTF/jOCCI-core https://github.com/EGI-FCTF/jOCCI-core]
| CESNET
| Apache License, Version 2.0
| <br>
|-
| WP4<br>
| colspan="2" | Cloud-BDII-provider<br>
| <br>
| [https://github.com/EGI-FCTF/cloud-bdii-provider https://github.com/EGI-FCTF/cloud-bdii-provider]
|
CSIC<br>
| ASL 2.0<br>
| although this is a FedCloud wide collaboration (authors are A. López, S. Pinto, B. Parak, E. Fernández, B. Hagemeier)
|-
| WP4<br>
| colspan="2" | OCCI-OS<br>
| <br>
| [https://github.com/EGI-FCTF/occi-os https://github.com/EGI-FCTF/occi-os]
| CSIC
| ASL 2.0
| main authors originally from intel, maintenance done by CSIC, to be substituded by "ooi"<br>
|-
| WP4<br>
| colspan="2" | ooi<br>
| <br>
| [https://github.com/IFCA/ooi https://github.com/IFCA/ooi]
| CSIC
| ASL 2.0
| <br>
|-
| WP4<br>
| colspan="2" | EGI: onedata<br>
| <br>
| Not available yet - check [http://www.onedata.org] for updates
| ACC Cyfronet AGH
| MIT
| Remarks: Source repository for current latest version 3.0 will be available soon.
|-
| <span style="font-size: 13.2799997329712px;">WP4</span>
| colspan="2" | OSSSM<br>
| <br>
| [https://github.com/EGI-FCTF/osssm https://github.com/EGI-FCTF/osssm]
| IN2P3<br>
| GPL2<br>
| Deprecated
|-
| <span style="font-size: 13.2799997329712px;">WP4</span>
| colspan="2" | cASO
| <br>
| [https://github.com/IFCA/caso/ https://github.com/IFCA/caso/]
| CSIC
| ASL 2.0
| <br>
|-
| <span style="font-size: 13.2799997329712px;">WP4</span>
| colspan="2" | keystone-voms
| <br>
| [https://github.com/IFCA/keystone-voms https://github.com/IFCA/keystone-voms]
| CSIC
| ASL 2.0
| <br>
|-
| WP4
| colspan="2" | Glancepush-vmcatcher
| <br>
| [https://github.com/EGI-FCTF/glancepush-vmcatcher2 https://github.com/EGI-FCTF/glancepush-vmcatcher2]
| BIFI
| MIT
| <br>
|-
| WP4
| colspan="2" | vmcatcher/vmcaster
| <br>
| https://github.com/hepix-virtualisation/vmcatcher <br> https://github.com/hepix-virtualisation/vmcaster
| O. Synge
| ASL 2.0
| <br>
|-
| WP4
| colspan="2" | EGI-FCTF/cloud-bdii-provider
| <br>
| https://github.com/EGI-FCTF/cloud-bdii-provider <br> https://github.com/EGI-FCTF/cloud-bdii-provider
| EGI
| Apache
| <br>
|-
| EGI<br>
| colspan="2" | OSGC - OpenSource Geospatial Catalogue
| <br>
| [http://sourceforge.net/projects/osgcat/ http://sourceforge.net/projects/osgcat/]
| EGI.eu
| GPLv3
| <br>
|-
| <span style="font-size: 13.2799997329712px;">WP4</span>
| colspan="2" | synnefo connectors
| <br>
| [https://github.com/grnet/synnefo/ https://github.com/grnet/synnefo/]
| GRNET S.A.
| GPL v3
| synnefo connectors like occi, cdmi, etc
|-
| <br>
| colspan="2" | GPGPU-enabled CREAM
| <br>
| [https://github.com/italiangrid/cream https://github.com/italiangrid/cream]
| Members of the EGEE Collaboration
| ASL 2.0
| CREAM, BLAH, Infoproviders
|-
| WP3
| colspan="2" | Application Database
| <br>
| <br>
| IASA<br>
| Apache 2.0<br>
|
*Server side:
**Zend Framework (New BSD License) - http://framework.zend.com/license
**MySQL data back-end (GPL) - http://www.mysql.com/about/legal/licensing/index.html
**PHP (PHP License v3.01, an Open Source license) - http://www.php.net/license/3_01.txt
**Apache (Apache License, Version 2.0) - http://www.apache.org/licenses/LICENSE-2.0
*Client side:
**Dõjõ Toolkit (Academic free license / New BSD License) - http://www.dojotoolkit.org/reference-guide/quickstart/introduction/licensing.html
**jQuery (MIT/GPL v2 License) - http://jquery.org/license
**AMMAPS Flash map- (Commercial Product -Proprietary license Ammap software single web site license) - http://www.ammap.com/licenses/single_web_site/
|-
| EGI<br>
| colspan="2" | Training market place
| <br>
| <br>
| STFC<br>
| Apache 2.0
| <br>
|-
| WP6 (LifeWatch)
| colspan="2" | [[EGI-Engage:WP6 Caffe|Caffe - Assisted pattern recognition tools integrated with EGI for citizen science]]
| <br>
| [https://github.com/BVLC/caffe https://github.com/BVLC/caffe], [https://github.com/EGI-Lifewatch-CC https://github.com/EGI-Lifewatch-CC]
| Lifewatch<br>
| BSD 2-Clause License
| <br>
|-
| WP6 (DARIAH)
| colspan="2" | Data repository for DARIAH
| <br>
| <br>
| <br>
| <br>
| <br>
|-
| WP6 (EISCAT_3D)
| colspan="2" | Production portal for EISCAT_3D
| <br>
| <br>
| <br>
| <br>
| <br>
|-
| WP6 (MoBrain)
| colspan="2" | Fully integrated MoBrain web portal
| <br>
| <br>
| <br>
| <br>
| <br>
|-
| WP6 (DARIAH)
| colspan="2" | Final version of Multi-Source Distributed Real-Time Search and Information Retrieval application
| <br>
| <br>
| <br>
| <br>
| <br>
|-
| WP6 (LifeWatch)
| colspan="2" | Data flow handler and basic R tools to integrate and process data from Ecological Observatories on EGI
| <br>
| <br>
| <br>
| <br>
| <br>
|}
<br>
<br> <br>


[[Category:EGI-Engage]]
[[Category:EGI-Engage]]

Latest revision as of 17:00, 23 October 2017

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



Help and support: quality@egi.eu


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


Quality

Services

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


Software

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 https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing

Licenses

  • New developed software: An OSI-approved license (http://opensource.org/licenses), 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, 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
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 @ egi.eu for customized version of banner

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

Template: Tool acknowledgment4.png

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

Template: Tool acknowledgment3.png