WP4: EOSC Science Cluster Pilots and Driver projects

​

WP4 meeting

24 April 2024 - Online (Zoom) - indico: https://indico.cern.ch/event/1407644/

Doglioni, Caterina Juckeland, Guido

[she/her] [he/him]

UniMan/CERN HZDR

​

Participants:

BSC, CERTH, CU, ELIXIR-Hub, HZDR, OpenAIRE, UniMan, UPM, UvA, CU

This project has received funding from the European Union’s Horizon Europe Programme under GA 101129744 — EVERSE — HORIZON-INFRA-2023-EOSC-01-02

From the kick-off meeting: Overview and scope of WP4

Direct connection between researchers and EVERSE through pilots and science clusters

1

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

WP4: what we need to do in the near future

The first 6-12 months

2

→ first talk �from particle �physics (ESCAPE) �today

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

How do we organise our work, in practice

The next 5 meetings will be about pilot cases - fill in this sheet for booking a slot

3

We would ask you to have some slides (<20-25’ in total) for all following points - 1

• These points have been inspired by the TF2 reference model draft here (OwnCloud link)
• We can provide a google slides template if you want to use it�
• (1) Describe the community that uses the software in your pilot
• Who is the developer? (One, many, organised, less organised, changeable…)
• Who are the users, and how experienced are they? �
• (2) Describe the technical aspects of the code in your pilot(s) according to the following template:
• Software tier
• Tier 1: Analysis code
• Tier 2: Prototype Tools
• Tier 3: Research Software Infrastructure (includes services)
• Technical specifications: language(s), size of codebase, where does it run (specify if it’s on a VRE, HPC…) �
• (3) Describe your software lifecycle [https://zenodo.org/records/8324828]
• This includes information in (1) but also the following points:
• How has it been developed so far (version control, contribution policy)
• How do you onboard new developers/users?
• You can start by describing a “user story” (see page 4 of reference model)

• M1: Outreach setup (WP1) needs preferred communication channels with clusters
• M4: Initial best practices landscaping results (WP2)
• D2.1: Initial collections of additional aspects to enhance software quality (WP2)
• D3.1: First collection of existing tools and services available in the Science clusters to assess, curate and improve software quality and FAIRness (WP3)
• D5.1 Landscape analysis of existing rewards and mechanisms for research software and training activities (WP5)

This will probably also be a questionnaire, and we’re happy if you give us / TF2 feedback on points we’ve forgotten here through your talk!

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

How do we organise our work, in practice

The next 5 meetings will be about pilot cases - fill in this sheet for booking a slot

4

We would ask you to have some slides (<20’ in total) for all following points - 2

• These points have been inspired by the TF2 reference model draft here (OwnCloud link)
• We will provide a google slides template if you want to use it�
• (4) Are there indicators and tools applicable to your pilot(s) that provide insight into technical quality?
• Do you or others in your community use them?

​

• (5) Describe the FAIR / Open aspects of the code in your pilot(s):
• See https://fair-software.eu/ for inspiration: are there a repository and a license, do you have a community registry/catalogue where the code is available, is it citeable, do you have a “good software” checklist
• How is the documentation maintained / by whom�
• (6) Does your software have a sustainability plan?
• This includes information on management, funding, contributors�
• (7) In your community, do you already have/know of training resources for developing/using software?
• WP5 has a list of resources here, we’ll contribute to that if anything is not listed already �
• (8) How are software developers rewarded in your community?

• M1: Outreach setup (WP1) needs preferred communication channels with clusters
• M4: Initial best practices landscaping results (WP2)
• D2.1: Initial collections of additional aspects to enhance software quality (WP2)
• D3.1: First collection of existing tools and services available in the Science clusters to assess, curate and improve software quality and FAIRness (WP3)
• D5.1 Landscape analysis of existing rewards and mechanisms for research software and training activities (WP5)

This will probably also be a questionnaire, and we’re happy if you give us / TF2 feedback on points we’ve forgotten here through your talk!

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

How to proceed

• We are starting with discussions of the pilots to gather information prior to the following phases

​

• You’re encouraged to join the meetings, especially the two Task Forces (Mondays, see indico)
• helps EVERSE gather voices from different clusters/researchers to build a useful framework for software excellence
• or if you can’t, you can ask us if you’d like a short summary of what’s going on at the start of each WP4 meeting (raise Zoom hands if you’d like that :) )

​

• We count on you for discussing the work ongoing in EVERSE with your cluster, and bring feedback back
• More structured discussions (e.g. WP4 coordinators going to speak at cluster meetings) will come later, this is more of a “getting to know each other’s work” stage
• OSCARS is a possible funding source to involve more people/pilots, we can write letters of support as WP4 coordinators

In the next few months we will have many discussions with the other WPs

5

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

Thank you!

​

Contact details for meeting announcements (ask us to subscribe):

everse-wp4@lists.certh.gr

​

WP leads:

Caterina Doglioni: caterina.doglioni@manchester.ac.uk

Guido Juckeland: g.Juckeland@hzdr.de

​

This project has received funding from the European Union’s Horizon Europe Programme under GA 101129744 — EVERSE — HORIZON-INFRA-2023-EOSC-01-02

WP4: Tasks

7

How

What

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland

WP4: Planned / Expected interactions with other WPs

8

WP4 intro - 24/04/2024 | C. Doglioni, G. Juckeland