Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

...

GÉANT Software Catalogue is an up-to-date repository of information about software development projects and teams

...

. The tool facilitates and supports the software engineering community in various processes that require knowledge on 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:

More than 4 years ago, in February 2019, the Software Catalogue was launched and keeps working on the long term mission of building and sharing the "big picture" of GEANT software development efforts. The SC does this in an automated way by exploring projects' resources like Git, JIRA, GitHub, GitLab and many others.

SC may be compared to other available directories like, for example, Apache Projects Directory.

Image Added

...


Example use cases for the catalogue

Advanced Tables - Table Plus
border1
rowStylesbackground:lightyellow,background: lightyellow
heading0


As a software engineer

...

I can search for

...

teams 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

...

maintainer I can recognize actual community in my project.
As

...

developer of a single microservice I can get an overview on a team's joint effort put into our multi-modular software.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

...

<place for your use case here>


Highlights

  • indexing software projects

...

  • ;
  • focus on organisational and technical aspects;
  • actual project community is recognized instead of just "declared" team members;
  • unified view for all

...

  • software initiatives;
  • access restricted to organisation members;
  • information collected automatically;
  • information download from heterogeneous and scattered sources;
  • integration with Mend.io and SonarQube.
  • information updated continuously.

Learn more