From cc995d1a34f2ac02e3befe54502854592e76667b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20R=C3=B6blitz?= Date: Thu, 12 Feb 2026 21:28:18 +0100 Subject: [PATCH 1/8] EESSI roadmap 2026 for approval by SC --- docs/roadmap.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++ mkdocs.yml | 1 + 2 files changed, 52 insertions(+) create mode 100644 docs/roadmap.md diff --git a/docs/roadmap.md b/docs/roadmap.md new file mode 100644 index 0000000000..af8056e0d5 --- /dev/null +++ b/docs/roadmap.md @@ -0,0 +1,51 @@ +# Roadmap for EESSI + +*(approved by EESSI steering committee: dd-mm-yyyy; valid until: dd-mm-yyyy; to be revised by: dd-mm-yyyy; questions/suggestions: contact-sc@eessi.io)* + +The purpose of this roadmap is to focus our collective efforts on the specific goals we aim to achieve together this year. + +## Core Infrastructure, Operations & Policy +### Lifecycle & Governance Policies +- Generation Lifecycle: Define clear policies for "Active" vs. "Archived" generations (e.g., how long to add software to EESSI/2023.06) +- Development Policy: Establish lifetime policies for experimental installations on `dev.eessi.io` +- Cadence: Formalise the yearly release cycle (targeting pre-summer releases) +### Build System Modernisation +- Diversify Build Sites: Enhance reliability by spreading build operations +- Bot Modernisation: Upgrade infrastructure; implement tarball analysis to simplify ingestion and track differences +- Maintainer Support: Leverage the EESSI bot to assist EasyBuild maintainers +### Quality Assurance & Compliance +- Automated License Checks: Towards automatic mandatory license checks for EESSI/2026.06 +- Monitoring: Establish regular use of regression tests & status dashboard +- Performance: Assess performance of end-user applications +### Compatibility Layer +- Release EESSI/2026.06: next generation bundled with upcoming toolchains (update of Gentoo Prefix) +## Software Stack & Hardware Targets +### Hardware Enablement +- NVIDIA: Support for Blackwell GPUs +- AMD: Support for Zen5 and ROCm stack (AMD GPUs) +- ARM: Support for AWS Graviton 4+5 +### Software Portfolio +- AI/ML Focus: Extend GPU software (PyTorch, TensorFlow, AlphaFold) +- Volume Goal: Reach 1,000 unique software packages +- Toolchains: Integration of lfoss/2025b (EESSI/2025.06) and foss/2026* (EESSI/2026.06) +## User Experience & Integration +### Direct User Interaction +- CLI: Prototype an EESSI Command Line Interface (CLI) to provide an interface beyondmodules +- Discovery: Create a dynamic software overview +### Feedback & Transparency +- Software Wishlist: Implement mechanism (e.g., anonymous forms) for users to request software and trigger documentation PRs +- Work-in-Progress (WIP) View: Create dashboard/overview of WIP PRs, so users can see upcoming software +### Workflow Integration +- Tools: Prototype Nextflow & Spack integration +- CI/CD: Promote EESSI usage in CI/CD pipelines +- Scientific Compliance: Enhance FAIRness of software installations +## Community, Outreach & Sustainability +### Governance & Future +- Sustainability: Advance steps towards joining Linux Foundation (LF) & HPSF +### Community Engagement +- Events: Continue "Happy Hours", hackathons (focus on documentation/cleanup), and training +- Feedback: Conduct an annual User Survey (aligned with annual EasyBuild survey) +- Adoption: Track and map systems/sites that have adopted EESSI +### Dissemination & Marketing +- Content: Maintain a standard slide deck, elevator pitch, monthly blog/social updates +- Conference: FOSDEM, EuroHPC Summit, ISC, EUM, and EuroHPC User Days, etc diff --git a/mkdocs.yml b/mkdocs.yml index 08f6565a5b..3ea166c819 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -82,6 +82,7 @@ nav: - Contact info: contact.md - Training & events: training-events/index.md - Systems where EESSI is available: systems.md + - Roadmap: roadmap.md - Governance: - Overview: governance/index.md - Charter: governance/charter.md From 2a77f9f85a905489171af2f7e570977ef4544ffa Mon Sep 17 00:00:00 2001 From: Thomas Roeblitz Date: Thu, 19 Feb 2026 12:55:25 +0100 Subject: [PATCH 2/8] address some of the suggestions --- docs/roadmap.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index af8056e0d5..758cd24bf9 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -1,12 +1,13 @@ -# Roadmap for EESSI +# Short-term roadmap for EESSI -*(approved by EESSI steering committee: dd-mm-yyyy; valid until: dd-mm-yyyy; to be revised by: dd-mm-yyyy; questions/suggestions: contact-sc@eessi.io)* +*(approved by EESSI steering committee: 19-02-2026; valid until: 18-02-2027; to be revised by: 18-12-2026; questions/suggestions: support@eessi.io)* -The purpose of this roadmap is to focus our collective efforts on the specific goals we aim to achieve together this year. +The purpose of this roadmap is to focus the collective effort of the EESSI +community on the specific goals we aim to achieve together in the coming year. ## Core Infrastructure, Operations & Policy ### Lifecycle & Governance Policies -- Generation Lifecycle: Define clear policies for "Active" vs. "Archived" generations (e.g., how long to add software to EESSI/2023.06) +- Version Lifecycle: Define clear policies for "Active" vs. "Archived" versions (e.g., how long to add software to EESSI/2023.06) - Development Policy: Establish lifetime policies for experimental installations on `dev.eessi.io` - Cadence: Formalise the yearly release cycle (targeting pre-summer releases) ### Build System Modernisation @@ -14,11 +15,11 @@ The purpose of this roadmap is to focus our collective efforts on the specific g - Bot Modernisation: Upgrade infrastructure; implement tarball analysis to simplify ingestion and track differences - Maintainer Support: Leverage the EESSI bot to assist EasyBuild maintainers ### Quality Assurance & Compliance -- Automated License Checks: Towards automatic mandatory license checks for EESSI/2026.06 +- Automated License Checks: Towards automatic mandatory license checks for the next EESSI version (2026.x) - Monitoring: Establish regular use of regression tests & status dashboard - Performance: Assess performance of end-user applications ### Compatibility Layer -- Release EESSI/2026.06: next generation bundled with upcoming toolchains (update of Gentoo Prefix) +- Release the next EESSI version (2026.x): next version bundled with upcoming toolchains (update of Gentoo Prefix) ## Software Stack & Hardware Targets ### Hardware Enablement - NVIDIA: Support for Blackwell GPUs @@ -27,7 +28,7 @@ The purpose of this roadmap is to focus our collective efforts on the specific g ### Software Portfolio - AI/ML Focus: Extend GPU software (PyTorch, TensorFlow, AlphaFold) - Volume Goal: Reach 1,000 unique software packages -- Toolchains: Integration of lfoss/2025b (EESSI/2025.06) and foss/2026* (EESSI/2026.06) +- Toolchains: Integration of `lfoss/2025b` (in EESSI 2025.06) and `foss/2026*` (in EESSI 2026.x) toolchains ## User Experience & Integration ### Direct User Interaction - CLI: Prototype an EESSI Command Line Interface (CLI) to provide an interface beyondmodules @@ -44,7 +45,7 @@ The purpose of this roadmap is to focus our collective efforts on the specific g - Sustainability: Advance steps towards joining Linux Foundation (LF) & HPSF ### Community Engagement - Events: Continue "Happy Hours", hackathons (focus on documentation/cleanup), and training -- Feedback: Conduct an annual User Survey (aligned with annual EasyBuild survey) +- Feedback: Conduct an annual User Survey - Adoption: Track and map systems/sites that have adopted EESSI ### Dissemination & Marketing - Content: Maintain a standard slide deck, elevator pitch, monthly blog/social updates From 714944ee54106743d204a937192bf897e25c270f Mon Sep 17 00:00:00 2001 From: Thomas Roeblitz Date: Wed, 20 May 2026 21:41:04 +0200 Subject: [PATCH 3/8] rephrased roadmap to be goal-oriented versus a task list --- docs/roadmap.md | 87 ++++++++++++++++++++----------------------------- 1 file changed, 35 insertions(+), 52 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 758cd24bf9..21ea3e83ec 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -1,52 +1,35 @@ -# Short-term roadmap for EESSI - -*(approved by EESSI steering committee: 19-02-2026; valid until: 18-02-2027; to be revised by: 18-12-2026; questions/suggestions: support@eessi.io)* - -The purpose of this roadmap is to focus the collective effort of the EESSI -community on the specific goals we aim to achieve together in the coming year. - -## Core Infrastructure, Operations & Policy -### Lifecycle & Governance Policies -- Version Lifecycle: Define clear policies for "Active" vs. "Archived" versions (e.g., how long to add software to EESSI/2023.06) -- Development Policy: Establish lifetime policies for experimental installations on `dev.eessi.io` -- Cadence: Formalise the yearly release cycle (targeting pre-summer releases) -### Build System Modernisation -- Diversify Build Sites: Enhance reliability by spreading build operations -- Bot Modernisation: Upgrade infrastructure; implement tarball analysis to simplify ingestion and track differences -- Maintainer Support: Leverage the EESSI bot to assist EasyBuild maintainers -### Quality Assurance & Compliance -- Automated License Checks: Towards automatic mandatory license checks for the next EESSI version (2026.x) -- Monitoring: Establish regular use of regression tests & status dashboard -- Performance: Assess performance of end-user applications -### Compatibility Layer -- Release the next EESSI version (2026.x): next version bundled with upcoming toolchains (update of Gentoo Prefix) -## Software Stack & Hardware Targets -### Hardware Enablement -- NVIDIA: Support for Blackwell GPUs -- AMD: Support for Zen5 and ROCm stack (AMD GPUs) -- ARM: Support for AWS Graviton 4+5 -### Software Portfolio -- AI/ML Focus: Extend GPU software (PyTorch, TensorFlow, AlphaFold) -- Volume Goal: Reach 1,000 unique software packages -- Toolchains: Integration of `lfoss/2025b` (in EESSI 2025.06) and `foss/2026*` (in EESSI 2026.x) toolchains -## User Experience & Integration -### Direct User Interaction -- CLI: Prototype an EESSI Command Line Interface (CLI) to provide an interface beyondmodules -- Discovery: Create a dynamic software overview -### Feedback & Transparency -- Software Wishlist: Implement mechanism (e.g., anonymous forms) for users to request software and trigger documentation PRs -- Work-in-Progress (WIP) View: Create dashboard/overview of WIP PRs, so users can see upcoming software -### Workflow Integration -- Tools: Prototype Nextflow & Spack integration -- CI/CD: Promote EESSI usage in CI/CD pipelines -- Scientific Compliance: Enhance FAIRness of software installations -## Community, Outreach & Sustainability -### Governance & Future -- Sustainability: Advance steps towards joining Linux Foundation (LF) & HPSF -### Community Engagement -- Events: Continue "Happy Hours", hackathons (focus on documentation/cleanup), and training -- Feedback: Conduct an annual User Survey -- Adoption: Track and map systems/sites that have adopted EESSI -### Dissemination & Marketing -- Content: Maintain a standard slide deck, elevator pitch, monthly blog/social updates -- Conference: FOSDEM, EuroHPC Summit, ISC, EUM, and EuroHPC User Days, etc +# Short-Term Roadmap for EESSI + +*(approved by EESSI Steering Committee: 2026-05-xx; questions and suggestions: support@eessi.io)* + +The purpose of this roadmap is to focus the collective effort of the EESSI community on a set of priorities for the coming year. It describes areas where the community aims to make progress together and is reviewed regularly by the Steering Committee as priorities evolve. + +Most EESSI development currently happens within the scope of funded projects, but many of the goals outlined here benefit from broader community involvement and collaboration. If you are interested in contributing to one of these areas, or if you believe important topics are missing from the roadmap, please reach out to the EESSI community at support@eessi.io. + +# Core Infrastructure +EESSI will continue improving the reliability and scalability of its build and deployment infrastructure. Particular attention will be given to distributing operational responsibilities across sites and contributors, improving build and testing workflows, and strengthening integration with EasyBuild. + +# Hardware Enablement +EESSI will continue expanding support for emerging and widely requested hardware platforms, while growing the collection of GPU-enabled scientific and AI/ML software available through the project. + +Current areas of interest include newer generations of AWS Graviton systems and improved support for AMD GPU platforms through the ROCm software ecosystem. + +# Software Stack +EESSI will continue improving software quality, reproducibility, and transparency across the software stack, with particular attention to software licensing and compliance. + +Current areas of interest include automated license compliance workflows and improved visibility of software licensing information. + +# User Experience +EESSI aims to improve how users discover, access, and reuse software provided through the project, while strengthening support for reproducible research. + +Current areas of interest include development of a dedicated EESSI CLI and mechanisms for uniquely identifying and reusing software installations in support of FAIR research practices. + +# Community +The EESSI community plays a central role in the development and adoption of the project. EESSI will continue its efforts to engage with users, contributors, and partner organisations through community events, training activities, and participation in relevant conferences and workshops. + +Current areas of interest include community events and hackathons, shared outreach and training materials, and continued collaboration with related open source and HPC communities. + +# Sustainability +As EESSI continues to grow beyond the original project partners and is adopted by a broader range of sites and organisations, the project will continue strengthening the organisational structures needed to support long-term coordination, maintenance, and community ownership. + +Current areas of interest include continued evolution of the project's governance structures and collaboration with organisations such as the Linux Foundation and HPSF. From 32210778517838802121d3350c7fe2e50d730e6a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20R=C3=B6blitz?= Date: Wed, 20 May 2026 21:45:06 +0200 Subject: [PATCH 4/8] Apply suggestion from @boegel Co-authored-by: Kenneth Hoste --- mkdocs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mkdocs.yml b/mkdocs.yml index 3ea166c819..e517b3b0e1 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -82,7 +82,7 @@ nav: - Contact info: contact.md - Training & events: training-events/index.md - Systems where EESSI is available: systems.md - - Roadmap: roadmap.md + - Roadmap (short-term): roadmap/short-term.md - Governance: - Overview: governance/index.md - Charter: governance/charter.md From b60823f21d91a462bac269ed9cdce5d9411e84fd Mon Sep 17 00:00:00 2001 From: Kenneth Hoste Date: Wed, 27 May 2026 11:11:02 +0200 Subject: [PATCH 5/8] minor revision of roadmap, include links where useful --- docs/roadmap.md | 67 ++++++++++++++++++++++++++++++++++++------------- 1 file changed, 50 insertions(+), 17 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 21ea3e83ec..f7be27b276 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -1,35 +1,68 @@ -# Short-Term Roadmap for EESSI +# EESSI roadmap -*(approved by EESSI Steering Committee: 2026-05-xx; questions and suggestions: support@eessi.io)* +*(approved by the [EESSI Steering Committee](governance/steering_committee.md); last revised: 27 May 2026)* -The purpose of this roadmap is to focus the collective effort of the EESSI community on a set of priorities for the coming year. It describes areas where the community aims to make progress together and is reviewed regularly by the Steering Committee as priorities evolve. +This roadmap outlines the goals we hope to accomplish for EESSI in the coming 6-12 months. -Most EESSI development currently happens within the scope of funded projects, but many of the goals outlined here benefit from broader community involvement and collaboration. If you are interested in contributing to one of these areas, or if you believe important topics are missing from the roadmap, please reach out to the EESSI community at support@eessi.io. +Its main purpose is to focus the collective effort of the EESSI community on a set of priorities. +It describes areas where the community aims to make progress together, and is reviewed regularly by the Steering Committee +as priorities evolve and goals that were set have been accomplished. -# Core Infrastructure -EESSI will continue improving the reliability and scalability of its build and deployment infrastructure. Particular attention will be given to distributing operational responsibilities across sites and contributors, improving build and testing workflows, and strengthening integration with EasyBuild. +Most EESSI development currently happens within the scope of funded projects, but many of the goals outlined here benefit +from broader community involvement and collaboration. -# Hardware Enablement -EESSI will continue expanding support for emerging and widely requested hardware platforms, while growing the collection of GPU-enabled scientific and AI/ML software available through the project. +Note that these goals are aspirational, we can *not* provide any guarantees that they will indeed be accomplished +in the near future. -Current areas of interest include newer generations of AWS Graviton systems and improved support for AMD GPU platforms through the ROCm software ecosystem. +In case of questions related to this roadmap, or if you believe important topics are missing from the roadmap, +please reach out to the [EESSI Steering Committee](governance/steering_committee.md), or open a [support ticket](support.md). + + +## Core Infrastructure + +We will continue improving the reliability and scalability of the EESSI build and deployment infrastructure. + +Particular attention will be given to distributing operational responsibilities across sites and contributors, +improving build and testing workflows, and strengthening integration with [EasyBuild](https://easybuild.io). + + +## Hardware Enablement + +We will continue expanding support in EESSI for additional hardware platforms, +while growing the collection of available GPU-enabled scientific and AI/ML software. + +Current areas of interest include support newer generations of [AWS Graviton](https://aws.github.io/graviton/) CPUs (4 and 5), +and support for AMD GPUs through the [ROCm software ecosystem](https://www.amd.com/en/products/software/rocm.html). + + +## Software Stack -# Software Stack EESSI will continue improving software quality, reproducibility, and transparency across the software stack, with particular attention to software licensing and compliance. Current areas of interest include automated license compliance workflows and improved visibility of software licensing information. -# User Experience -EESSI aims to improve how users discover, access, and reuse software provided through the project, while strengthening support for reproducible research. +In additional, we expect to provide installations for over 1,000 unique (non-extension) software projects soon -- +see also [Overview of available software](available_software/index.md). + + +## User Experience + +EESSI aims to improve how users discover, access, and reuse provided software installations, while strengthening support for reproducible research. -Current areas of interest include development of a dedicated EESSI CLI and mechanisms for uniquely identifying and reusing software installations in support of FAIR research practices. +Current areas of interest include development of a user-friendly [command-line interface for EESSI](https://github.com/EESSI/eessi-cli), +and mechanisms for uniquely identifying and reusing software installations in support of [FAIR](https://www.nature.com/articles/sdata201618) research practices. -# Community -The EESSI community plays a central role in the development and adoption of the project. EESSI will continue its efforts to engage with users, contributors, and partner organisations through community events, training activities, and participation in relevant conferences and workshops. + +## Community + +The EESSI community plays a central role in the development and adoption of the project. EESSI will continue its efforts to engage with users, contributors, and partner organisations through community events, [training activities](training-events/index.md), and participation in relevant conferences and workshops. Current areas of interest include community events and hackathons, shared outreach and training materials, and continued collaboration with related open source and HPC communities. -# Sustainability + +## Sustainability + As EESSI continues to grow beyond the original project partners and is adopted by a broader range of sites and organisations, the project will continue strengthening the organisational structures needed to support long-term coordination, maintenance, and community ownership. -Current areas of interest include continued evolution of the project's governance structures and collaboration with organisations such as the Linux Foundation and HPSF. +Current areas of interest include continued evolution of the project's [governance](governance/index.md) structures and collaboration with organisations +such as the [Linux Foundation Europe](https://linuxfoundation.eu/) and the [High Performance Software Foundation (HPSF)](https://hpsf.io/). From a7654b9bb5f0bd27d5691675408e65d4eafe07d3 Mon Sep 17 00:00:00 2001 From: Kenneth Hoste Date: Wed, 27 May 2026 11:11:35 +0200 Subject: [PATCH 6/8] fix link to roadmap --- mkdocs.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index f387413ccd..53a27507eb 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -62,7 +62,7 @@ nav: # - Dashboard: test-suite/dashboard.md - Known issues and workarounds: - v2023.06: known_issues/eessi-2023.06.md - - Adding software to EESSI: + - Adding software to EESSI: - Overview: adding_software/overview.md - For contributors: - Contribution policy: adding_software/contribution_policy.md @@ -83,7 +83,7 @@ nav: - Contact info: contact.md - Training & events: training-events/index.md - Systems where EESSI is available: systems.md - - Roadmap (short-term): roadmap/short-term.md + - Roadmap: roadmap.md - Governance: - Overview: governance/index.md - Charter: governance/charter.md @@ -157,12 +157,12 @@ plugins: - inject_ld_json # link to any Markdown heading - autorefs - # api automatics documentation + # api automatics documentation - mkdocstrings: default_handler: python handlers: python: - paths: [test-suite/test-suite] + paths: [test-suite/test-suite] options: docstring_style: sphinx docstring_section_style: spacy From 95f5ba9274650a136ca167ba373f19c80f87462a Mon Sep 17 00:00:00 2001 From: Kenneth Hoste Date: Thu, 28 May 2026 13:45:09 +0200 Subject: [PATCH 7/8] fix typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Bob Dröge --- docs/roadmap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index f7be27b276..87b67746e1 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -31,7 +31,7 @@ improving build and testing workflows, and strengthening integration with [EasyB We will continue expanding support in EESSI for additional hardware platforms, while growing the collection of available GPU-enabled scientific and AI/ML software. -Current areas of interest include support newer generations of [AWS Graviton](https://aws.github.io/graviton/) CPUs (4 and 5), +Current areas of interest include support for newer generations of [AWS Graviton](https://aws.github.io/graviton/) CPUs (4 and 5), and support for AMD GPUs through the [ROCm software ecosystem](https://www.amd.com/en/products/software/rocm.html). @@ -41,7 +41,7 @@ EESSI will continue improving software quality, reproducibility, and transparenc Current areas of interest include automated license compliance workflows and improved visibility of software licensing information. -In additional, we expect to provide installations for over 1,000 unique (non-extension) software projects soon -- +In addition, we expect to provide installations for over 1,000 unique (non-extension) software projects soon -- see also [Overview of available software](available_software/index.md). From c25847888ea4f99f1ff2960c104c2a188fe448e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= Date: Thu, 28 May 2026 14:17:41 +0200 Subject: [PATCH 8/8] add sentence about yearly EESSI releases Co-authored-by: Kenneth Hoste --- docs/roadmap.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/roadmap.md b/docs/roadmap.md index 87b67746e1..f69cff46e6 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -41,6 +41,8 @@ EESSI will continue improving software quality, reproducibility, and transparenc Current areas of interest include automated license compliance workflows and improved visibility of software licensing information. +We intend to create a new EESSI version every (calendar) year, by rebuilding the EESSI compatibility layer and gradually installing software on top of it in the software layer, using new compiler toolchains. + In addition, we expect to provide installations for over 1,000 unique (non-extension) software projects soon -- see also [Overview of available software](available_software/index.md).