EESSI roadmap 2026 for approval by SC

docs/roadmap.md

@@ -0,0 +1,70 @@
+# EESSI roadmap
+
+*(approved by the [EESSI Steering Committee](governance/steering_committee.md); last revised: 27 May 2026)*
+
+This roadmap outlines the goals we hope to accomplish for EESSI in the coming 6-12 months.
+
+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.
+
+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.
+
+Note that these goals are aspirational, we can *not* provide any guarantees that they will indeed be accomplished
+in the near future.
+
+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 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).
+
+
+## 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.
+
+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).
+
+
+## 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 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](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
+
+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](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/).

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,6 +83,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
@@ -156,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