EESSI roadmap 2026 for approval by SC #680
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -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)* | ||||||
|
Contributor
There was a problem hiding this comment. This should be fixed before merging. Can we just use support@eessi.io here? |
||||||
|
|
||||||
| The purpose of this roadmap is to focus our collective efforts on the specific goals we aim to achieve together this year. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| ## 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) | ||||||
|
Contributor
There was a problem hiding this comment. If we use "generation" here, we should clarify somewhere (not here) what we mean. |
||||||
| - 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 | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| - 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) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
Ideally we avoid use of "generation", since it's not clearly defined |
||||||
| ## 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) | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| ## User Experience & Integration | ||||||
| ### Direct User Interaction | ||||||
| - CLI: Prototype an EESSI Command Line Interface (CLI) to provide an interface beyondmodules | ||||||
|
Contributor
There was a problem hiding this comment. add pointer to https://github.com/EESSI/eessi-cli repo? |
||||||
| - Discovery: Create a dynamic software overview | ||||||
|
Contributor
There was a problem hiding this comment. add pointer to https://www.eessi.io/docs/available_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 | ||||||
|
Contributor
There was a problem hiding this comment. We should add the "release" concept here: monthly "releases" (needs better name, maybe "revision") with a changelog (and associated DOI) |
||||||
| ### 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 | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
Contributor
There was a problem hiding this comment. Why "focus on documentation/cleanup"? I think the topic we have in mind for next EESSI hackathon (during EuroHPC User Days 2026) is to focus on process for onboarding software into EESSI |
||||||
| - Feedback: Conduct an annual User Survey (aligned with annual EasyBuild survey) | ||||||
|
Contributor
There was a problem hiding this comment. I wouldn't aim to align it with annual EasyBuild user survey, it's already tricky to get that out in time (usually Dec/Jan, but not this year yet). I would more aim for May, so we can report on results in ISC BoF session (fingers crossed there), and use it as input to revise roadmap right before or after summer break. |
||||||
| - 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 | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this should say "Short-term roadmap for EESSI"?