You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

The idea is to establish an up-to-date repository of information about software projects and teams in order to: facilitate and support GÉANT software engineering community and to create a base and starting point for further analysis and reporting on GÉANT software development efforts.

Background

Information about individual participants in the GN4-2 project and their roles in particular activities and tasks is maintained via the internal COmanage Registry [GN-COmanage]. This type of information management is organised in a delegated manner is designed for virtual collaborations, and very well suited for large collaborations such as the GN4-2 project. Activity and Task Leaders are delegated with the responsibility of managing the information about their task members. Information from this registry is used for generating group mailing lists, making authorization decisions when GÉANT participants access other services, etc. However, this registry does not contain more granular information, for example in which software development teams, an individual is participating. In previous GÉANT projects, the Forge service fulfilled the role of a hub for software efforts [GN-Forge]. At its peak usage, the Forge contained information on 10 projects. However, the service has now been deprecated to the status of archive.

In-depth information about the project software development teams has been already gathered in the survey conducted by the SWM team. 30 software projects are being developed by about 20 software development teams of highly skilled professionals originating from different member NRENs. 

Considering the above, an up-to-date catalogue of software projects and teams needs to be established in order to:

  • facilitate and support GÉANT software engineering community, 
  • and to create a base and starting point for further analysis and reporting on GÉANT software development efforts.

Example use cases for the catalogue

As a software engineer I can search for projects doing a related work so that I can start cooperating.As a training coordinator I can get an overview of project characteristics so that I can better plan training activities.As a leader I can search for contact points and people responsible.
As a team member I can search for people with specific competences so that I can start exchanging experience.As an infrastructure provider I can get an overview on projects and teams so that I can better adjust my service to real community needs.As someone I can get an overview of software development efforts in my organisation so that I can make better decision about ... XXX.

Functionality

  • indexing software projects and teams;
  • focus on organisational and technical aspects;
  • unified view for all items in catalogue;
  • access restricted to organisation members;
  • information collected automatically;
  • information download from heterogeneous and scattered sources;
  • information updated continuously.
  • No labels