From ceb566bc25051b0ad8a02a3d465485fa9095b31f Mon Sep 17 00:00:00 2001 From: Christian Heissenberger Date: Tue, 17 Feb 2026 18:21:41 +0100 Subject: [PATCH 1/4] feat(hugo): migrate static HTML site to Hugo content/layout structure - add Hugo layouts (baseof, single, index) - migrate pages from static/*.html to content/*.md - preserve existing styling/scripts via front matter includes - enable raw HTML rendering for migrated content - fix UTF-8 character encoding issues in migrated files - move original HTML sources to legacy-html/ - update Hugo config (uglyURLs + Goldmark unsafe rendering) --- config.toml | 7 + content/_index.md | 825 +++++ content/about-us.md | 646 ++++ content/articles.md | 286 ++ content/blog-details.md | 359 ++ content/docs.md | 267 ++ content/faq.md | 1087 ++++++ content/how_to_contribute.md | 617 ++++ content/news.md | 430 +++ content/press_releases.md | 319 ++ content/reference-implementation.md | 390 +++ content/townhalls.md | 254 ++ content/training-modules.md | 1259 +++++++ layouts/_default/baseof.html | 53 + layouts/_default/single.html | 7 + layouts/index.html | 7 + {static => legacy-html}/about-us.html | 1502 ++++----- {static => legacy-html}/articles.html | 828 ++--- {static => legacy-html}/blog-details.html | 884 ++--- {static => legacy-html}/docs.html | 744 ++--- {static => legacy-html}/faq.html | 2468 +++++++------- .../how_to_contribute.html | 1444 ++++---- {static => legacy-html}/index.html | 1826 +++++----- {static => legacy-html}/news.html | 1120 +++---- {static => legacy-html}/press_releases.html | 896 ++--- .../reference-implementation.html | 996 +++--- {static => legacy-html}/townhalls.html | 764 ++--- {static => legacy-html}/training-modules.html | 2942 ++++++++--------- 28 files changed, 15020 insertions(+), 8207 deletions(-) create mode 100644 content/_index.md create mode 100644 content/about-us.md create mode 100644 content/articles.md create mode 100644 content/blog-details.md create mode 100644 content/docs.md create mode 100644 content/faq.md create mode 100644 content/how_to_contribute.md create mode 100644 content/news.md create mode 100644 content/press_releases.md create mode 100644 content/reference-implementation.md create mode 100644 content/townhalls.md create mode 100644 content/training-modules.md create mode 100644 layouts/_default/baseof.html create mode 100644 layouts/_default/single.html create mode 100644 layouts/index.html rename {static => legacy-html}/about-us.html (97%) rename {static => legacy-html}/articles.html (97%) rename {static => legacy-html}/blog-details.html (97%) rename {static => legacy-html}/docs.html (97%) rename {static => legacy-html}/faq.html (97%) rename {static => legacy-html}/how_to_contribute.html (97%) rename {static => legacy-html}/index.html (97%) rename {static => legacy-html}/news.html (97%) rename {static => legacy-html}/press_releases.html (97%) rename {static => legacy-html}/reference-implementation.html (97%) rename {static => legacy-html}/townhalls.html (97%) rename {static => legacy-html}/training-modules.html (97%) diff --git a/config.toml b/config.toml index 9e34502..0c9000a 100644 --- a/config.toml +++ b/config.toml @@ -4,7 +4,9 @@ title = "Eclipse S-CORE" #theme = "hugo-solstice-theme" metaDataFormat = "yaml" disableKinds = [] + enableRobotsTXT = true +uglyURLs = true pluralizeListTitles = false [Params] @@ -88,3 +90,8 @@ pluralizeListTitles = false # or to define your own menu links. # [[menu.main]] + +[markup] + [markup.goldmark] + [markup.goldmark.renderer] + unsafe = true diff --git a/content/_index.md b/content/_index.md new file mode 100644 index 0000000..fa824f3 --- /dev/null +++ b/content/_index.md @@ -0,0 +1,825 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/owl.carousel.min.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/loading.css" + - "css/news.css" + - "css/style.css" + - "css/contributor-slider.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/owl.carousel.min.js" + - "js/panzoom.min.js" + - "js/zoom.js" + - "js/news.js" + - "js/contributor-slider.js" + - "js/loading.js" +--- + +
+
+
+
+ +
+
+
+
+

+ From Proprietary + To Open Source +

+

+ The industry has long tackled software challenges + independently – often duplicating efforts and building + closed, incompatible systems.

+ S-CORE changes this by uniting OEMs, suppliers and + developers around a common SW-platform. The goal of S-CORE + is to reduce complexity, promote re-use, gain speed & + enable scalable innovation. +

+
+

+ Join our global community building a common, + safety-critical runtime foundation for automotive + innovation. +

+
+ Explore the projects + Get Involved + Visit Our Github +
+
+
+
+ 3D illustration of a futuristic car with floating cubes +
+
+
+
+
+
+
+
+
+
+

Latest News:
S-CORE Release v0.5 - beta is available

+
+ +
+
+
+
+ +
+
Release Notes
+

+ Find out more about the release and all components integrated and available. +
+ + + Release Notes + + +

+ +
+
+ +
+
+
+ +
+
How to get started
+

+ Follow this Guide to start you development with Eclipse S-CORE today! +
+ + + How to get started + +

+
+
+ +
+
+
+ +
+
Get in touch
+

+ Get in touch with us on and discuss with the developers on Slack or via E-mail! +
+ + + Get in touch + + +

+
+
+ + +
+ +
+
+
+
+
+
+
+

Latest News & Events

+ + Discover more News/Events + + +
+ +
+
+
+ +
+
+ +
+
+

Coming soon: Eclipse S-CORE 0.5

+

+ The automotive industry’s first open, safety-ready software stack is almost here.
+ Eclipse S-CORE brings the community one step closer to a shared foundation for software-defined vehicles. +

+

Eclipse S-CORE:
+ Open by Choice. Safe by Design.

+
+
+ Learn More +
+ +
+ +
+
+ +
+
+ +
+
+

Nov 12, 2025

+

+ Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Eclipse Community Meetup, Japan/ Yokohama

+

+ Introduction and update about recent S-CORE developments. +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ + +
+
+
+
+
+
+
+
+

S-CORE In A Nutshell

+
+
+

Together...

+

S-CORE began in 2024 with five initial members: + Accenture, BMW, ETAS, Mercedes-Benz, and Qorix – “the coalition of the willing”.
+ Since then, both active participation and global interest have grown significantly.

+
+
+
+
+ +
+

OEMS

+
+
+ +
+
+
+ +
+

Tiers

+
+
+ +
+
+
+ +
+

SW-Supplier

+
+
+ +
+
+
+ +
+

Service Provider

+
+
+
+ +

...we´re shaping an open-source and code-based SW-platform...

+

S-CORE solves the requirements of a future SDV with a collaborative, open, and modular approach. + Developed by and for the industry, it delivers a robust core architecture that reduces integration effort, + enhances safety, and accelerates development.
+ Rather than fostering competition through proprietary, + stacks, S-CORE enables collaboration through standardisation.

+ +
+
+
+
+ +
+
+
+ +
+
+
+ +
+

Open Source

+
+
+ +
+
+
+ +
+

Code Based

+
+
+
+ +

...for "dynamic core" components with strict requirements of a future SDV.

+

+ S-CORE bridges the OS–application gap and is being developed as a modular, + standards-oriented middleware. The goal: enable predictable, safe, and reusable execution + environments across diverse hardware and ECU types – without prescribing a fixed implementation.
+ + Its architecture is designed for safety-critical contexts – especially ADAS, Body, and Chassis – and supports compliance with ISO 26262 and ISO/SAE 21434. +

+
+
+
+
+ +
+
+
+ +
+
+
+ +
+

Quality (ASPICE)

+
+
+ +
+
+
+ +
+

Safety (ISO 26262)

+
+
+ +
+
+
+ +
+

Security (ISO 21434)

+
+
+
+
+
+
+
+
+
+
+
+
+

+ The focus of S-CORE are safety-critical in-car components +

+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+

+ S-CORE aims to build-up all SW-platform layers below the + application layer and above the board support package of the + SoC. +

+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+

+ What are the deliverables of S-CORE? +

+

+ Besides describing the SW-platform, S-CORE provides a huge + load of complementary deliverables. +

+
+
+
+
+
+ +
+
+
+
+
+
+ +
+
+
+
+
+

Why is S-CORE Needed

+
+
+ +
+
+
+
+ +
+
Common Stack & Collaboration
+

+ A common full-stack software runtime addressing shared + industry problems through joint solutions. +

+
+
+ +
+
+
+ +
+
Speed
+

+ Accelerates development by working in open source with + code-centric, iterative methods. +

+
+
+ +
+
+
+ +
+
Abstraction & Extensibility
+

+ Decouples HW and SW with flexible layers and enables + project-specific extensions of the stack. +

+
+
+ +
+
+
+ +
+
Quality & Efficiency
+

+ A lean, no-frills solution using modern languages, + readable specs, and safe open source processes. +

+
+
+
+
+
+
+ +
+
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+
+
+
+ Member 1 +
+
+
+
+ Member 2 +
+
+
+
+ Member 3 +
+
+
+
+ Member 4 +
+
+
+
+ Member 5 +
+
+
+
+ Member 6 +
+
+
+
+ Member 7 +
+
+
+
+ Member 8 +
+
+
+
+ Member 9 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+ + +
+
+
+
+
+ + + +
+ +
+
+
diff --git a/content/about-us.md b/content/about-us.md new file mode 100644 index 0000000..213f0fd --- /dev/null +++ b/content/about-us.md @@ -0,0 +1,646 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/owl.carousel.min.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/about-us.css" + - "css/contributor-slider.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/owl.carousel.min.js" + - "js/panzoom.min.js" + - "js/zoom.js" + - "js/about-us.js" + - "js/contributor-slider.js" + - "js/loading.js" +--- + +
+ +
+
+
+

About Us

+
+
+ +
+
+
+
+ +
+
+
+
+
+
+

Who We Are

+

+ We’re a collaborative and ever-growing community of automotive + experts, technology partners, developers, and innovators + united under the Eclipse Foundation. Together, we’re shaping + the future of automotive software by building open, safe, and + scalable solutions. +

+ +
+
+
+ Vision Icon +
+
+

Our Vision

+

+ “Build the best automotive runtime solution – ONLY + ONCE!” +

+
+
+ +
+
+ Vision Icon +
+
+

Our Mission

+

+ Unite the automotive software community around
+ ONE OPEN-SOURCE CORE” +
+
+ +

+

+ Reuse “Stop + reinventing the wheel” +

+

+ Reduce + “…complexity, effort,…” +

+

+ Evolve “Build on a + future-proof foundation” +

+
+
+
+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+
+
+
+ Member 2 +
+
+
+
+ Member 3 +
+
+
+
+ Member 4 +
+
+
+
+ Member 5 +
+
+
+
+ Member 6 +
+
+
+
+ Member 1 +
+
+
+
+ Member 7 +
+
+
+
+ Member 8 +
+
+
+
+ Member 9 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+ + +
+
+
+
+ +
+
+
+

S-CORE Community Structure

+

+ S-CORE brings together members, technical leads, and specialized + teams to define and manage modules, propose requirements, and + ensure the platform evolves with clarity and purpose. +

+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Steering Committees

+

+ Every core member can name a project lead. Project leads are + representatives of their entities, and jointly they´re steering + the project. Because of the project´s size, an additional role + “technical leads” was introduced in S-Core. Each project lead can + nominate one technical lead to support in operational topics like + project planning. In order to run the project, there are two major + committees: +

+
+
+
+
+

+ Technical Lead Circle +

+
+ +
+

+ The Technical Steering Committee (TSC) is responsible for the + overall technical direction of the project. It ensures that + the project remains aligned with its goals and objectives, and + it provides guidance on technical decisions. +

+
+
+

+ Project Lead Circle +

+
+ +
+

+ The Project Management Committee (PMC) is responsible for the + day-to-day management of the project. It oversees the + project's progress, manages resources, and ensures that + deadlines are met. +

+
+
+
+
+
+ +
+
+
+

Communities

+

+ Every S-CORE community has its focus topic, and every S-CORE + member is free to join, discuss and to shape the outcome. +

+
+
+
+ Software Architecture +

Software Architecture

+

+ + In this community, the overall software architecture of our + stack is planned. Join here to get the recent information about + next features for S-CORE. . +

+
+
+ Software Development Process +

Software Development Process

+

+ Due to our goal to deliver a stack which is safety certifiable, + we need well defined software development processes. This + community is continuously designing & improving our processes. +

+
+
+ Infrastructure +

Infrastructure

+

+ To enable a fast and reliable development, this community is + setting up the build infrastructure, the tooling, process + enabling, the CI/CD pipelines, and more… +

+
+
+ Testing +

Testing

+

+ To meet our quality goals, S-CORE needs to be tested – In this + community, experienced test managers and testers are ensuring + exactly this. +

+
+
+ Marketing & Communication +

Marketing & Communication

+

+ S-CORE can only be successful, when more and more members are + joining! – This community ensures, that the great results + -provided by S-CORE teams- are communicated to the automotive + community. +

+
+
+
+
+ +
+
+
+

+ Community Voices – What Our Members Say +

+

+ Community Voices captures insights and experiences from our + members, highlighting their role in shaping the platform and + driving innovation within the S-CORE ecosystem. Their feedback + reflects the impact, collaboration, and shared vision that fuel + our open-source journey. +

+
+
+
+
+
+
+
+
+ +
+
+
Mike Milinkovich
+
Executive Director of the Eclipse Foundation
+
+
+ +
+
+

+ With S-CORE, we’re providing developers with a reliable, safety-grade runtime environment that allows the industry to focus on innovation while reducing duplication of effort. This project offers the entire sector a jumpstart in building the custom solutions that will define the future of mobility +

+
+
+ +
+
+
+
+ +
+
+
Anton Krivoborodov
+
Technical Project Lead - BMW
+
+
+
+
+

+ With S-Core, we can shape the future of the Safe-POSIX platform with the support of a strong open-source community. +

+
+
+ +
+
+
+
+ +
+
+
Markus Schupfner
+
CEO Qorix
+
+
+
+
+

+ S-CORE is more than a project – it’s the foundation of an open, collaborative future for automotive software. As a founding contributor and distributor, Qorix is proud to shape a platform that turns shared challenges into shared progress. +

+
+
+ +
+
+
+
+ +
+
+
Sven Kappel
+
Head of ETAS.NEXT
+
+
+
+
+

+ At ETAS, we believe in the transformative potential of open collaboration in driving software innovation. + As a founding member of Eclipse S-CORE, we are committed to shaping a robust platform that fosters seamless integration, + sustainable development processes, and cutting-edge solutions empowering tomorrow's automotive software +

+
+
+ +
+
+
+
+ +
+
+
Lars Bauhofer
+
Product Program Manager - Qorix
+
+
+
+
+

+ S-CORE makes collaboration tangible. From architecture workshops to release planning – we’re actively building the stack, aligning teams, and turning code into common ground. +

+
+
+
+
+
+
+ +
+
+
Dr. Nico Hartmann
+
CTO - Qorix
+
+
+
+
+

+ Contributing to S-CORE means contributing to what matters: deterministic execution, safety by design, and reusable infrastructure. We bring the middleware expertise – and we’re here to make it usable at scale. +

+
+
+
+ + +
+
+
+
+ + +
+
+ +
diff --git a/content/articles.md b/content/articles.md new file mode 100644 index 0000000..52e854b --- /dev/null +++ b/content/articles.md @@ -0,0 +1,286 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/news.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/loading.js" +--- + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+
+
+
+ +
+
+
+ + + + Nov 6th, 2025 +
+

+ Eclipse S-CORE 0.5 – What’s inside the first public release. +

+

+ Source: Eclipse SDV WG Linkedin

+

+

+ The first version of Eclipse S-CORE (Safe Open Vehicle Core) lays the groundwork for open, safety-ready automotive software.
+ +

+ + Read More and Discuss + +
+
+
+
+ +
+
+
+ + + + Sept 30, 2025 +
+

+ Eclipse S-CORE: A new approach to building automotive software together +

+

+ by Valerie Hasler and Memsud Godinjak +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+
+ + +
+
+ +
diff --git a/content/blog-details.md b/content/blog-details.md new file mode 100644 index 0000000..06f1d2e --- /dev/null +++ b/content/blog-details.md @@ -0,0 +1,359 @@ +--- +title: "S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/owl.carousel.min.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/news.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/owl.carousel.min.js" + - "js/news.js" + - "js/loading.js" +--- + +
+ +
+
+
+

+ Unlocking Innovation: The Power of Open Source Software +

+
+
+ +
+
+
+
+ +
+
+
+
+
+ + + + 14 Feb, 2024 +
+ +

+ One of the greatest advantages of open source software is its + community-driven nature, which brings together developers from + across the world. These contributors often come from vastly + different backgrounds, cultures, and levels of experience — yet + they unite around a shared goal: building better software. This + global collaboration leads to diverse perspectives, creative + problem-solving, and faster identification of bugs or security + flaws. Since the code is open and accessible, anyone can + contribute, whether it’s by writing new features, improving + documentation, or testing for issues. This open process allows the + software to evolve rapidly, often outpacing traditional + closed-source development. With thousands of eyes reviewing and + refining the code, quality tends to increase over time. The sense + of shared ownership among contributors also builds trust and + commitment within the community. Unlike proprietary systems, where + innovation is limited to internal teams, open source benefits from + decentralized innovation at scale. It’s this collaborative spirit + that turns open source from just code into a movement — one that’s + shaping the future of technology. +

+
+ +
+
+

Recommended

+
+
+
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+ +
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+ + +
+
+
+
+
+ + +
+
+ +
diff --git a/content/docs.md b/content/docs.md new file mode 100644 index 0000000..abfdf58 --- /dev/null +++ b/content/docs.md @@ -0,0 +1,267 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/docs.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/panzoom.min.js" + - "js/zoom.js" + - "js/loading.js" +--- + +
+ +
+
+
+

Docs

+
+
+ +
+
+
+
+ +
+
+
+
+

Eclipse S-Core Building Blocks

+ +
+
+ + S-CORE v0.5 module +
+
+ + + S-CORE v1.0 module +
+
+
+ +
+
+

+ This section provides a schematic overview of the technical building blocks that form the foundation of our platform. + Here, you’ll find a clear differentiation between S-CORE modules available in version 0.5 and those planned for version 1.0.
+

+
+
+ +
+
+
+
+
+
+ +
+
+
+

S-Core Project Roadmap

+
+
+
+

+ Get athe development and release timeline of Eclipse S-CORE. It shows the key phases that shape the platform’s evolution—starting from early development to achieving maturity and stability. + Gain an understanding of how each phase contributes to delivering a scalable and reliable platform. +

+
+
+ +
+
+
+
+
+
+ +
+
+
+

Build & Documentation Toolchain

+

+ The build system uses Bazel to automate workflows like repository + cloning, software builds, documentation generation, testing, and + more. Documentation is managed with Sphinx and sphinx-needs, while + diagrams are created using PlantUML and draw.io. Supported + languages include C++ and Rust, with testing handled by + gtest/gmock. +

+
+
+
+
+
+ +
+
+

+ Check out our GitHub Project + + +
+
+
+ + +
+
+ +
diff --git a/content/faq.md b/content/faq.md new file mode 100644 index 0000000..fb1fe00 --- /dev/null +++ b/content/faq.md @@ -0,0 +1,1087 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/swiper-bundle.min.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/campus.css" + - "css/about-us.css" +external_styles: + - "https://cdn.jsdelivr.net/npm/@glidejs/glide/dist/css/glide.core.min.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/swiper-bundle.min.js" + - "js/swiper.js" + - "js/loading.js" +--- + +
+ +
+
+
+

Frequently Asked Questions

+
+
+ +
+
+
+
+ +
+ + +
+
+
+
+ +

+ Get quick answers to the most common questions about S-CORE. Whether you're just starting or deep into development, + our FAQs cover everything from training schedules to platform usage — helping you find what you need without the hassle. +

+ + +
+
+ + + +
+ +
+
+ + + +
    + + + +
+ + +
+ +
+
+
+
+ +
+

+ +

+
+
+ The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. +
+
+
+ + +
+

+ +

+
+
+ Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules +
+
+
+ + +
+

+ +

+
+
+ A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors +
+
+
+ +
+

+ +

+
+
+ Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . +
+
+
+
+ +
+ +
+

+ +

+
+
+ Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. +
+
+
+ +
+

+ +

+
+
+ S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . +
+
+
+ +
+

+ +

+
+
+ Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository +
+
+
+ +
+

+ +

+
+
+ Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . +
+
+
+
+
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. +
+
+
+
+
+
+

+ +

+
+
+ S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. +
+
+
+
+
+
+

+ +

+
+
+ Change Request types include Feature, Feature Modification, Component, and Component Modification . +
+
+
+
+ +
+
+

+ +

+
+
+ Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . +
+
+
+
+ + +
+
+

+ +

+
+
+ GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . +
+
+
+
+ + +
+
+

+ +

+
+
+ Technical Leads manage the platform development, control multiple modules, and handle escalations . +
+
+
+
+ + +
+
+

+ +

+
+
+ Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . +
+
+
+
+ + +
+
+

+ +

+
+
+ Features and components are integrated into the platform using change requests and verified through tests . +
+
+
+
+ + +
+
+

+ +

+
+
+ Problems are reported through GitHub Issues, including documentation and resolution planning. +
+
+
+
+ +
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests +
+
+
+
+ +
+
+

+ +

+
+
+ Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination +
+
+
+
+ + +
+
+

+ +

+
+
+ Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git +
+
+
+
+ + +
+
+

+ +

+
+
+ Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Contribution Request Guideline details the process of submitting new features and tools . +
+
+
+
+ + +
+
+

+ +

+
+
+ Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. +
+
+
+
+ +
+
+
+
+
+
+


+
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
diff --git a/content/how_to_contribute.md b/content/how_to_contribute.md new file mode 100644 index 0000000..354f3e7 --- /dev/null +++ b/content/how_to_contribute.md @@ -0,0 +1,617 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/owl.carousel.min.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/about-us.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/owl.carousel.min.js" + - "js/panzoom.min.js" + - "js/zoom.js" + - "js/about-us.js" + - "js/loading.js" +--- + +
+ +
+
+
+

How To Contribute

+
+
+ +
+
+
+
+ +
+
+
+
+
+
+

Who We Are

+

+ We’re a collaborative and ever-growing community of automotive + experts, technology partners, developers, and innovators + united under the Eclipse Foundation. Together, we’re shaping + the future of automotive software by building open, safe, and + scalable solutions. +

+ +
+
+
+ Vision Icon +
+
+

Our Vision

+

+ “Build the best automotive runtime solution – ONLY + ONCE!” +

+
+
+ +
+
+ Vision Icon +
+
+

Our Mission

+

+ Unite the automotive software community around ONE + OPEN-SOURCE CORE” +

+

+ Reuse “Stop + reinventing the wheel” +

+

+ Reduce + “…complexity, effort,…” +

+

+ Evolve “Build on a + future-proof foundation” +

+
+
+
+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+
+
+ +
+
+
+

S-CORE Community Structure

+

+ S-CORE brings together members, technical leads, and specialized + teams to define and manage modules, propose requirements, and + ensure the platform evolves with clarity and purpose. +

+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Steering Committees

+

+ Every core member can name a project lead. Project leads are + representatives of their entities, and jointly they´re steering + the project. Because of the project´s size, an additional role + “technical leads” was introduced in S-Core. Each project lead can + nominate one technical lead to support in operational topics like + project planning. In order to run the project, there are two major + committees: +

+
+
+
+
+

+ Technical Lead Circle +

+
+ +
+

+ The Technical Steering Committee (TSC) is responsible for the + overall technical direction of the project. It ensures that + the project remains aligned with its goals and objectives, and + it provides guidance on technical decisions. +

+
+
+

+ Project Lead Circle +

+
+ +
+

+ The Project Management Committee (PMC) is responsible for the + day-to-day management of the project. It oversees the + project's progress, manages resources, and ensures that + deadlines are met. +

+
+
+
+
+
+ +
+
+
+

Communities

+

+ Every S-CORE community has its focus topic, and every S-CORE + member is free to join, discuss and to shape the outcome. +

+
+
+
+ Software Architecture +

Software Architecture

+

+ In this community, the overall software architecture of our + stack is planned. Join here to get the recent information about + next features for S-CORE. . +

+
+
+ Software Development Process +

Software Development Process

+

+ Due to our goal to deliver a stack which is safety certifiable, + we need well defined software development processes. This + community is continuously designing & improving our processes. +

+
+
+ Infrastructure +

Infrastructure

+

+ To enable a fast and reliable development, this community is + setting up the build infrastructure, the tooling, process + enabling, the CI/CD pipelines, and more… +

+
+
+ Testing +

Testing

+

+ To meet our quality goals, S-CORE needs to be tested – In this + community, experienced test managers and testers are ensuring + exactly this. +

+
+
+ Marketing & Communication +

Marketing & Communication

+

+ S-CORE can only be successful, when more and more members are + joining! – This community ensures, that the great results + -provided by S-CORE teams- are communicated to the automotive + community. +

+
+
+
+
+ +
+
+
+

+ Community Voices – What Our Members Say +

+

+ Community Voices captures insights and experiences from our + members, highlighting their role in shaping the platform and + driving innovation within the S-CORE ecosystem. Their feedback + reflects the impact, collaboration, and shared vision that fuel + our open-source journey. +

+
+
+
+
+
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+
+ + +
+
+
+
+ + +
+
+ +
diff --git a/content/news.md b/content/news.md new file mode 100644 index 0000000..4cc21b0 --- /dev/null +++ b/content/news.md @@ -0,0 +1,430 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/news.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/loading.js" +--- + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+ +
+
+
+ +
+
Upcoming Conferences
+ + + +
+ +
+ +
+ +
+
+ + + + 5 Feb, 2026 +
+

+ SIA 2026 | Future Proofing SDV Study Day,
Paris, France +

+

+ Presenter: Björn Reistel (ETAS)
+ Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" +

+ + Read More + +
+
+ + + +
+ +
+ +
+ +
+
+ + + + 21-23 Apr, 2026 +
+

+ OCX 2026 | Open Community Exceprience,
Brussels, Belgium +

+

+ Presenter: tbd.
+ Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" +

+ + Read More + +
+
+ +
+ + + + + + +
+
+ + Show More + +
+
+
+
+ + +
+
Previous Conferences
+ + + +
+
+
+
+
+
+ + +
+
+ +
diff --git a/content/press_releases.md b/content/press_releases.md new file mode 100644 index 0000000..43c2164 --- /dev/null +++ b/content/press_releases.md @@ -0,0 +1,319 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/news.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/loading.js" +--- + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+ +
+
+
+
+ + + + Nov 12, 2025 +
+ +

+ Source: Eclipse S-CORE Project +


+ +

+ Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles +


+

+ November 12th, 2025 — The Eclipse Safe Open Vehicle Core (S-CORE) project today announced the active participation of Qualcomm Technologies, Inc. as a new member of its open-source community. + By leveraging Qualcomm Technologies Inc.’s Snapdragon® Digital Chassis™ solutions, S-CORE will run seamlessly on Qualcomm Technologies’ established high-performance hardware for future software-defined vehicles (SDVs). This collaboration further expands the reach of the S-CORE community, as a significant share of today’s safety-critical and secure automotive systems already rely on Qualcomm Technologies’ hardware.

+ + Hosted by the Eclipse Foundation under the purview of the Eclipse Software Defined Vehicle Working Group, Eclipse S-CORE, is an open-source initiative delivering a shared, safety-aligned middleware platform for high-performance automotive compute platforms. Developed by leading automotive and software companies — including Accenture GmbH, Aumovio SE, BMW Group, Elektrobit Automotive GmbH, ETAS GmbH, Mercedes-Benz Tech Innovation GmbH, Qualcomm Technologies, Inc., and Qorix GmbH — S-CORE provides a scalable, modular, and interoperable foundation for safety-critical components, reducing duplication, accelerating SDV development, and promoting industry-wide standardization.

+ + “Open collaboration is at the heart of solving the growing complexity of modern vehicle software,” said Mike Milinkovich, executive director of the Eclipse Foundation. “Through Eclipse S-CORE, we’re building a fully open, safety-aligned middleware foundation that helps automakers and suppliers focus on innovation instead of duplication. We’re delighted to welcome Qualcomm Technologies to this global community and the important work ahead.”

+ + “Qualcomm Technologies’ engagement with S-CORE represents a pivotal step toward democratizing access to high-performance automotive middleware,” said Laxmi Rayapudi, VP, Product Management, Qualcomm Technologies, Inc. “By aligning our Snapdragon Digital Chassis solutions with the S-CORE community, we’re empowering automakers and Tier-1 suppliers to innovate faster and deliver intelligent, connected, and safer vehicles.”

+ + The S-CORE project aims to establish a vendor-neutral, open-source software stack that addresses the increasing complexity of software-defined vehicles. Qualcomm Technologies’ contribution will streamline development workflows, reduce time-to-market, and foster a vibrant ecosystem of automotive software innovation — reinforcing the community’s shared vision to enable AI-driven, software-centric mobility at global scale.

+ + Snapdragon and Digital Chassis are trademarks or registered trademarks of Qualcomm Incorporated.
+ Snapdragon Digital Chassis is a product of Qualcomm Technologies, Inc. and/or its subsidiaries.


+

+ +

Eclipse S-CORE: "Open by Choice. Safe by Design."
+
+
+ +
+
+ +
+
+
+ + + + Jun 12, 2025 +
+

+ The Eclipse Foundation Launches the S-CORE Project: The Automotive Industry's First Open Source Core Stack for Software-Defined Vehicles +

+

+ Source: Eclipse Foundation Canada +

+ + Read More + +
+
+
+
+ +
+
+
+ + + + 18 Jun, 2025 +
+

+ QNX to Serve as Foundational Operating System for Eclipse Safe Open Vehicle Core (S-CORE) Project +

+

+ Source: BlackBerry Media Relations +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+ + +
+
+ +
diff --git a/content/reference-implementation.md b/content/reference-implementation.md new file mode 100644 index 0000000..e150d86 --- /dev/null +++ b/content/reference-implementation.md @@ -0,0 +1,390 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/swiper-bundle.min.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/campus.css" + - "css/about-us.css" +external_styles: + - "https://cdn.jsdelivr.net/npm/@glidejs/glide/dist/css/glide.core.min.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/campus.js" + - "js/loading.js" +--- + +
+ +
+
+
+

Join us

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+

+ How to get in contact with S-CORE +

+

+ If you want to get into contact with S-CORE, these are your primary entry points:

+ + Project Mailing List:
+ score-dev@eclipse.org +

+ + Architectural Discussion:
+ Join SDV's slack workspace and jump to + #score-project-channel-public + +

+ + Eclipse S-CORE Project Office Hours:
+ + Monday 13.00 - 14.00 (Weekly) + + +



+ Find all our meetings:
+ Open Eclipse community calendar + +

+ General Information / Alignment regarding S-CORE as a basis for distributions & products:
+ + Contact one of the project leads of SCORE + + +

+ +
+ +
+
+
+

+ How to start your Contribution Journey +

+ +

+ Active Contributions to the S-CORE project are the basis for getting involved. + The S-CORE Project works according to the Eclipse Project Handbook and has named and elected project leads and committers + (see + Eclipse Safe Open Vehicle Core + + ).

The direction of the S-CORE project is discussed and decided in the project lead circle, + the technical direction is created and upfront in the tech lead circle. Meeting notes are transparent via the + + S-CORE GitHub Discussions. +

+ +

+

+ We aim to build a safety ready full stack architecture, + where components fit to each other in automotive grade Software Quality and performance. To achieve this, we follow a strict + + feature roadmap and architecture + + and a rigid + + software development process +

+ +

+ +

+ Contributions to the S-CORE project must therefore follow the technical direction of the project and the S-CORE architecture. + For an introduction on how to contribute, please check out our + How to Contribut Guideline. +

+

+ + + +
+
+ +
+ +


+ +
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
diff --git a/content/townhalls.md b/content/townhalls.md new file mode 100644 index 0000000..61b70e8 --- /dev/null +++ b/content/townhalls.md @@ -0,0 +1,254 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/news.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/loading.js" +--- + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+
+
+
+ +
+
+
+ + + + Apr 11, 2025 +
+

+ Eclipse S-CORE Townhall +

+

+ Background information to S-CORE and Q&A session. +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+
+ + +
+
+ +
diff --git a/content/training-modules.md b/content/training-modules.md new file mode 100644 index 0000000..0378952 --- /dev/null +++ b/content/training-modules.md @@ -0,0 +1,1259 @@ +--- +title: "Eclipse S-CORE" +render_raw: true +extra_styles: + - "css/bootstrap.min.css" + - "css/loading.css" + - "css/navbar.css" + - "css/swiper-bundle.min.css" + - "css/globals.css" + - "css/footer.css" + - "css/styleguide.css" + - "css/campus.css" + - "css/about-us.css" +external_styles: + - "https://cdn.jsdelivr.net/npm/@glidejs/glide/dist/css/glide.core.min.css" +extra_scripts: + - "js/jquery-3.7.1.min.js" + - "js/bootstrap.min.js" + - "js/swiper-bundle.min.js" + - "js/swiper.js" + - "js/loading.js" +--- + +
+ +
+
+
+

Join us

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+

+ Start Your Contribution Journey +

+ +

+ Dive into the S-CORE contributor community by adhering to our guiding principles. + We strive for impactful, efficient contributions that evolve the project without + redundancy while connected to the "Development Workflow”. +

+

+ Learn how the stack works — from core systems to application + support. +

+ +
+
+ + + +
+ +
+
+
+

Our Guiding Principles

+

+ S-CORE is built upon core principles that champion inclusivity, efficiency, and innovation within the open source automotive software community. + Our collaborative framework welcomes contributions from everyone, paving the way for more advanced and robust solutions. + Below are the guiding principles that steer the S-CORE ecosystem +

+
+
+
+ Evolve, Everybody Can Join: +

Evolve, Everybody Can Join:

+

+ We recognize the power of collective intelligence and the strength of diverse contributions. + Everyone is welcome to participate, use, and join S-CORE, fostering a vibrant community united by shared goals and mutual growth. + +

+
+
+ No Re-Implementation: +

No Re-Implementation:

+

+ Our approach leverages existing solutions to optimize development processes. + By building on established findings and methodologies, we avoid redundancy, focusing our efforts on crafting innovative and efficient solutions. + +

+
+
+ Working Model - Shift Left: +

Working Model - Shift Left:

+

+ We adopt a proactive development model that prioritizes early testing and integration, + ensuring high quality and minimizing risks throughout the software lifecycle. +

+
+
+ S-CORE Ecosystem: +

S-CORE Ecosystem:

+

+ Our ecosystem thrives on collaboration and co-creation across various stakeholders, including universities, + industry partners, and EU commissions. We encourage dynamic contributions and collective efforts to achieve shared objectives. + +

+
+
+ Engage and Get Involved: +

Engage and Get Involved:

+

+ Join us on this transformative journey and explore opportunities to contribute to S-CORE's evolution. Visit our Get Involved pages for more details, + and learn about the S-CORE structure by browsing the About Us section for comprehensive insights. +

+
+
+
+
+ +
+
+
+

Broaden Your Impact Beyond Code

+

+ Become actively involved with S-CORE — we are committed to continuous improvement through open collaboration. + Engage with a community of innovators and explore opportunities to contribute to ongoing projects and development processes. +

+
+
+
+
+

+ Community Participation +

+
+ +
+

+ Extend your influence beyond code. Engage with the community through participation, + and contribute to various initiatives that support S-CORE's evolution.


+ Ways to Participate
+ Documentation enhancements improve project understanding and usability.
+ Event Participation: Involve yourself in community events, discussions and workshops.
+ Specialized Working Groups: Bring in your specific knowledge on processes, safety etc.
+ Feedback and Testing: Offer insights within the for project improvement.
+ +

+ +
+
+

+ Community Engagement +

+
+ +
+

+ Connect and Collaborate + Engage in lively discussions within the S-CORE community, sharing insights and collaboratively tackling challenges. + The community fosters innovation and collective growth.

+ A Vibrant Hub of Interaction
+ Join forums and contribute to dialogue.
+ Engagement Platforms
+ Forums and Channels: Discuss topics, share knowledge, and evolve solutions.
+ Feedback Mechanism: Receive updates and contribute insights to active projects.
+ +

+
+
+
+
+
+ +
+ + +
+
+
+
+

+ Frequently Asked Questions +

+

+ Get quick answers to the most common questions about S-CORE. + Whether you're just starting or deep into development, our FAQs + cover everything from training schedules to platform usage — + helping you find what you need without the hassle. +

+
+ + +
    + + + +
+ + +
+ +
+
+
+
+ +
+

+ +

+
+
+ The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. +
+
+
+ + +
+

+ +

+
+
+ Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules +
+
+
+ + +
+

+ +

+
+
+ A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors +
+
+
+ +
+

+ +

+
+
+ Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . +
+
+
+
+ +
+ +
+

+ +

+
+
+ Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. +
+
+
+ +
+

+ +

+
+
+ S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . +
+
+
+ +
+

+ +

+
+
+ Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository +
+
+
+ +
+

+ +

+
+
+ Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . +
+
+
+
+
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. +
+
+
+
+
+
+

+ +

+
+
+ S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. +
+
+
+
+
+
+

+ +

+
+
+ Change Request types include Feature, Feature Modification, Component, and Component Modification . +
+
+
+
+ +
+
+

+ +

+
+
+ Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . +
+
+
+
+ + +
+
+

+ +

+
+
+ GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . +
+
+
+
+ + +
+
+

+ +

+
+
+ Technical Leads manage the platform development, control multiple modules, and handle escalations . +
+
+
+
+ + +
+
+

+ +

+
+
+ Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . +
+
+
+
+ + +
+
+

+ +

+
+
+ Features and components are integrated into the platform using change requests and verified through tests . +
+
+
+
+ + +
+
+

+ +

+
+
+ Problems are reported through GitHub Issues, including documentation and resolution planning. +
+
+
+
+ +
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests +
+
+
+
+ +
+
+

+ +

+
+
+ Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination +
+
+
+
+ + +
+
+

+ +

+
+
+ Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git +
+
+
+
+ + +
+
+

+ +

+
+
+ Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Contribution Request Guideline details the process of submitting new features and tools . +
+
+
+
+ + +
+
+

+ +

+
+
+ Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. +
+
+
+
+ +
+
+
+
+
+
+


+
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html new file mode 100644 index 0000000..bf4fde2 --- /dev/null +++ b/layouts/_default/baseof.html @@ -0,0 +1,53 @@ + + + + + + + {{ $defaultDescription := .Site.Params.description }} + {{ $pageDescription := .Description | default .Params.description | default $defaultDescription }} + {{ if .IsHome }}{{ .Site.Title }}{{ else }}{{ .Title }} | {{ .Site.Title }}{{ end }} + + + + + {{ $styles := slice "css/bootstrap.min.css" "css/loading.css" "css/navbar.css" "css/globals.css" "css/footer.css" "css/styleguide.css" }} + {{ with .Params.extra_styles }} + {{ range . }} + {{ $styles = $styles | append . }} + {{ end }} + {{ end }} + + {{ range uniq $styles }} + + {{ end }} + + {{ with .Params.external_styles }} + {{ range . }} + + {{ end }} + {{ end }} + + + {{ block "main" . }}{{ end }} + + {{ $scripts := slice "js/jquery-3.7.1.min.js" "js/bootstrap.min.js" "js/loading.js" }} + {{ with .Params.extra_scripts }} + {{ range . }} + {{ $scripts = $scripts | append . }} + {{ end }} + {{ end }} + + {{ range uniq $scripts }} + + {{ end }} + + {{ with .Params.external_scripts }} + {{ range . }} + + {{ end }} + {{ end }} + + {{ block "scripts" . }}{{ end }} + + \ No newline at end of file diff --git a/layouts/_default/single.html b/layouts/_default/single.html new file mode 100644 index 0000000..437933e --- /dev/null +++ b/layouts/_default/single.html @@ -0,0 +1,7 @@ +{{ define "main" }} +{{ if .Params.render_raw }} +{{ .RawContent | safeHTML }} +{{ else }} +{{ .Content }} +{{ end }} +{{ end }} diff --git a/layouts/index.html b/layouts/index.html new file mode 100644 index 0000000..437933e --- /dev/null +++ b/layouts/index.html @@ -0,0 +1,7 @@ +{{ define "main" }} +{{ if .Params.render_raw }} +{{ .RawContent | safeHTML }} +{{ else }} +{{ .Content }} +{{ end }} +{{ end }} diff --git a/static/about-us.html b/legacy-html/about-us.html similarity index 97% rename from static/about-us.html rename to legacy-html/about-us.html index 7dae234..e998c7e 100644 --- a/static/about-us.html +++ b/legacy-html/about-us.html @@ -1,751 +1,751 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - -
- -
-
-
-

About Us

-
-
- -
-
-
-
- -
-
-
-
-
-
-

Who We Are

-

- We’re a collaborative and ever-growing community of automotive - experts, technology partners, developers, and innovators - united under the Eclipse Foundation. Together, we’re shaping - the future of automotive software by building open, safe, and - scalable solutions. -

- -
-
-
- Vision Icon -
-
-

Our Vision

-

- “Build the best automotive runtime solution – ONLY - ONCE!” -

-
-
- -
-
- Vision Icon -
-
-

Our Mission

-

- Unite the automotive software community around
- ONE OPEN-SOURCE CORE” -
-
- -

-

- Reuse “Stop - reinventing the wheel” -

-

- Reduce - “…complexity, effort,…” -

-

- Evolve “Build on a - future-proof foundation” -

-
-
-
-
-
-
-
- -
-
-
-
-
- -
-
-
-

Our Contributors

-

- S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

-
-
-
-
-
-
- Member 2 -
-
-
-
- Member 3 -
-
-
-
- Member 4 -
-
-
-
- Member 5 -
-
-
-
- Member 6 -
-
-
-
- Member 1 -
-
-
-
- Member 7 -
-
-
-
- Member 8 -
-
-
-
- Member 9 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
- - -
-
-
-
- -
-
-
-

S-CORE Community Structure

-

- S-CORE brings together members, technical leads, and specialized - teams to define and manage modules, propose requirements, and - ensure the platform evolves with clarity and purpose. -

-
-
-
-
- -
-
-
-
-
- -
-
-
-

Steering Committees

-

- Every core member can name a project lead. Project leads are - representatives of their entities, and jointly they´re steering - the project. Because of the project´s size, an additional role - “technical leads” was introduced in S-Core. Each project lead can - nominate one technical lead to support in operational topics like - project planning. In order to run the project, there are two major - committees: -

-
-
-
-
-

- Technical Lead Circle -

-
- -
-

- The Technical Steering Committee (TSC) is responsible for the - overall technical direction of the project. It ensures that - the project remains aligned with its goals and objectives, and - it provides guidance on technical decisions. -

-
-
-

- Project Lead Circle -

-
- -
-

- The Project Management Committee (PMC) is responsible for the - day-to-day management of the project. It oversees the - project's progress, manages resources, and ensures that - deadlines are met. -

-
-
-
-
-
- -
-
-
-

Communities

-

- Every S-CORE community has its focus topic, and every S-CORE - member is free to join, discuss and to shape the outcome. -

-
-
-
- Software Architecture -

Software Architecture

-

- - In this community, the overall software architecture of our - stack is planned. Join here to get the recent information about - next features for S-CORE. . -

-
-
- Software Development Process -

Software Development Process

-

- Due to our goal to deliver a stack which is safety certifiable, - we need well defined software development processes. This - community is continuously designing & improving our processes. -

-
-
- Infrastructure -

Infrastructure

-

- To enable a fast and reliable development, this community is - setting up the build infrastructure, the tooling, process - enabling, the CI/CD pipelines, and more… -

-
-
- Testing -

Testing

-

- To meet our quality goals, S-CORE needs to be tested – In this - community, experienced test managers and testers are ensuring - exactly this. -

-
-
- Marketing & Communication -

Marketing & Communication

-

- S-CORE can only be successful, when more and more members are - joining! – This community ensures, that the great results - -provided by S-CORE teams- are communicated to the automotive - community. -

-
-
-
-
- -
-
-
-

- Community Voices – What Our Members Say -

-

- Community Voices captures insights and experiences from our - members, highlighting their role in shaping the platform and - driving innovation within the S-CORE ecosystem. Their feedback - reflects the impact, collaboration, and shared vision that fuel - our open-source journey. -

-
-
-
-
-
-
-
-
- -
-
-
Mike Milinkovich
-
Executive Director of the Eclipse Foundation
-
-
- -
-
-

- With S-CORE, we’re providing developers with a reliable, safety-grade runtime environment that allows the industry to focus on innovation while reducing duplication of effort. This project offers the entire sector a jumpstart in building the custom solutions that will define the future of mobility -

-
-
- -
-
-
-
- -
-
-
Anton Krivoborodov
-
Technical Project Lead - BMW
-
-
-
-
-

- With S-Core, we can shape the future of the Safe-POSIX platform with the support of a strong open-source community. -

-
-
- -
-
-
-
- -
-
-
Markus Schupfner
-
CEO Qorix
-
-
-
-
-

- S-CORE is more than a project – it’s the foundation of an open, collaborative future for automotive software. As a founding contributor and distributor, Qorix is proud to shape a platform that turns shared challenges into shared progress. -

-
-
- -
-
-
-
- -
-
-
Sven Kappel
-
Head of ETAS.NEXT
-
-
-
-
-

- At ETAS, we believe in the transformative potential of open collaboration in driving software innovation. - As a founding member of Eclipse S-CORE, we are committed to shaping a robust platform that fosters seamless integration, - sustainable development processes, and cutting-edge solutions empowering tomorrow's automotive software -

-
-
- -
-
-
-
- -
-
-
Lars Bauhofer
-
Product Program Manager - Qorix
-
-
-
-
-

- S-CORE makes collaboration tangible. From architecture workshops to release planning – we’re actively building the stack, aligning teams, and turning code into common ground. -

-
-
-
-
-
-
- -
-
-
Dr. Nico Hartmann
-
CTO - Qorix
-
-
-
-
-

- Contributing to S-CORE means contributing to what matters: deterministic execution, safety by design, and reusable infrastructure. We bring the middleware expertise – and we’re here to make it usable at scale. -

-
-
-
- - -
-
-
-
- - -
-
- -
- - - - - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + + +
+ +
+
+
+

About Us

+
+
+ +
+
+
+
+ +
+
+
+
+
+
+

Who We Are

+

+ We’re a collaborative and ever-growing community of automotive + experts, technology partners, developers, and innovators + united under the Eclipse Foundation. Together, we’re shaping + the future of automotive software by building open, safe, and + scalable solutions. +

+ +
+
+
+ Vision Icon +
+
+

Our Vision

+

+ “Build the best automotive runtime solution – ONLY + ONCE!” +

+
+
+ +
+
+ Vision Icon +
+
+

Our Mission

+

+ Unite the automotive software community around
+ ONE OPEN-SOURCE CORE” +
+
+ +

+

+ Reuse “Stop + reinventing the wheel” +

+

+ Reduce + “…complexity, effort,…” +

+

+ Evolve “Build on a + future-proof foundation” +

+
+
+
+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+
+
+
+ Member 2 +
+
+
+
+ Member 3 +
+
+
+
+ Member 4 +
+
+
+
+ Member 5 +
+
+
+
+ Member 6 +
+
+
+
+ Member 1 +
+
+
+
+ Member 7 +
+
+
+
+ Member 8 +
+
+
+
+ Member 9 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+ + +
+
+
+
+ +
+
+
+

S-CORE Community Structure

+

+ S-CORE brings together members, technical leads, and specialized + teams to define and manage modules, propose requirements, and + ensure the platform evolves with clarity and purpose. +

+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Steering Committees

+

+ Every core member can name a project lead. Project leads are + representatives of their entities, and jointly they´re steering + the project. Because of the project´s size, an additional role + “technical leads” was introduced in S-Core. Each project lead can + nominate one technical lead to support in operational topics like + project planning. In order to run the project, there are two major + committees: +

+
+
+
+
+

+ Technical Lead Circle +

+
+ +
+

+ The Technical Steering Committee (TSC) is responsible for the + overall technical direction of the project. It ensures that + the project remains aligned with its goals and objectives, and + it provides guidance on technical decisions. +

+
+
+

+ Project Lead Circle +

+
+ +
+

+ The Project Management Committee (PMC) is responsible for the + day-to-day management of the project. It oversees the + project's progress, manages resources, and ensures that + deadlines are met. +

+
+
+
+
+
+ +
+
+
+

Communities

+

+ Every S-CORE community has its focus topic, and every S-CORE + member is free to join, discuss and to shape the outcome. +

+
+
+
+ Software Architecture +

Software Architecture

+

+ + In this community, the overall software architecture of our + stack is planned. Join here to get the recent information about + next features for S-CORE. . +

+
+
+ Software Development Process +

Software Development Process

+

+ Due to our goal to deliver a stack which is safety certifiable, + we need well defined software development processes. This + community is continuously designing & improving our processes. +

+
+
+ Infrastructure +

Infrastructure

+

+ To enable a fast and reliable development, this community is + setting up the build infrastructure, the tooling, process + enabling, the CI/CD pipelines, and more… +

+
+
+ Testing +

Testing

+

+ To meet our quality goals, S-CORE needs to be tested – In this + community, experienced test managers and testers are ensuring + exactly this. +

+
+
+ Marketing & Communication +

Marketing & Communication

+

+ S-CORE can only be successful, when more and more members are + joining! – This community ensures, that the great results + -provided by S-CORE teams- are communicated to the automotive + community. +

+
+
+
+
+ +
+
+
+

+ Community Voices – What Our Members Say +

+

+ Community Voices captures insights and experiences from our + members, highlighting their role in shaping the platform and + driving innovation within the S-CORE ecosystem. Their feedback + reflects the impact, collaboration, and shared vision that fuel + our open-source journey. +

+
+
+
+
+
+
+
+
+ +
+
+
Mike Milinkovich
+
Executive Director of the Eclipse Foundation
+
+
+ +
+
+

+ With S-CORE, we’re providing developers with a reliable, safety-grade runtime environment that allows the industry to focus on innovation while reducing duplication of effort. This project offers the entire sector a jumpstart in building the custom solutions that will define the future of mobility +

+
+
+ +
+
+
+
+ +
+
+
Anton Krivoborodov
+
Technical Project Lead - BMW
+
+
+
+
+

+ With S-Core, we can shape the future of the Safe-POSIX platform with the support of a strong open-source community. +

+
+
+ +
+
+
+
+ +
+
+
Markus Schupfner
+
CEO Qorix
+
+
+
+
+

+ S-CORE is more than a project – it’s the foundation of an open, collaborative future for automotive software. As a founding contributor and distributor, Qorix is proud to shape a platform that turns shared challenges into shared progress. +

+
+
+ +
+
+
+
+ +
+
+
Sven Kappel
+
Head of ETAS.NEXT
+
+
+
+
+

+ At ETAS, we believe in the transformative potential of open collaboration in driving software innovation. + As a founding member of Eclipse S-CORE, we are committed to shaping a robust platform that fosters seamless integration, + sustainable development processes, and cutting-edge solutions empowering tomorrow's automotive software +

+
+
+ +
+
+
+
+ +
+
+
Lars Bauhofer
+
Product Program Manager - Qorix
+
+
+
+
+

+ S-CORE makes collaboration tangible. From architecture workshops to release planning – we’re actively building the stack, aligning teams, and turning code into common ground. +

+
+
+
+
+
+
+ +
+
+
Dr. Nico Hartmann
+
CTO - Qorix
+
+
+
+
+

+ Contributing to S-CORE means contributing to what matters: deterministic execution, safety by design, and reusable infrastructure. We bring the middleware expertise – and we’re here to make it usable at scale. +

+
+
+
+ + +
+
+
+
+ + +
+
+ +
+ + + + + + + + + + diff --git a/static/articles.html b/legacy-html/articles.html similarity index 97% rename from static/articles.html rename to legacy-html/articles.html index 57526a4..0f03a6f 100644 --- a/static/articles.html +++ b/legacy-html/articles.html @@ -1,414 +1,414 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
- -
-
-
-

News & Events

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
-
-
-
-
-
- -
-
-
- - - - Nov 6th, 2025 -
-

- Eclipse S-CORE 0.5 – What’s inside the first public release. -

-

- Source: Eclipse SDV WG Linkedin

-

-

- The first version of Eclipse S-CORE (Safe Open Vehicle Core) lays the groundwork for open, safety-ready automotive software.
- -

- - Read More and Discuss - -
-
-
-
- -
-
-
- - - - Sept 30, 2025 -
-

- Eclipse S-CORE: A new approach to building automotive software together -

-

- by Valerie Hasler and Memsud Godinjak -

- - Read More - -
-
- -
-
- - Show More - -
-
-
-
- -
-
-
-
-
- - -
-
- -
- - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+
+
+
+ +
+
+
+ + + + Nov 6th, 2025 +
+

+ Eclipse S-CORE 0.5 – What’s inside the first public release. +

+

+ Source: Eclipse SDV WG Linkedin

+

+

+ The first version of Eclipse S-CORE (Safe Open Vehicle Core) lays the groundwork for open, safety-ready automotive software.
+ +

+ + Read More and Discuss + +
+
+
+
+ +
+
+
+ + + + Sept 30, 2025 +
+

+ Eclipse S-CORE: A new approach to building automotive software together +

+

+ by Valerie Hasler and Memsud Godinjak +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+
+ + +
+
+ +
+ + + + + diff --git a/static/blog-details.html b/legacy-html/blog-details.html similarity index 97% rename from static/blog-details.html rename to legacy-html/blog-details.html index f75e120..0e4f977 100644 --- a/static/blog-details.html +++ b/legacy-html/blog-details.html @@ -1,442 +1,442 @@ - - - - - - - S-CORE - - - - - - - - - - - - - - - - -
- -
-
-
-

- Unlocking Innovation: The Power of Open Source Software -

-
-
- -
-
-
-
- -
-
-
-
-
- - - - 14 Feb, 2024 -
- -

- One of the greatest advantages of open source software is its - community-driven nature, which brings together developers from - across the world. These contributors often come from vastly - different backgrounds, cultures, and levels of experience — yet - they unite around a shared goal: building better software. This - global collaboration leads to diverse perspectives, creative - problem-solving, and faster identification of bugs or security - flaws. Since the code is open and accessible, anyone can - contribute, whether it’s by writing new features, improving - documentation, or testing for issues. This open process allows the - software to evolve rapidly, often outpacing traditional - closed-source development. With thousands of eyes reviewing and - refining the code, quality tends to increase over time. The sense - of shared ownership among contributors also builds trust and - commitment within the community. Unlike proprietary systems, where - innovation is limited to internal teams, open source benefits from - decentralized innovation at scale. It’s this collaborative spirit - that turns open source from just code into a movement — one that’s - shaping the future of technology. -

-
- -
-
-

Recommended

-
-
-
-
-
-
- -
-
-

Next Eclipse Community Event

-

- Next Eclipse Community Event, June 4th 2025 in Starnberg -

-
-
- Learn More -
- -
- -
-
- -
-
- -
-
-

Next Eclipse Community Event

-

- Next Eclipse Community Event, June 4th 2025 in Starnberg -

-
-
- Learn More -
- -
- -
-
-
-
- -
-
-

Next Eclipse Community Event

-

- Next Eclipse Community Event, June 4th 2025 in Starnberg -

-
-
- Learn More -
- -
- -
-
-
-
- -
-
-

Next Eclipse Community Event

-

- Next Eclipse Community Event, June 4th 2025 in Starnberg -

-
-
- Learn More -
- -
- -
-
-
-
- -
-
-

Next Eclipse Community Event

-

- Next Eclipse Community Event, June 4th 2025 in Starnberg -

-
-
- Learn More -
- -
- -
-
-
- - -
-
-
-
-
- - -
-
- -
- - - - - - - + + + + + + + S-CORE + + + + + + + + + + + + + + + + +
+ +
+
+
+

+ Unlocking Innovation: The Power of Open Source Software +

+
+
+ +
+
+
+
+ +
+
+
+
+
+ + + + 14 Feb, 2024 +
+ +

+ One of the greatest advantages of open source software is its + community-driven nature, which brings together developers from + across the world. These contributors often come from vastly + different backgrounds, cultures, and levels of experience — yet + they unite around a shared goal: building better software. This + global collaboration leads to diverse perspectives, creative + problem-solving, and faster identification of bugs or security + flaws. Since the code is open and accessible, anyone can + contribute, whether it’s by writing new features, improving + documentation, or testing for issues. This open process allows the + software to evolve rapidly, often outpacing traditional + closed-source development. With thousands of eyes reviewing and + refining the code, quality tends to increase over time. The sense + of shared ownership among contributors also builds trust and + commitment within the community. Unlike proprietary systems, where + innovation is limited to internal teams, open source benefits from + decentralized innovation at scale. It’s this collaborative spirit + that turns open source from just code into a movement — one that’s + shaping the future of technology. +

+
+ +
+
+

Recommended

+
+
+
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+ +
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Next Eclipse Community Event

+

+ Next Eclipse Community Event, June 4th 2025 in Starnberg +

+
+
+ Learn More +
+ +
+ +
+
+
+ + +
+
+
+
+
+ + +
+
+ +
+ + + + + + + diff --git a/static/docs.html b/legacy-html/docs.html similarity index 97% rename from static/docs.html rename to legacy-html/docs.html index 75b84ba..1d2b38e 100644 --- a/static/docs.html +++ b/legacy-html/docs.html @@ -1,372 +1,372 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
- -
-
-
-

Docs

-
-
- -
-
-
-
- -
-
-
-
-

Eclipse S-Core Building Blocks

- -
-
- - S-CORE v0.5 module -
-
- - - S-CORE v1.0 module -
-
-
- -
-
-

- This section provides a schematic overview of the technical building blocks that form the foundation of our platform. - Here, you’ll find a clear differentiation between S-CORE modules available in version 0.5 and those planned for version 1.0.
-

-
-
- -
-
-
-
-
-
- -
-
-
-

S-Core Project Roadmap

-
-
-
-

- Get athe development and release timeline of Eclipse S-CORE. It shows the key phases that shape the platform’s evolution—starting from early development to achieving maturity and stability. - Gain an understanding of how each phase contributes to delivering a scalable and reliable platform. -

-
-
- -
-
-
-
-
-
- -
-
-
-

Build & Documentation Toolchain

-

- The build system uses Bazel to automate workflows like repository - cloning, software builds, documentation generation, testing, and - more. Documentation is managed with Sphinx and sphinx-needs, while - diagrams are created using PlantUML and draw.io. Supported - languages include C++ and Rust, with testing handled by - gtest/gmock. -

-
-
-
-
-
- -
-
-

- Check out our GitHub Project - - -
-
-
- - -
-
- -
- - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + +
+ +
+
+
+

Docs

+
+
+ +
+
+
+
+ +
+
+
+
+

Eclipse S-Core Building Blocks

+ +
+
+ + S-CORE v0.5 module +
+
+ + + S-CORE v1.0 module +
+
+
+ +
+
+

+ This section provides a schematic overview of the technical building blocks that form the foundation of our platform. + Here, you’ll find a clear differentiation between S-CORE modules available in version 0.5 and those planned for version 1.0.
+

+
+
+ +
+
+
+
+
+
+ +
+
+
+

S-Core Project Roadmap

+
+
+
+

+ Get athe development and release timeline of Eclipse S-CORE. It shows the key phases that shape the platform’s evolution—starting from early development to achieving maturity and stability. + Gain an understanding of how each phase contributes to delivering a scalable and reliable platform. +

+
+
+ +
+
+
+
+
+
+ +
+
+
+

Build & Documentation Toolchain

+

+ The build system uses Bazel to automate workflows like repository + cloning, software builds, documentation generation, testing, and + more. Documentation is managed with Sphinx and sphinx-needs, while + diagrams are created using PlantUML and draw.io. Supported + languages include C++ and Rust, with testing handled by + gtest/gmock. +

+
+
+
+
+
+ +
+
+

+ Check out our GitHub Project + + +
+
+
+ + +
+
+ +
+ + + + + + + diff --git a/static/faq.html b/legacy-html/faq.html similarity index 97% rename from static/faq.html rename to legacy-html/faq.html index a6be807..8fa9654 100644 --- a/static/faq.html +++ b/legacy-html/faq.html @@ -1,1234 +1,1234 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
- -
-
-
-

Frequently Asked Questions

-
-
- -
-
-
-
- -
- - -
-
-
-
- -

- Get quick answers to the most common questions about S-CORE. Whether you're just starting or deep into development, - our FAQs cover everything from training schedules to platform usage — helping you find what you need without the hassle. -

- - -
-
- - - -
- -
-
- - - -
    - - - -
- - -
- -
-
-
-
- -
-

- -

-
-
- The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. -
-
-
- - -
-

- -

-
-
- Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules -
-
-
- - -
-

- -

-
-
- A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors -
-
-
- -
-

- -

-
-
- Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . -
-
-
-
- -
- -
-

- -

-
-
- Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. -
-
-
- -
-

- -

-
-
- S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . -
-
-
- -
-

- -

-
-
- Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository -
-
-
- -
-

- -

-
-
- Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . -
-
-
-
-
-
-
- - -
-
-
-
-
-

- -

-
-
- Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. -
-
-
-
-
-
-

- -

-
-
- S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. -
-
-
-
-
-
-

- -

-
-
- Change Request types include Feature, Feature Modification, Component, and Component Modification . -
-
-
-
- -
-
-

- -

-
-
- Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . -
-
-
-
- - -
-
-

- -

-
-
- GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . -
-
-
-
- - -
-
-

- -

-
-
- Technical Leads manage the platform development, control multiple modules, and handle escalations . -
-
-
-
- - -
-
-

- -

-
-
- Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . -
-
-
-
- - -
-
-

- -

-
-
- Features and components are integrated into the platform using change requests and verified through tests . -
-
-
-
- - -
-
-

- -

-
-
- Problems are reported through GitHub Issues, including documentation and resolution planning. -
-
-
-
- -
-
-
- - -
-
-
-
-
-

- -

-
-
- Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests -
-
-
-
- -
-
-

- -

-
-
- Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination -
-
-
-
- - -
-
-

- -

-
-
- Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git -
-
-
-
- - -
-
-

- -

-
-
- Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . -
-
-
-
- - -
-
-

- -

-
-
- The Contribution Request Guideline details the process of submitting new features and tools . -
-
-
-
- - -
-
-

- -

-
-
- Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . -
-
-
-
- - -
-
-

- -

-
-
- The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. -
-
-
-
- -
-
-
-
-
-
-


-
-
-
-
-

- Stay Connected with S-CORE -

-

- Join the conversation, access exclusive resources, and follow us - for the latest updates. -

-
- -
- -
-
- Join Icon -
-
Join S-CORE
-

Connect With Us!

-
-
-
- - -
-
- Download Icon -
-
Stay up to date!
-

Read our latest news!

-
-
-
- -
-
-
- - LinkedIn - - - Slack - -
-
-
Follow Us
-

- Stay in the loop on all platforms! -

-
-
-
-
-
-
-
- - -
-
- -
- - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + + + +
+ +
+
+
+

Frequently Asked Questions

+
+
+ +
+
+
+
+ +
+ + +
+
+
+
+ +

+ Get quick answers to the most common questions about S-CORE. Whether you're just starting or deep into development, + our FAQs cover everything from training schedules to platform usage — helping you find what you need without the hassle. +

+ + +
+
+ + + +
+ +
+
+ + + +
    + + + +
+ + +
+ +
+
+
+
+ +
+

+ +

+
+
+ The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. +
+
+
+ + +
+

+ +

+
+
+ Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules +
+
+
+ + +
+

+ +

+
+
+ A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors +
+
+
+ +
+

+ +

+
+
+ Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . +
+
+
+
+ +
+ +
+

+ +

+
+
+ Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. +
+
+
+ +
+

+ +

+
+
+ S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . +
+
+
+ +
+

+ +

+
+
+ Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository +
+
+
+ +
+

+ +

+
+
+ Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . +
+
+
+
+
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. +
+
+
+
+
+
+

+ +

+
+
+ S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. +
+
+
+
+
+
+

+ +

+
+
+ Change Request types include Feature, Feature Modification, Component, and Component Modification . +
+
+
+
+ +
+
+

+ +

+
+
+ Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . +
+
+
+
+ + +
+
+

+ +

+
+
+ GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . +
+
+
+
+ + +
+
+

+ +

+
+
+ Technical Leads manage the platform development, control multiple modules, and handle escalations . +
+
+
+
+ + +
+
+

+ +

+
+
+ Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . +
+
+
+
+ + +
+
+

+ +

+
+
+ Features and components are integrated into the platform using change requests and verified through tests . +
+
+
+
+ + +
+
+

+ +

+
+
+ Problems are reported through GitHub Issues, including documentation and resolution planning. +
+
+
+
+ +
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests +
+
+
+
+ +
+
+

+ +

+
+
+ Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination +
+
+
+
+ + +
+
+

+ +

+
+
+ Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git +
+
+
+
+ + +
+
+

+ +

+
+
+ Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Contribution Request Guideline details the process of submitting new features and tools . +
+
+
+
+ + +
+
+

+ +

+
+
+ Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. +
+
+
+
+ +
+
+
+
+
+
+


+
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
+ + + + + + + diff --git a/static/how_to_contribute.html b/legacy-html/how_to_contribute.html similarity index 97% rename from static/how_to_contribute.html rename to legacy-html/how_to_contribute.html index 0f27e87..f4304ed 100644 --- a/static/how_to_contribute.html +++ b/legacy-html/how_to_contribute.html @@ -1,722 +1,722 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - -
- -
-
-
-

How To Contribute

-
-
- -
-
-
-
- -
-
-
-
-
-
-

Who We Are

-

- We’re a collaborative and ever-growing community of automotive - experts, technology partners, developers, and innovators - united under the Eclipse Foundation. Together, we’re shaping - the future of automotive software by building open, safe, and - scalable solutions. -

- -
-
-
- Vision Icon -
-
-

Our Vision

-

- “Build the best automotive runtime solution – ONLY - ONCE!” -

-
-
- -
-
- Vision Icon -
-
-

Our Mission

-

- Unite the automotive software community around ONE - OPEN-SOURCE CORE” -

-

- Reuse “Stop - reinventing the wheel” -

-

- Reduce - “…complexity, effort,…” -

-

- Evolve “Build on a - future-proof foundation” -

-
-
-
-
-
-
-
- -
-
-
-
-
- -
-
-
-

Our Contributors

-

- S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

-
-
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
-
-
- -
-
-
-

S-CORE Community Structure

-

- S-CORE brings together members, technical leads, and specialized - teams to define and manage modules, propose requirements, and - ensure the platform evolves with clarity and purpose. -

-
-
-
-
- -
-
-
-
-
- -
-
-
-

Steering Committees

-

- Every core member can name a project lead. Project leads are - representatives of their entities, and jointly they´re steering - the project. Because of the project´s size, an additional role - “technical leads” was introduced in S-Core. Each project lead can - nominate one technical lead to support in operational topics like - project planning. In order to run the project, there are two major - committees: -

-
-
-
-
-

- Technical Lead Circle -

-
- -
-

- The Technical Steering Committee (TSC) is responsible for the - overall technical direction of the project. It ensures that - the project remains aligned with its goals and objectives, and - it provides guidance on technical decisions. -

-
-
-

- Project Lead Circle -

-
- -
-

- The Project Management Committee (PMC) is responsible for the - day-to-day management of the project. It oversees the - project's progress, manages resources, and ensures that - deadlines are met. -

-
-
-
-
-
- -
-
-
-

Communities

-

- Every S-CORE community has its focus topic, and every S-CORE - member is free to join, discuss and to shape the outcome. -

-
-
-
- Software Architecture -

Software Architecture

-

- In this community, the overall software architecture of our - stack is planned. Join here to get the recent information about - next features for S-CORE. . -

-
-
- Software Development Process -

Software Development Process

-

- Due to our goal to deliver a stack which is safety certifiable, - we need well defined software development processes. This - community is continuously designing & improving our processes. -

-
-
- Infrastructure -

Infrastructure

-

- To enable a fast and reliable development, this community is - setting up the build infrastructure, the tooling, process - enabling, the CI/CD pipelines, and more… -

-
-
- Testing -

Testing

-

- To meet our quality goals, S-CORE needs to be tested – In this - community, experienced test managers and testers are ensuring - exactly this. -

-
-
- Marketing & Communication -

Marketing & Communication

-

- S-CORE can only be successful, when more and more members are - joining! – This community ensures, that the great results - -provided by S-CORE teams- are communicated to the automotive - community. -

-
-
-
-
- -
-
-
-

- Community Voices – What Our Members Say -

-

- Community Voices captures insights and experiences from our - members, highlighting their role in shaping the platform and - driving innovation within the S-CORE ecosystem. Their feedback - reflects the impact, collaboration, and shared vision that fuel - our open-source journey. -

-
-
-
-
-
-
-
-
- -
-
-
Serhiy Hipskyy
-
CEO Universal
-
-
-
-
- -
-
- -
-
- -
- -
- -
-
- -
-
-
-
-

- On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

-
-
- -
-
-
-
- -
-
-
Serhiy Hipskyy
-
CEO Universal
-
-
-
-
- -
-
- -
-
- -
- -
- -
-
- -
-
-
-
-

- On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

-
-
- -
-
-
-
- -
-
-
Serhiy Hipskyy
-
CEO Universal
-
-
-
-
- -
-
- -
-
- -
- -
- -
-
- -
-
-
-
-

- On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

-
-
- -
-
-
-
- -
-
-
Serhiy Hipskyy
-
CEO Universal
-
-
-
-
- -
-
- -
-
- -
- -
- -
-
- -
-
-
-
-

- On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

-
-
-
- - -
-
-
-
- - -
-
- -
- - - - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + +
+ +
+
+
+

How To Contribute

+
+
+ +
+
+
+
+ +
+
+
+
+
+
+

Who We Are

+

+ We’re a collaborative and ever-growing community of automotive + experts, technology partners, developers, and innovators + united under the Eclipse Foundation. Together, we’re shaping + the future of automotive software by building open, safe, and + scalable solutions. +

+ +
+
+
+ Vision Icon +
+
+

Our Vision

+

+ “Build the best automotive runtime solution – ONLY + ONCE!” +

+
+
+ +
+
+ Vision Icon +
+
+

Our Mission

+

+ Unite the automotive software community around ONE + OPEN-SOURCE CORE” +

+

+ Reuse “Stop + reinventing the wheel” +

+

+ Reduce + “…complexity, effort,…” +

+

+ Evolve “Build on a + future-proof foundation” +

+
+
+
+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+
+
+ +
+
+
+

S-CORE Community Structure

+

+ S-CORE brings together members, technical leads, and specialized + teams to define and manage modules, propose requirements, and + ensure the platform evolves with clarity and purpose. +

+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Steering Committees

+

+ Every core member can name a project lead. Project leads are + representatives of their entities, and jointly they´re steering + the project. Because of the project´s size, an additional role + “technical leads” was introduced in S-Core. Each project lead can + nominate one technical lead to support in operational topics like + project planning. In order to run the project, there are two major + committees: +

+
+
+
+
+

+ Technical Lead Circle +

+
+ +
+

+ The Technical Steering Committee (TSC) is responsible for the + overall technical direction of the project. It ensures that + the project remains aligned with its goals and objectives, and + it provides guidance on technical decisions. +

+
+
+

+ Project Lead Circle +

+
+ +
+

+ The Project Management Committee (PMC) is responsible for the + day-to-day management of the project. It oversees the + project's progress, manages resources, and ensures that + deadlines are met. +

+
+
+
+
+
+ +
+
+
+

Communities

+

+ Every S-CORE community has its focus topic, and every S-CORE + member is free to join, discuss and to shape the outcome. +

+
+
+
+ Software Architecture +

Software Architecture

+

+ In this community, the overall software architecture of our + stack is planned. Join here to get the recent information about + next features for S-CORE. . +

+
+
+ Software Development Process +

Software Development Process

+

+ Due to our goal to deliver a stack which is safety certifiable, + we need well defined software development processes. This + community is continuously designing & improving our processes. +

+
+
+ Infrastructure +

Infrastructure

+

+ To enable a fast and reliable development, this community is + setting up the build infrastructure, the tooling, process + enabling, the CI/CD pipelines, and more… +

+
+
+ Testing +

Testing

+

+ To meet our quality goals, S-CORE needs to be tested – In this + community, experienced test managers and testers are ensuring + exactly this. +

+
+
+ Marketing & Communication +

Marketing & Communication

+

+ S-CORE can only be successful, when more and more members are + joining! – This community ensures, that the great results + -provided by S-CORE teams- are communicated to the automotive + community. +

+
+
+
+
+ +
+
+
+

+ Community Voices – What Our Members Say +

+

+ Community Voices captures insights and experiences from our + members, highlighting their role in shaping the platform and + driving innovation within the S-CORE ecosystem. Their feedback + reflects the impact, collaboration, and shared vision that fuel + our open-source journey. +

+
+
+
+
+
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+ +
+
+
+
+ +
+
+
Serhiy Hipskyy
+
CEO Universal
+
+
+
+
+ +
+
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+

+ On the other hand, we denounce with righteous indignation + and dislike men who are so beguiled and. +

+
+
+
+ + +
+
+
+
+ + +
+
+ +
+ + + + + + + + + diff --git a/static/index.html b/legacy-html/index.html similarity index 97% rename from static/index.html rename to legacy-html/index.html index dcd017e..f150e3c 100644 --- a/static/index.html +++ b/legacy-html/index.html @@ -1,913 +1,913 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - - -
-
-
-
- -
-
-
-
-

- From Proprietary - To Open Source -

-

- The industry has long tackled software challenges - independently – often duplicating efforts and building - closed, incompatible systems.

- S-CORE changes this by uniting OEMs, suppliers and - developers around a common SW-platform. The goal of S-CORE - is to reduce complexity, promote re-use, gain speed & - enable scalable innovation. -

-
-

- Join our global community building a common, - safety-critical runtime foundation for automotive - innovation. -

-
- Explore the projects - Get Involved - Visit Our Github -
-
-
-
- 3D illustration of a futuristic car with floating cubes -
-
-
-
-
-
-
-
-
-
-

Latest News:
S-CORE Release v0.5 - beta is available

-
- -
-
-
-
- -
-
Release Notes
-

- Find out more about the release and all components integrated and available. -
- - - Release Notes - - -

- -
-
- -
-
-
- -
-
How to get started
-

- Follow this Guide to start you development with Eclipse S-CORE today! -
- - - How to get started - -

-
-
- -
-
-
- -
-
Get in touch
-

- Get in touch with us on and discuss with the developers on Slack or via E-mail! -
- - - Get in touch - - -

-
-
- - -
- -
-
-
-
-
-
-
-

Latest News & Events

- - Discover more News/Events - - -
- -
-
-
- -
-
- -
-
-

Coming soon: Eclipse S-CORE 0.5

-

- The automotive industry’s first open, safety-ready software stack is almost here.
- Eclipse S-CORE brings the community one step closer to a shared foundation for software-defined vehicles. -

-

Eclipse S-CORE:
- Open by Choice. Safe by Design.

-
-
- Learn More -
- -
- -
-
- -
-
- -
-
-

Nov 12, 2025

-

- Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles -

-
-
- Learn More -
- -
- -
-
-
-
- -
-
-

Eclipse Community Meetup, Japan/ Yokohama

-

- Introduction and update about recent S-CORE developments. -

-
-
- Learn More -
- -
- -
-
-
-
- - -
-
-
-
-
-
-
-
-

S-CORE In A Nutshell

-
-
-

Together...

-

S-CORE began in 2024 with five initial members: - Accenture, BMW, ETAS, Mercedes-Benz, and Qorix – “the coalition of the willing”.
- Since then, both active participation and global interest have grown significantly.

-
-
-
-
- -
-

OEMS

-
-
- -
-
-
- -
-

Tiers

-
-
- -
-
-
- -
-

SW-Supplier

-
-
- -
-
-
- -
-

Service Provider

-
-
-
- -

...we´re shaping an open-source and code-based SW-platform...

-

S-CORE solves the requirements of a future SDV with a collaborative, open, and modular approach. - Developed by and for the industry, it delivers a robust core architecture that reduces integration effort, - enhances safety, and accelerates development.
- Rather than fostering competition through proprietary, - stacks, S-CORE enables collaboration through standardisation.

- -
-
-
-
- -
-
-
- -
-
-
- -
-

Open Source

-
-
- -
-
-
- -
-

Code Based

-
-
-
- -

...for "dynamic core" components with strict requirements of a future SDV.

-

- S-CORE bridges the OS–application gap and is being developed as a modular, - standards-oriented middleware. The goal: enable predictable, safe, and reusable execution - environments across diverse hardware and ECU types – without prescribing a fixed implementation.
- - Its architecture is designed for safety-critical contexts – especially ADAS, Body, and Chassis – and supports compliance with ISO 26262 and ISO/SAE 21434. -

-
-
-
-
- -
-
-
- -
-
-
- -
-

Quality (ASPICE)

-
-
- -
-
-
- -
-

Safety (ISO 26262)

-
-
- -
-
-
- -
-

Security (ISO 21434)

-
-
-
-
-
-
-
-
-
-
-
-
-

- The focus of S-CORE are safety-critical in-car components -

-
-
-
-
-
- -
-
-
-
-
-
-
-
-
-
-
-

- S-CORE aims to build-up all SW-platform layers below the - application layer and above the board support package of the - SoC. -

-
-
-
-
-
- -
-
-
-
-
-
-
-
-
-
-
-

- What are the deliverables of S-CORE? -

-

- Besides describing the SW-platform, S-CORE provides a huge - load of complementary deliverables. -

-
-
-
-
-
- -
-
-
-
-
-
- -
-
-
-
-
-

Why is S-CORE Needed

-
-
- -
-
-
-
- -
-
Common Stack & Collaboration
-

- A common full-stack software runtime addressing shared - industry problems through joint solutions. -

-
-
- -
-
-
- -
-
Speed
-

- Accelerates development by working in open source with - code-centric, iterative methods. -

-
-
- -
-
-
- -
-
Abstraction & Extensibility
-

- Decouples HW and SW with flexible layers and enables - project-specific extensions of the stack. -

-
-
- -
-
-
- -
-
Quality & Efficiency
-

- A lean, no-frills solution using modern languages, - readable specs, and safe open source processes. -

-
-
-
-
-
-
- -
-
-
-
-

Our Contributors

-

- S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

-
-
-
-
-
-
- Member 1 -
-
-
-
- Member 2 -
-
-
-
- Member 3 -
-
-
-
- Member 4 -
-
-
-
- Member 5 -
-
-
-
- Member 6 -
-
-
-
- Member 7 -
-
-
-
- Member 8 -
-
-
-
- Member 9 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
-
- Member 10 -
-
-
- - -
-
-
-
-
- - - -
- -
-
-
- - -
- -
- - - - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+
+
+
+

+ From Proprietary + To Open Source +

+

+ The industry has long tackled software challenges + independently – often duplicating efforts and building + closed, incompatible systems.

+ S-CORE changes this by uniting OEMs, suppliers and + developers around a common SW-platform. The goal of S-CORE + is to reduce complexity, promote re-use, gain speed & + enable scalable innovation. +

+
+

+ Join our global community building a common, + safety-critical runtime foundation for automotive + innovation. +

+
+ Explore the projects + Get Involved + Visit Our Github +
+
+
+
+ 3D illustration of a futuristic car with floating cubes +
+
+
+
+
+
+
+
+
+
+

Latest News:
S-CORE Release v0.5 - beta is available

+
+ +
+
+
+
+ +
+
Release Notes
+

+ Find out more about the release and all components integrated and available. +
+ + + Release Notes + + +

+ +
+
+ +
+
+
+ +
+
How to get started
+

+ Follow this Guide to start you development with Eclipse S-CORE today! +
+ + + How to get started + +

+
+
+ +
+
+
+ +
+
Get in touch
+

+ Get in touch with us on and discuss with the developers on Slack or via E-mail! +
+ + + Get in touch + + +

+
+
+ + +
+ +
+
+
+
+
+
+
+

Latest News & Events

+ + Discover more News/Events + + +
+ +
+
+
+ +
+
+ +
+
+

Coming soon: Eclipse S-CORE 0.5

+

+ The automotive industry’s first open, safety-ready software stack is almost here.
+ Eclipse S-CORE brings the community one step closer to a shared foundation for software-defined vehicles. +

+

Eclipse S-CORE:
+ Open by Choice. Safe by Design.

+
+
+ Learn More +
+ +
+ +
+
+ +
+
+ +
+
+

Nov 12, 2025

+

+ Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ +
+
+

Eclipse Community Meetup, Japan/ Yokohama

+

+ Introduction and update about recent S-CORE developments. +

+
+
+ Learn More +
+ +
+ +
+
+
+
+ + +
+
+
+
+
+
+
+
+

S-CORE In A Nutshell

+
+
+

Together...

+

S-CORE began in 2024 with five initial members: + Accenture, BMW, ETAS, Mercedes-Benz, and Qorix – “the coalition of the willing”.
+ Since then, both active participation and global interest have grown significantly.

+
+
+
+
+ +
+

OEMS

+
+
+ +
+
+
+ +
+

Tiers

+
+
+ +
+
+
+ +
+

SW-Supplier

+
+
+ +
+
+
+ +
+

Service Provider

+
+
+
+ +

...we´re shaping an open-source and code-based SW-platform...

+

S-CORE solves the requirements of a future SDV with a collaborative, open, and modular approach. + Developed by and for the industry, it delivers a robust core architecture that reduces integration effort, + enhances safety, and accelerates development.
+ Rather than fostering competition through proprietary, + stacks, S-CORE enables collaboration through standardisation.

+ +
+
+
+
+ +
+
+
+ +
+
+
+ +
+

Open Source

+
+
+ +
+
+
+ +
+

Code Based

+
+
+
+ +

...for "dynamic core" components with strict requirements of a future SDV.

+

+ S-CORE bridges the OS–application gap and is being developed as a modular, + standards-oriented middleware. The goal: enable predictable, safe, and reusable execution + environments across diverse hardware and ECU types – without prescribing a fixed implementation.
+ + Its architecture is designed for safety-critical contexts – especially ADAS, Body, and Chassis – and supports compliance with ISO 26262 and ISO/SAE 21434. +

+
+
+
+
+ +
+
+
+ +
+
+
+ +
+

Quality (ASPICE)

+
+
+ +
+
+
+ +
+

Safety (ISO 26262)

+
+
+ +
+
+
+ +
+

Security (ISO 21434)

+
+
+
+
+
+
+
+
+
+
+
+
+

+ The focus of S-CORE are safety-critical in-car components +

+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+

+ S-CORE aims to build-up all SW-platform layers below the + application layer and above the board support package of the + SoC. +

+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+
+

+ What are the deliverables of S-CORE? +

+

+ Besides describing the SW-platform, S-CORE provides a huge + load of complementary deliverables. +

+
+
+
+
+
+ +
+
+
+
+
+
+ +
+
+
+
+
+

Why is S-CORE Needed

+
+
+ +
+
+
+
+ +
+
Common Stack & Collaboration
+

+ A common full-stack software runtime addressing shared + industry problems through joint solutions. +

+
+
+ +
+
+
+ +
+
Speed
+

+ Accelerates development by working in open source with + code-centric, iterative methods. +

+
+
+ +
+
+
+ +
+
Abstraction & Extensibility
+

+ Decouples HW and SW with flexible layers and enables + project-specific extensions of the stack. +

+
+
+ +
+
+
+ +
+
Quality & Efficiency
+

+ A lean, no-frills solution using modern languages, + readable specs, and safe open source processes. +

+
+
+
+
+
+
+ +
+
+
+
+

Our Contributors

+

+ S-CORE is backed by a diverse network of leading automotive + companies, technology providers, and open-source contributors. + These members play a vital role in driving innovation, shaping the + platform’s direction, and ensuring its success across real-world + applications. +

+
+
+
+
+
+
+ Member 1 +
+
+
+
+ Member 2 +
+
+
+
+ Member 3 +
+
+
+
+ Member 4 +
+
+
+
+ Member 5 +
+
+
+
+ Member 6 +
+
+
+
+ Member 7 +
+
+
+
+ Member 8 +
+
+
+
+ Member 9 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+
+ Member 10 +
+
+
+ + +
+
+
+
+
+ + + +
+ +
+
+
+ + +
+ +
+ + + + + + + + + diff --git a/static/news.html b/legacy-html/news.html similarity index 97% rename from static/news.html rename to legacy-html/news.html index ebb7b57..b0e3b14 100644 --- a/static/news.html +++ b/legacy-html/news.html @@ -1,560 +1,560 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
- -
-
-
-

News & Events

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
- -
-
-
- -
-
Upcoming Conferences
- - - -
- -
- -
- -
-
- - - - 5 Feb, 2026 -
-

- SIA 2026 | Future Proofing SDV Study Day,
Paris, France -

-

- Presenter: Björn Reistel (ETAS)
- Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" -

- - Read More - -
-
- - - -
- -
- -
- -
-
- - - - 21-23 Apr, 2026 -
-

- OCX 2026 | Open Community Exceprience,
Brussels, Belgium -

-

- Presenter: tbd.
- Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" -

- - Read More - -
-
- -
- - - - - - -
-
- - Show More - -
-
-
-
- - -
-
Previous Conferences
- - - -
-
-
-
-
-
- - -
-
- -
- - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+ +
+
+
+ +
+
Upcoming Conferences
+ + + +
+ +
+ +
+ +
+
+ + + + 5 Feb, 2026 +
+

+ SIA 2026 | Future Proofing SDV Study Day,
Paris, France +

+

+ Presenter: Björn Reistel (ETAS)
+ Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" +

+ + Read More + +
+
+ + + +
+ +
+ +
+ +
+
+ + + + 21-23 Apr, 2026 +
+

+ OCX 2026 | Open Community Exceprience,
Brussels, Belgium +

+

+ Presenter: tbd.
+ Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" +

+ + Read More + +
+
+ +
+ + + + + + +
+
+ + Show More + +
+
+
+
+ + +
+
Previous Conferences
+ + + +
+
+
+
+
+
+ + +
+
+ +
+ + + + + diff --git a/static/press_releases.html b/legacy-html/press_releases.html similarity index 97% rename from static/press_releases.html rename to legacy-html/press_releases.html index 37be152..4dc11f4 100644 --- a/static/press_releases.html +++ b/legacy-html/press_releases.html @@ -1,448 +1,448 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
- -
-
-
-

News & Events

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
-
-
- -
-
-
-
- - - - Nov 12, 2025 -
- -

- Source: Eclipse S-CORE Project -


- -

- Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles -


-

- November 12th, 2025 — The Eclipse Safe Open Vehicle Core (S-CORE) project today announced the active participation of Qualcomm Technologies, Inc. as a new member of its open-source community. - By leveraging Qualcomm Technologies Inc.’s Snapdragon® Digital Chassis™ solutions, S-CORE will run seamlessly on Qualcomm Technologies’ established high-performance hardware for future software-defined vehicles (SDVs). This collaboration further expands the reach of the S-CORE community, as a significant share of today’s safety-critical and secure automotive systems already rely on Qualcomm Technologies’ hardware.

- - Hosted by the Eclipse Foundation under the purview of the Eclipse Software Defined Vehicle Working Group, Eclipse S-CORE, is an open-source initiative delivering a shared, safety-aligned middleware platform for high-performance automotive compute platforms. Developed by leading automotive and software companies — including Accenture GmbH, Aumovio SE, BMW Group, Elektrobit Automotive GmbH, ETAS GmbH, Mercedes-Benz Tech Innovation GmbH, Qualcomm Technologies, Inc., and Qorix GmbH — S-CORE provides a scalable, modular, and interoperable foundation for safety-critical components, reducing duplication, accelerating SDV development, and promoting industry-wide standardization.

- - “Open collaboration is at the heart of solving the growing complexity of modern vehicle software,” said Mike Milinkovich, executive director of the Eclipse Foundation. “Through Eclipse S-CORE, we’re building a fully open, safety-aligned middleware foundation that helps automakers and suppliers focus on innovation instead of duplication. We’re delighted to welcome Qualcomm Technologies to this global community and the important work ahead.”

- - “Qualcomm Technologies’ engagement with S-CORE represents a pivotal step toward democratizing access to high-performance automotive middleware,” said Laxmi Rayapudi, VP, Product Management, Qualcomm Technologies, Inc. “By aligning our Snapdragon Digital Chassis solutions with the S-CORE community, we’re empowering automakers and Tier-1 suppliers to innovate faster and deliver intelligent, connected, and safer vehicles.”

- - The S-CORE project aims to establish a vendor-neutral, open-source software stack that addresses the increasing complexity of software-defined vehicles. Qualcomm Technologies’ contribution will streamline development workflows, reduce time-to-market, and foster a vibrant ecosystem of automotive software innovation — reinforcing the community’s shared vision to enable AI-driven, software-centric mobility at global scale.

- - Snapdragon and Digital Chassis are trademarks or registered trademarks of Qualcomm Incorporated.
- Snapdragon Digital Chassis is a product of Qualcomm Technologies, Inc. and/or its subsidiaries.


-

- -

Eclipse S-CORE: "Open by Choice. Safe by Design."
-
-
- -
-
- -
-
-
- - - - Jun 12, 2025 -
-

- The Eclipse Foundation Launches the S-CORE Project: The Automotive Industry's First Open Source Core Stack for Software-Defined Vehicles -

-

- Source: Eclipse Foundation Canada -

- - Read More - -
-
-
-
- -
-
-
- - - - 18 Jun, 2025 -
-

- QNX to Serve as Foundational Operating System for Eclipse Safe Open Vehicle Core (S-CORE) Project -

-

- Source: BlackBerry Media Relations -

- - Read More - -
-
- -
-
- - Show More - -
-
-
-
- -
-
-
-
- - -
-
- -
- - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+ +
+
+
+
+ + + + Nov 12, 2025 +
+ +

+ Source: Eclipse S-CORE Project +


+ +

+ Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles +


+

+ November 12th, 2025 — The Eclipse Safe Open Vehicle Core (S-CORE) project today announced the active participation of Qualcomm Technologies, Inc. as a new member of its open-source community. + By leveraging Qualcomm Technologies Inc.’s Snapdragon® Digital Chassis™ solutions, S-CORE will run seamlessly on Qualcomm Technologies’ established high-performance hardware for future software-defined vehicles (SDVs). This collaboration further expands the reach of the S-CORE community, as a significant share of today’s safety-critical and secure automotive systems already rely on Qualcomm Technologies’ hardware.

+ + Hosted by the Eclipse Foundation under the purview of the Eclipse Software Defined Vehicle Working Group, Eclipse S-CORE, is an open-source initiative delivering a shared, safety-aligned middleware platform for high-performance automotive compute platforms. Developed by leading automotive and software companies — including Accenture GmbH, Aumovio SE, BMW Group, Elektrobit Automotive GmbH, ETAS GmbH, Mercedes-Benz Tech Innovation GmbH, Qualcomm Technologies, Inc., and Qorix GmbH — S-CORE provides a scalable, modular, and interoperable foundation for safety-critical components, reducing duplication, accelerating SDV development, and promoting industry-wide standardization.

+ + “Open collaboration is at the heart of solving the growing complexity of modern vehicle software,” said Mike Milinkovich, executive director of the Eclipse Foundation. “Through Eclipse S-CORE, we’re building a fully open, safety-aligned middleware foundation that helps automakers and suppliers focus on innovation instead of duplication. We’re delighted to welcome Qualcomm Technologies to this global community and the important work ahead.”

+ + “Qualcomm Technologies’ engagement with S-CORE represents a pivotal step toward democratizing access to high-performance automotive middleware,” said Laxmi Rayapudi, VP, Product Management, Qualcomm Technologies, Inc. “By aligning our Snapdragon Digital Chassis solutions with the S-CORE community, we’re empowering automakers and Tier-1 suppliers to innovate faster and deliver intelligent, connected, and safer vehicles.”

+ + The S-CORE project aims to establish a vendor-neutral, open-source software stack that addresses the increasing complexity of software-defined vehicles. Qualcomm Technologies’ contribution will streamline development workflows, reduce time-to-market, and foster a vibrant ecosystem of automotive software innovation — reinforcing the community’s shared vision to enable AI-driven, software-centric mobility at global scale.

+ + Snapdragon and Digital Chassis are trademarks or registered trademarks of Qualcomm Incorporated.
+ Snapdragon Digital Chassis is a product of Qualcomm Technologies, Inc. and/or its subsidiaries.


+

+ +

Eclipse S-CORE: "Open by Choice. Safe by Design."
+
+
+ +
+
+ +
+
+
+ + + + Jun 12, 2025 +
+

+ The Eclipse Foundation Launches the S-CORE Project: The Automotive Industry's First Open Source Core Stack for Software-Defined Vehicles +

+

+ Source: Eclipse Foundation Canada +

+ + Read More + +
+
+
+
+ +
+
+
+ + + + 18 Jun, 2025 +
+

+ QNX to Serve as Foundational Operating System for Eclipse Safe Open Vehicle Core (S-CORE) Project +

+

+ Source: BlackBerry Media Relations +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+ + +
+
+ +
+ + + + + diff --git a/static/reference-implementation.html b/legacy-html/reference-implementation.html similarity index 97% rename from static/reference-implementation.html rename to legacy-html/reference-implementation.html index a12f71f..9aaed46 100644 --- a/static/reference-implementation.html +++ b/legacy-html/reference-implementation.html @@ -1,498 +1,498 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
- -
-
-
-

Join us

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
-
-

- How to get in contact with S-CORE -

-

- If you want to get into contact with S-CORE, these are your primary entry points:

- - Project Mailing List:
- score-dev@eclipse.org -

- - Architectural Discussion:
- Join SDV's slack workspace and jump to - #score-project-channel-public - -

- - Eclipse S-CORE Project Office Hours:
- - Monday 13.00 - 14.00 (Weekly) - - -



- Find all our meetings:
- Open Eclipse community calendar - -

- General Information / Alignment regarding S-CORE as a basis for distributions & products:
- - Contact one of the project leads of SCORE - - -

- -
- -
-
-
-

- How to start your Contribution Journey -

- -

- Active Contributions to the S-CORE project are the basis for getting involved. - The S-CORE Project works according to the Eclipse Project Handbook and has named and elected project leads and committers - (see - Eclipse Safe Open Vehicle Core - - ).

The direction of the S-CORE project is discussed and decided in the project lead circle, - the technical direction is created and upfront in the tech lead circle. Meeting notes are transparent via the - - S-CORE GitHub Discussions. -

- -

-

- We aim to build a safety ready full stack architecture, - where components fit to each other in automotive grade Software Quality and performance. To achieve this, we follow a strict - - feature roadmap and architecture - - and a rigid - - software development process -

- -

- -

- Contributions to the S-CORE project must therefore follow the technical direction of the project and the S-CORE architecture. - For an introduction on how to contribute, please check out our - How to Contribut Guideline. -

-

- - - -
-
- -
- -


- -
-
-
-
-

- Stay Connected with S-CORE -

-

- Join the conversation, access exclusive resources, and follow us - for the latest updates. -

-
- -
- -
-
- Join Icon -
-
Join S-CORE
-

Connect With Us!

-
-
-
- - -
-
- Download Icon -
-
Stay up to date!
-

Read our latest news!

-
-
-
- -
-
-
- - LinkedIn - - - Slack - -
-
-
Follow Us
-

- Stay in the loop on all platforms! -

-
-
-
-
-
-
-
- - -
-
- -
- - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + + + +
+ +
+
+
+

Join us

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+

+ How to get in contact with S-CORE +

+

+ If you want to get into contact with S-CORE, these are your primary entry points:

+ + Project Mailing List:
+ score-dev@eclipse.org +

+ + Architectural Discussion:
+ Join SDV's slack workspace and jump to + #score-project-channel-public + +

+ + Eclipse S-CORE Project Office Hours:
+ + Monday 13.00 - 14.00 (Weekly) + + +



+ Find all our meetings:
+ Open Eclipse community calendar + +

+ General Information / Alignment regarding S-CORE as a basis for distributions & products:
+ + Contact one of the project leads of SCORE + + +

+ +
+ +
+
+
+

+ How to start your Contribution Journey +

+ +

+ Active Contributions to the S-CORE project are the basis for getting involved. + The S-CORE Project works according to the Eclipse Project Handbook and has named and elected project leads and committers + (see + Eclipse Safe Open Vehicle Core + + ).

The direction of the S-CORE project is discussed and decided in the project lead circle, + the technical direction is created and upfront in the tech lead circle. Meeting notes are transparent via the + + S-CORE GitHub Discussions. +

+ +

+

+ We aim to build a safety ready full stack architecture, + where components fit to each other in automotive grade Software Quality and performance. To achieve this, we follow a strict + + feature roadmap and architecture + + and a rigid + + software development process +

+ +

+ +

+ Contributions to the S-CORE project must therefore follow the technical direction of the project and the S-CORE architecture. + For an introduction on how to contribute, please check out our + How to Contribut Guideline. +

+

+ + + +
+
+ +
+ +


+ +
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
+ + + + + + diff --git a/static/townhalls.html b/legacy-html/townhalls.html similarity index 97% rename from static/townhalls.html rename to legacy-html/townhalls.html index d912063..e44b83f 100644 --- a/static/townhalls.html +++ b/legacy-html/townhalls.html @@ -1,382 +1,382 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
- -
-
-
-

News & Events

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
-
-
-
-
-
- -
-
-
- - - - Apr 11, 2025 -
-

- Eclipse S-CORE Townhall -

-

- Background information to S-CORE and Q&A session. -

- - Read More - -
-
- -
-
- - Show More - -
-
-
-
- -
-
-
-
-
- - -
-
- -
- - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + +
+ +
+
+
+

News & Events

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+
+
+
+
+ +
+
+
+ + + + Apr 11, 2025 +
+

+ Eclipse S-CORE Townhall +

+

+ Background information to S-CORE and Q&A session. +

+ + Read More + +
+
+ +
+
+ + Show More + +
+
+
+
+ +
+
+
+
+
+ + +
+
+ +
+ + + + + diff --git a/static/training-modules.html b/legacy-html/training-modules.html similarity index 97% rename from static/training-modules.html rename to legacy-html/training-modules.html index d4fd638..7116404 100644 --- a/static/training-modules.html +++ b/legacy-html/training-modules.html @@ -1,1471 +1,1471 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
- -
-
-
-

Join us

-
-
- -
-
-
-
- -
-
-
-
- -
-
-
- -
-
-
-

- Start Your Contribution Journey -

- -

- Dive into the S-CORE contributor community by adhering to our guiding principles. - We strive for impactful, efficient contributions that evolve the project without - redundancy while connected to the "Development Workflow”. -

-

- Learn how the stack works — from core systems to application - support. -

- -
-
- - - -
- -
-
-
-

Our Guiding Principles

-

- S-CORE is built upon core principles that champion inclusivity, efficiency, and innovation within the open source automotive software community. - Our collaborative framework welcomes contributions from everyone, paving the way for more advanced and robust solutions. - Below are the guiding principles that steer the S-CORE ecosystem -

-
-
-
- Evolve, Everybody Can Join: -

Evolve, Everybody Can Join:

-

- We recognize the power of collective intelligence and the strength of diverse contributions. - Everyone is welcome to participate, use, and join S-CORE, fostering a vibrant community united by shared goals and mutual growth. - -

-
-
- No Re-Implementation: -

No Re-Implementation:

-

- Our approach leverages existing solutions to optimize development processes. - By building on established findings and methodologies, we avoid redundancy, focusing our efforts on crafting innovative and efficient solutions. - -

-
-
- Working Model - Shift Left: -

Working Model - Shift Left:

-

- We adopt a proactive development model that prioritizes early testing and integration, - ensuring high quality and minimizing risks throughout the software lifecycle. -

-
-
- S-CORE Ecosystem: -

S-CORE Ecosystem:

-

- Our ecosystem thrives on collaboration and co-creation across various stakeholders, including universities, - industry partners, and EU commissions. We encourage dynamic contributions and collective efforts to achieve shared objectives. - -

-
-
- Engage and Get Involved: -

Engage and Get Involved:

-

- Join us on this transformative journey and explore opportunities to contribute to S-CORE's evolution. Visit our Get Involved pages for more details, - and learn about the S-CORE structure by browsing the About Us section for comprehensive insights. -

-
-
-
-
- -
-
-
-

Broaden Your Impact Beyond Code

-

- Become actively involved with S-CORE — we are committed to continuous improvement through open collaboration. - Engage with a community of innovators and explore opportunities to contribute to ongoing projects and development processes. -

-
-
-
-
-

- Community Participation -

-
- -
-

- Extend your influence beyond code. Engage with the community through participation, - and contribute to various initiatives that support S-CORE's evolution.


- Ways to Participate
- Documentation enhancements improve project understanding and usability.
- Event Participation: Involve yourself in community events, discussions and workshops.
- Specialized Working Groups: Bring in your specific knowledge on processes, safety etc.
- Feedback and Testing: Offer insights within the for project improvement.
- -

- -
-
-

- Community Engagement -

-
- -
-

- Connect and Collaborate - Engage in lively discussions within the S-CORE community, sharing insights and collaboratively tackling challenges. - The community fosters innovation and collective growth.

- A Vibrant Hub of Interaction
- Join forums and contribute to dialogue.
- Engagement Platforms
- Forums and Channels: Discuss topics, share knowledge, and evolve solutions.
- Feedback Mechanism: Receive updates and contribute insights to active projects.
- -

-
-
-
-
-
- -
- - -
-
-
-
-

- Frequently Asked Questions -

-

- Get quick answers to the most common questions about S-CORE. - Whether you're just starting or deep into development, our FAQs - cover everything from training schedules to platform usage — - helping you find what you need without the hassle. -

-
- - -
    - - - -
- - -
- -
-
-
-
- -
-

- -

-
-
- The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. -
-
-
- - -
-

- -

-
-
- Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules -
-
-
- - -
-

- -

-
-
- A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors -
-
-
- -
-

- -

-
-
- Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . -
-
-
-
- -
- -
-

- -

-
-
- Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. -
-
-
- -
-

- -

-
-
- S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . -
-
-
- -
-

- -

-
-
- Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository -
-
-
- -
-

- -

-
-
- Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . -
-
-
-
-
-
-
- - -
-
-
-
-
-

- -

-
-
- Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. -
-
-
-
-
-
-

- -

-
-
- S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. -
-
-
-
-
-
-

- -

-
-
- Change Request types include Feature, Feature Modification, Component, and Component Modification . -
-
-
-
- -
-
-

- -

-
-
- Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . -
-
-
-
- - -
-
-

- -

-
-
- GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . -
-
-
-
- - -
-
-

- -

-
-
- Technical Leads manage the platform development, control multiple modules, and handle escalations . -
-
-
-
- - -
-
-

- -

-
-
- Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . -
-
-
-
- - -
-
-

- -

-
-
- Features and components are integrated into the platform using change requests and verified through tests . -
-
-
-
- - -
-
-

- -

-
-
- Problems are reported through GitHub Issues, including documentation and resolution planning. -
-
-
-
- -
-
-
- - -
-
-
-
-
-

- -

-
-
- Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests -
-
-
-
- -
-
-

- -

-
-
- Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination -
-
-
-
- - -
-
-

- -

-
-
- Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git -
-
-
-
- - -
-
-

- -

-
-
- Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . -
-
-
-
- - -
-
-

- -

-
-
- The Contribution Request Guideline details the process of submitting new features and tools . -
-
-
-
- - -
-
-

- -

-
-
- Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . -
-
-
-
- - -
-
-

- -

-
-
- The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. -
-
-
-
- -
-
-
-
-
-
-


-
-
-
-
-

- Stay Connected with S-CORE -

-

- Join the conversation, access exclusive resources, and follow us - for the latest updates. -

-
- -
- -
-
- Join Icon -
-
Join S-CORE
-

Connect With Us!

-
-
-
- - -
-
- Download Icon -
-
Stay up to date!
-

Read our latest news!

-
-
-
- -
-
-
- - LinkedIn - - - Slack - -
-
-
Follow Us
-

- Stay in the loop on all platforms! -

-
-
-
-
-
-
-
- - -
-
- -
- - - - - - - + + + + + + + Eclipse S-CORE + + + + + + + + + + + + + + + + + +
+ +
+
+
+

Join us

+
+
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+ +
+
+
+

+ Start Your Contribution Journey +

+ +

+ Dive into the S-CORE contributor community by adhering to our guiding principles. + We strive for impactful, efficient contributions that evolve the project without + redundancy while connected to the "Development Workflow”. +

+

+ Learn how the stack works — from core systems to application + support. +

+ +
+
+ + + +
+ +
+
+
+

Our Guiding Principles

+

+ S-CORE is built upon core principles that champion inclusivity, efficiency, and innovation within the open source automotive software community. + Our collaborative framework welcomes contributions from everyone, paving the way for more advanced and robust solutions. + Below are the guiding principles that steer the S-CORE ecosystem +

+
+
+
+ Evolve, Everybody Can Join: +

Evolve, Everybody Can Join:

+

+ We recognize the power of collective intelligence and the strength of diverse contributions. + Everyone is welcome to participate, use, and join S-CORE, fostering a vibrant community united by shared goals and mutual growth. + +

+
+
+ No Re-Implementation: +

No Re-Implementation:

+

+ Our approach leverages existing solutions to optimize development processes. + By building on established findings and methodologies, we avoid redundancy, focusing our efforts on crafting innovative and efficient solutions. + +

+
+
+ Working Model - Shift Left: +

Working Model - Shift Left:

+

+ We adopt a proactive development model that prioritizes early testing and integration, + ensuring high quality and minimizing risks throughout the software lifecycle. +

+
+
+ S-CORE Ecosystem: +

S-CORE Ecosystem:

+

+ Our ecosystem thrives on collaboration and co-creation across various stakeholders, including universities, + industry partners, and EU commissions. We encourage dynamic contributions and collective efforts to achieve shared objectives. + +

+
+
+ Engage and Get Involved: +

Engage and Get Involved:

+

+ Join us on this transformative journey and explore opportunities to contribute to S-CORE's evolution. Visit our Get Involved pages for more details, + and learn about the S-CORE structure by browsing the About Us section for comprehensive insights. +

+
+
+
+
+ +
+
+
+

Broaden Your Impact Beyond Code

+

+ Become actively involved with S-CORE — we are committed to continuous improvement through open collaboration. + Engage with a community of innovators and explore opportunities to contribute to ongoing projects and development processes. +

+
+
+
+
+

+ Community Participation +

+
+ +
+

+ Extend your influence beyond code. Engage with the community through participation, + and contribute to various initiatives that support S-CORE's evolution.


+ Ways to Participate
+ Documentation enhancements improve project understanding and usability.
+ Event Participation: Involve yourself in community events, discussions and workshops.
+ Specialized Working Groups: Bring in your specific knowledge on processes, safety etc.
+ Feedback and Testing: Offer insights within the for project improvement.
+ +

+ +
+
+

+ Community Engagement +

+
+ +
+

+ Connect and Collaborate + Engage in lively discussions within the S-CORE community, sharing insights and collaboratively tackling challenges. + The community fosters innovation and collective growth.

+ A Vibrant Hub of Interaction
+ Join forums and contribute to dialogue.
+ Engagement Platforms
+ Forums and Channels: Discuss topics, share knowledge, and evolve solutions.
+ Feedback Mechanism: Receive updates and contribute insights to active projects.
+ +

+
+
+
+
+
+ +
+ + +
+
+
+
+

+ Frequently Asked Questions +

+

+ Get quick answers to the most common questions about S-CORE. + Whether you're just starting or deep into development, our FAQs + cover everything from training schedules to platform usage — + helping you find what you need without the hassle. +

+
+ + +
    + + + +
+ + +
+ +
+
+
+
+ +
+

+ +

+
+
+ The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. +
+
+
+ + +
+

+ +

+
+
+ Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules +
+
+
+ + +
+

+ +

+
+
+ A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors +
+
+
+ +
+

+ +

+
+
+ Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . +
+
+
+
+ +
+ +
+

+ +

+
+
+ Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. +
+
+
+ +
+

+ +

+
+
+ S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . +
+
+
+ +
+

+ +

+
+
+ Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository +
+
+
+ +
+

+ +

+
+
+ Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . +
+
+
+
+
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. +
+
+
+
+
+
+

+ +

+
+
+ S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. +
+
+
+
+
+
+

+ +

+
+
+ Change Request types include Feature, Feature Modification, Component, and Component Modification . +
+
+
+
+ +
+
+

+ +

+
+
+ Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . +
+
+
+
+ + +
+
+

+ +

+
+
+ GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . +
+
+
+
+ + +
+
+

+ +

+
+
+ Technical Leads manage the platform development, control multiple modules, and handle escalations . +
+
+
+
+ + +
+
+

+ +

+
+
+ Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . +
+
+
+
+ + +
+
+

+ +

+
+
+ Features and components are integrated into the platform using change requests and verified through tests . +
+
+
+
+ + +
+
+

+ +

+
+
+ Problems are reported through GitHub Issues, including documentation and resolution planning. +
+
+
+
+ +
+
+
+ + +
+
+
+
+
+

+ +

+
+
+ Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests +
+
+
+
+ +
+
+

+ +

+
+
+ Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination +
+
+
+
+ + +
+
+

+ +

+
+
+ Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git +
+
+
+
+ + +
+
+

+ +

+
+
+ Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Contribution Request Guideline details the process of submitting new features and tools . +
+
+
+
+ + +
+
+

+ +

+
+
+ Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . +
+
+
+
+ + +
+
+

+ +

+
+
+ The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. +
+
+
+
+ +
+
+
+
+
+
+


+
+
+
+
+

+ Stay Connected with S-CORE +

+

+ Join the conversation, access exclusive resources, and follow us + for the latest updates. +

+
+ +
+ +
+
+ Join Icon +
+
Join S-CORE
+

Connect With Us!

+
+
+
+ + +
+
+ Download Icon +
+
Stay up to date!
+

Read our latest news!

+
+
+
+ +
+
+
+ + LinkedIn + + + Slack + +
+
+
Follow Us
+

+ Stay in the loop on all platforms! +

+
+
+
+
+
+
+
+ + +
+
+ +
+ + + + + + + From afbd80c1356a4b422a4297afa2dcbdd41f9c1c85 Mon Sep 17 00:00:00 2001 From: Christian Heissenberger Date: Tue, 17 Feb 2026 18:33:44 +0100 Subject: [PATCH 2/4] refactor(hugo): extract shared header/footer partials and deduplicate page content - add shared partials: - layouts/partials/site-header.html - layouts/partials/site-footer.html - update layouts/_default/single.html to include shared partials - remove duplicated header/footer/loading markup from non-home content pages - move page-specific header state into front matter: - active_nav - header_class - header_title - breadcrumb_html - keep existing styles/scripts and page body content unchanged --- content/about-us.md | 175 +++-------------------- content/articles.md | 183 ++++-------------------- content/blog-details.md | 214 ++++------------------------ content/docs.md | 172 +++------------------- content/faq.md | 174 +++------------------- content/how_to_contribute.md | 170 +++------------------- content/news.md | 183 ++++-------------------- content/press_releases.md | 184 ++++-------------------- content/reference-implementation.md | 189 ++++-------------------- content/townhalls.md | 184 ++++-------------------- content/training-modules.md | 185 ++++-------------------- layouts/_default/single.html | 6 + layouts/partials/site-footer.html | 43 ++++++ layouts/partials/site-header.html | 116 +++++++++++++++ 14 files changed, 425 insertions(+), 1753 deletions(-) create mode 100644 layouts/partials/site-footer.html create mode 100644 layouts/partials/site-header.html diff --git a/content/about-us.md b/content/about-us.md index 213f0fd..cd11976 100644 --- a/content/about-us.md +++ b/content/about-us.md @@ -20,115 +20,28 @@ extra_scripts: - "js/about-us.js" - "js/contributor-slider.js" - "js/loading.js" ---- - -
- -
-
-
-

About Us

-
-
- -
-
-
-
+ About Us + +--- -
+
@@ -597,50 +510,4 @@ extra_scripts:
- - -
-
- -
+
diff --git a/content/articles.md b/content/articles.md index 52e854b..637055b 100644 --- a/content/articles.md +++ b/content/articles.md @@ -13,121 +13,32 @@ extra_scripts: - "js/jquery-3.7.1.min.js" - "js/bootstrap.min.js" - "js/loading.js" ---- - -
- -
-
-
-

News & Events

-
-
- -
-
-
-
+ Articles + +--- -
+
@@ -237,50 +148,4 @@ extra_scripts:
- - -
-
- -
+
diff --git a/content/blog-details.md b/content/blog-details.md index 06f1d2e..1cd1865 100644 --- a/content/blog-details.md +++ b/content/blog-details.md @@ -16,150 +16,34 @@ extra_scripts: - "js/owl.carousel.min.js" - "js/news.js" - "js/loading.js" ---- - -
- -
-
-
-

- Unlocking Innovation: The Power of Open Source Software -

-
-
- -
-
-
-
+ + Unlocking Innovation: The Power of Open Source Software + + +--- -
+
@@ -310,50 +194,4 @@ extra_scripts:
- - -
-
- -
+
diff --git a/content/docs.md b/content/docs.md index abfdf58..b8b3dbe 100644 --- a/content/docs.md +++ b/content/docs.md @@ -15,112 +15,28 @@ extra_scripts: - "js/panzoom.min.js" - "js/zoom.js" - "js/loading.js" ---- - -
- -
-
-
-

Docs

-
-
- -
-
-
-
+ Docs + +--- -
+
- - -
-
- -
+
diff --git a/content/faq.md b/content/faq.md index fb1fe00..099f3a8 100644 --- a/content/faq.md +++ b/content/faq.md @@ -19,115 +19,28 @@ extra_scripts: - "js/swiper-bundle.min.js" - "js/swiper.js" - "js/loading.js" +use_shared_header: true +use_shared_footer: true +active_nav: "faq" +header_class: "campus-page-header" +header_title: "Frequently Asked Questions" +breadcrumb_html: | + +
  • + Home +
    • +
  • + FAQ +
    • --- -
    - -
    -
    -
    -

    Frequently Asked Questions

    -
    -
    - -
    -
    -
    -
    - -
    +
    @@ -1039,49 +952,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/how_to_contribute.md b/content/how_to_contribute.md index 354f3e7..0b17643 100644 --- a/content/how_to_contribute.md +++ b/content/how_to_contribute.md @@ -18,110 +18,28 @@ extra_scripts: - "js/zoom.js" - "js/about-us.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    How To Contribute

    -
    -
    - -
    -
    -
    -
    + How To Contribute + +--- -
    +
    @@ -568,50 +486,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/news.md b/content/news.md index 4cc21b0..38db137 100644 --- a/content/news.md +++ b/content/news.md @@ -13,121 +13,32 @@ extra_scripts: - "js/jquery-3.7.1.min.js" - "js/bootstrap.min.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    + Conferences + +--- -
    +
    @@ -381,50 +292,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/press_releases.md b/content/press_releases.md index 43c2164..0b2f392 100644 --- a/content/press_releases.md +++ b/content/press_releases.md @@ -13,122 +13,32 @@ extra_scripts: - "js/jquery-3.7.1.min.js" - "js/bootstrap.min.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    + Press Releases + +--- -
    +
    @@ -270,50 +180,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/reference-implementation.md b/content/reference-implementation.md index e150d86..36803cb 100644 --- a/content/reference-implementation.md +++ b/content/reference-implementation.md @@ -18,123 +18,34 @@ extra_scripts: - "js/bootstrap.min.js" - "js/campus.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    Join us

    -
    -
    - -
    -
    -
    -
    + How to Contribute + +--- -
    +
    @@ -341,50 +252,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/townhalls.md b/content/townhalls.md index 61b70e8..c2a571d 100644 --- a/content/townhalls.md +++ b/content/townhalls.md @@ -13,122 +13,32 @@ extra_scripts: - "js/jquery-3.7.1.min.js" - "js/bootstrap.min.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    + Townhalls + +--- -
    +
    @@ -205,50 +115,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/content/training-modules.md b/content/training-modules.md index 0378952..ed7e4c3 100644 --- a/content/training-modules.md +++ b/content/training-modules.md @@ -19,120 +19,34 @@ extra_scripts: - "js/swiper-bundle.min.js" - "js/swiper.js" - "js/loading.js" ---- - -
    - -
    -
    -
    -

    Join us

    -
    -
    - -
    -
    -
    -
    + How To Collaborate + +--- -
    +
    @@ -1211,49 +1125,4 @@ extra_scripts:
    - - -
    -
    - -
    +
    diff --git a/layouts/_default/single.html b/layouts/_default/single.html index 437933e..0bb73d8 100644 --- a/layouts/_default/single.html +++ b/layouts/_default/single.html @@ -1,7 +1,13 @@ {{ define "main" }} +{{ if .Params.use_shared_header }} +{{ partial "site-header.html" . }} +{{ end }} {{ if .Params.render_raw }} {{ .RawContent | safeHTML }} {{ else }} {{ .Content }} {{ end }} +{{ if .Params.use_shared_footer }} +{{ partial "site-footer.html" . }} +{{ end }} {{ end }} diff --git a/layouts/partials/site-footer.html b/layouts/partials/site-footer.html new file mode 100644 index 0000000..958b931 --- /dev/null +++ b/layouts/partials/site-footer.html @@ -0,0 +1,43 @@ + +
    + +
    diff --git a/layouts/partials/site-header.html b/layouts/partials/site-header.html new file mode 100644 index 0000000..2048a5c --- /dev/null +++ b/layouts/partials/site-header.html @@ -0,0 +1,116 @@ +{{ $active := .Params.active_nav | default "" }} +{{ $headerClass := .Params.header_class | default "about-page-header" }} +{{ $headerTitle := .Params.header_title | default .Title }} +
    + +
    +
    +
    +

    {{ $headerTitle }}

    +
    +
    + +
    +
    +
    +
    From 6ca93d7e7745b60ff8bab6a46cd04df1144cf6d4 Mon Sep 17 00:00:00 2001 From: Christian Heissenberger Date: Tue, 17 Feb 2026 18:41:07 +0100 Subject: [PATCH 3/4] remove backup html --- legacy-html/about-us.html | 751 ----------- legacy-html/articles.html | 414 ------ legacy-html/blog-details.html | 442 ------- legacy-html/docs.html | 372 ------ legacy-html/faq.html | 1234 ----------------- legacy-html/how_to_contribute.html | 722 ---------- legacy-html/index.html | 913 ------------- legacy-html/news.html | 560 -------- legacy-html/press_releases.html | 448 ------- legacy-html/reference-implementation.html | 498 ------- legacy-html/townhalls.html | 382 ------ legacy-html/training-modules.html | 1471 --------------------- 12 files changed, 8207 deletions(-) delete mode 100644 legacy-html/about-us.html delete mode 100644 legacy-html/articles.html delete mode 100644 legacy-html/blog-details.html delete mode 100644 legacy-html/docs.html delete mode 100644 legacy-html/faq.html delete mode 100644 legacy-html/how_to_contribute.html delete mode 100644 legacy-html/index.html delete mode 100644 legacy-html/news.html delete mode 100644 legacy-html/press_releases.html delete mode 100644 legacy-html/reference-implementation.html delete mode 100644 legacy-html/townhalls.html delete mode 100644 legacy-html/training-modules.html diff --git a/legacy-html/about-us.html b/legacy-html/about-us.html deleted file mode 100644 index e998c7e..0000000 --- a/legacy-html/about-us.html +++ /dev/null @@ -1,751 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    About Us

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -

    Who We Are

    -

    - We’re a collaborative and ever-growing community of automotive - experts, technology partners, developers, and innovators - united under the Eclipse Foundation. Together, we’re shaping - the future of automotive software by building open, safe, and - scalable solutions. -

    - -
    -
    -
    - Vision Icon -
    -
    -

    Our Vision

    -

    - “Build the best automotive runtime solution – ONLY - ONCE!” -

    -
    -
    - -
    -
    - Vision Icon -
    -
    -

    Our Mission

    -

    - Unite the automotive software community around
    - ONE OPEN-SOURCE CORE” -
    -
    - -

    -

    - Reuse “Stop - reinventing the wheel” -

    -

    - Reduce - “…complexity, effort,…” -

    -

    - Evolve “Build on a - future-proof foundation” -

    -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    - -
    -
    -
    -

    Our Contributors

    -

    - S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

    -
    -
    -
    -
    -
    -
    - Member 2 -
    -
    -
    -
    - Member 3 -
    -
    -
    -
    - Member 4 -
    -
    -
    -
    - Member 5 -
    -
    -
    -
    - Member 6 -
    -
    -
    -
    - Member 1 -
    -
    -
    -
    - Member 7 -
    -
    -
    -
    - Member 8 -
    -
    -
    -
    - Member 9 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    - - -
    -
    -
    -
    - -
    -
    -
    -

    S-CORE Community Structure

    -

    - S-CORE brings together members, technical leads, and specialized - teams to define and manage modules, propose requirements, and - ensure the platform evolves with clarity and purpose. -

    -
    -
    -
    -
    - -
    -
    -
    -
    -
    - -
    -
    -
    -

    Steering Committees

    -

    - Every core member can name a project lead. Project leads are - representatives of their entities, and jointly they´re steering - the project. Because of the project´s size, an additional role - “technical leads” was introduced in S-Core. Each project lead can - nominate one technical lead to support in operational topics like - project planning. In order to run the project, there are two major - committees: -

    -
    -
    -
    -
    -

    - Technical Lead Circle -

    -
    - -
    -

    - The Technical Steering Committee (TSC) is responsible for the - overall technical direction of the project. It ensures that - the project remains aligned with its goals and objectives, and - it provides guidance on technical decisions. -

    -
    -
    -

    - Project Lead Circle -

    -
    - -
    -

    - The Project Management Committee (PMC) is responsible for the - day-to-day management of the project. It oversees the - project's progress, manages resources, and ensures that - deadlines are met. -

    -
    -
    -
    -
    -
    - -
    -
    -
    -

    Communities

    -

    - Every S-CORE community has its focus topic, and every S-CORE - member is free to join, discuss and to shape the outcome. -

    -
    -
    -
    - Software Architecture -

    Software Architecture

    -

    - - In this community, the overall software architecture of our - stack is planned. Join here to get the recent information about - next features for S-CORE. . -

    -
    -
    - Software Development Process -

    Software Development Process

    -

    - Due to our goal to deliver a stack which is safety certifiable, - we need well defined software development processes. This - community is continuously designing & improving our processes. -

    -
    -
    - Infrastructure -

    Infrastructure

    -

    - To enable a fast and reliable development, this community is - setting up the build infrastructure, the tooling, process - enabling, the CI/CD pipelines, and more… -

    -
    -
    - Testing -

    Testing

    -

    - To meet our quality goals, S-CORE needs to be tested – In this - community, experienced test managers and testers are ensuring - exactly this. -

    -
    -
    - Marketing & Communication -

    Marketing & Communication

    -

    - S-CORE can only be successful, when more and more members are - joining! – This community ensures, that the great results - -provided by S-CORE teams- are communicated to the automotive - community. -

    -
    -
    -
    -
    - -
    -
    -
    -

    - Community Voices – What Our Members Say -

    -

    - Community Voices captures insights and experiences from our - members, highlighting their role in shaping the platform and - driving innovation within the S-CORE ecosystem. Their feedback - reflects the impact, collaboration, and shared vision that fuel - our open-source journey. -

    -
    -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    Mike Milinkovich
    -
    Executive Director of the Eclipse Foundation
    -
    -
    - -
    -
    -

    - With S-CORE, we’re providing developers with a reliable, safety-grade runtime environment that allows the industry to focus on innovation while reducing duplication of effort. This project offers the entire sector a jumpstart in building the custom solutions that will define the future of mobility -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Anton Krivoborodov
    -
    Technical Project Lead - BMW
    -
    -
    -
    -
    -

    - With S-Core, we can shape the future of the Safe-POSIX platform with the support of a strong open-source community. -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Markus Schupfner
    -
    CEO Qorix
    -
    -
    -
    -
    -

    - S-CORE is more than a project – it’s the foundation of an open, collaborative future for automotive software. As a founding contributor and distributor, Qorix is proud to shape a platform that turns shared challenges into shared progress. -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Sven Kappel
    -
    Head of ETAS.NEXT
    -
    -
    -
    -
    -

    - At ETAS, we believe in the transformative potential of open collaboration in driving software innovation. - As a founding member of Eclipse S-CORE, we are committed to shaping a robust platform that fosters seamless integration, - sustainable development processes, and cutting-edge solutions empowering tomorrow's automotive software -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Lars Bauhofer
    -
    Product Program Manager - Qorix
    -
    -
    -
    -
    -

    - S-CORE makes collaboration tangible. From architecture workshops to release planning – we’re actively building the stack, aligning teams, and turning code into common ground. -

    -
    -
    -
    -
    -
    -
    - -
    -
    -
    Dr. Nico Hartmann
    -
    CTO - Qorix
    -
    -
    -
    -
    -

    - Contributing to S-CORE means contributing to what matters: deterministic execution, safety by design, and reusable infrastructure. We bring the middleware expertise – and we’re here to make it usable at scale. -

    -
    -
    -
    - - -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - - - - - diff --git a/legacy-html/articles.html b/legacy-html/articles.html deleted file mode 100644 index 0f03a6f..0000000 --- a/legacy-html/articles.html +++ /dev/null @@ -1,414 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    - - - - Nov 6th, 2025 -
    -

    - Eclipse S-CORE 0.5 – What’s inside the first public release. -

    -

    - Source: Eclipse SDV WG Linkedin

    -

    -

    - The first version of Eclipse S-CORE (Safe Open Vehicle Core) lays the groundwork for open, safety-ready automotive software.
    - -

    - - Read More and Discuss - -
    -
    -
    -
    - -
    -
    -
    - - - - Sept 30, 2025 -
    -

    - Eclipse S-CORE: A new approach to building automotive software together -

    -

    - by Valerie Hasler and Memsud Godinjak -

    - - Read More - -
    -
    - -
    -
    - - Show More - -
    -
    -
    -
    - -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - diff --git a/legacy-html/blog-details.html b/legacy-html/blog-details.html deleted file mode 100644 index 0e4f977..0000000 --- a/legacy-html/blog-details.html +++ /dev/null @@ -1,442 +0,0 @@ - - - - - - - S-CORE - - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    - Unlocking Innovation: The Power of Open Source Software -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    -
    - - - - 14 Feb, 2024 -
    - -

    - One of the greatest advantages of open source software is its - community-driven nature, which brings together developers from - across the world. These contributors often come from vastly - different backgrounds, cultures, and levels of experience — yet - they unite around a shared goal: building better software. This - global collaboration leads to diverse perspectives, creative - problem-solving, and faster identification of bugs or security - flaws. Since the code is open and accessible, anyone can - contribute, whether it’s by writing new features, improving - documentation, or testing for issues. This open process allows the - software to evolve rapidly, often outpacing traditional - closed-source development. With thousands of eyes reviewing and - refining the code, quality tends to increase over time. The sense - of shared ownership among contributors also builds trust and - commitment within the community. Unlike proprietary systems, where - innovation is limited to internal teams, open source benefits from - decentralized innovation at scale. It’s this collaborative spirit - that turns open source from just code into a movement — one that’s - shaping the future of technology. -

    -
    - -
    -
    -

    Recommended

    -
    -
    -
    -
    -
    -
    - -
    -
    -

    Next Eclipse Community Event

    -

    - Next Eclipse Community Event, June 4th 2025 in Starnberg -

    -
    -
    - Learn More -
    - -
    -     -
    -
    - -
    -
    - -
    -
    -

    Next Eclipse Community Event

    -

    - Next Eclipse Community Event, June 4th 2025 in Starnberg -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    -
    - -
    -
    -

    Next Eclipse Community Event

    -

    - Next Eclipse Community Event, June 4th 2025 in Starnberg -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    -
    - -
    -
    -

    Next Eclipse Community Event

    -

    - Next Eclipse Community Event, June 4th 2025 in Starnberg -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    -
    - -
    -
    -

    Next Eclipse Community Event

    -

    - Next Eclipse Community Event, June 4th 2025 in Starnberg -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    - - -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - - diff --git a/legacy-html/docs.html b/legacy-html/docs.html deleted file mode 100644 index 1d2b38e..0000000 --- a/legacy-html/docs.html +++ /dev/null @@ -1,372 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    Docs

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    -

    Eclipse S-Core Building Blocks

    - -
    -
    - - S-CORE v0.5 module -
    -
    - - - S-CORE v1.0 module -
    -
    -
    - -
    -
    -

    - This section provides a schematic overview of the technical building blocks that form the foundation of our platform. - Here, you’ll find a clear differentiation between S-CORE modules available in version 0.5 and those planned for version 1.0.
    -

    -
    -
    - -
    -
    -
    -
    -
    -
    - -
    -
    -
    -

    S-Core Project Roadmap

    -
    -
    -
    -

    - Get athe development and release timeline of Eclipse S-CORE. It shows the key phases that shape the platform’s evolution—starting from early development to achieving maturity and stability. - Gain an understanding of how each phase contributes to delivering a scalable and reliable platform. -

    -
    -
    - -
    -
    -
    -
    -
    -
    - -
    -
    -
    -

    Build & Documentation Toolchain

    -

    - The build system uses Bazel to automate workflows like repository - cloning, software builds, documentation generation, testing, and - more. Documentation is managed with Sphinx and sphinx-needs, while - diagrams are created using PlantUML and draw.io. Supported - languages include C++ and Rust, with testing handled by - gtest/gmock. -

    -
    -
    -
    -
    -
    - -
    -
    -

    - Check out our GitHub Project - - -
    -
    -
    - - -
    -
    - -
    - - - - - - - diff --git a/legacy-html/faq.html b/legacy-html/faq.html deleted file mode 100644 index 8fa9654..0000000 --- a/legacy-html/faq.html +++ /dev/null @@ -1,1234 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    Frequently Asked Questions

    -
    -
    - -
    -
    -
    -
    - -
    - - -
    -
    -
    -
    - -

    - Get quick answers to the most common questions about S-CORE. Whether you're just starting or deep into development, - our FAQs cover everything from training schedules to platform usage — helping you find what you need without the hassle. -

    - - -
    -
    - - - -
    - -
    -
    - - - -
      - - - -
    - - -
    - -
    -
    -
    -
    - -
    -

    - -

    -
    -
    - The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. -
    -
    -
    - - -
    -

    - -

    -
    -
    - Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules -
    -
    -
    - - -
    -

    - -

    -
    -
    - A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors -
    -
    -
    - -
    -

    - -

    -
    -
    - Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . -
    -
    -
    -
    - -
    - -
    -

    - -

    -
    -
    - Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. -
    -
    -
    - -
    -

    - -

    -
    -
    - S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . -
    -
    -
    - -
    -

    - -

    -
    -
    - Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository -
    -
    -
    - -
    -

    - -

    -
    -
    - Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . -
    -
    -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. -
    -
    -
    -
    -
    -
    -

    - -

    -
    -
    - S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. -
    -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Change Request types include Feature, Feature Modification, Component, and Component Modification . -
    -
    -
    -
    - -
    -
    -

    - -

    -
    -
    - Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Technical Leads manage the platform development, control multiple modules, and handle escalations . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Features and components are integrated into the platform using change requests and verified through tests . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Problems are reported through GitHub Issues, including documentation and resolution planning. -
    -
    -
    -
    - -
    -
    -
    - - -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests -
    -
    -
    -
    - -
    -
    -

    - -

    -
    -
    - Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - The Contribution Request Guideline details the process of submitting new features and tools . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -


    -
    -
    -
    -
    -

    - Stay Connected with S-CORE -

    -

    - Join the conversation, access exclusive resources, and follow us - for the latest updates. -

    -
    - -
    - -
    -
    - Join Icon -
    -
    Join S-CORE
    -

    Connect With Us!

    -
    -
    -
    - - -
    -
    - Download Icon -
    -
    Stay up to date!
    -

    Read our latest news!

    -
    -
    -
    - -
    -
    -
    - - LinkedIn - - - Slack - -
    -
    -
    Follow Us
    -

    - Stay in the loop on all platforms! -

    -
    -
    -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - - diff --git a/legacy-html/how_to_contribute.html b/legacy-html/how_to_contribute.html deleted file mode 100644 index f4304ed..0000000 --- a/legacy-html/how_to_contribute.html +++ /dev/null @@ -1,722 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    How To Contribute

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -

    Who We Are

    -

    - We’re a collaborative and ever-growing community of automotive - experts, technology partners, developers, and innovators - united under the Eclipse Foundation. Together, we’re shaping - the future of automotive software by building open, safe, and - scalable solutions. -

    - -
    -
    -
    - Vision Icon -
    -
    -

    Our Vision

    -

    - “Build the best automotive runtime solution – ONLY - ONCE!” -

    -
    -
    - -
    -
    - Vision Icon -
    -
    -

    Our Mission

    -

    - Unite the automotive software community around ONE - OPEN-SOURCE CORE” -

    -

    - Reuse “Stop - reinventing the wheel” -

    -

    - Reduce - “…complexity, effort,…” -

    -

    - Evolve “Build on a - future-proof foundation” -

    -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    - -
    -
    -
    -

    Our Contributors

    -

    - S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

    -
    -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -

    S-CORE Community Structure

    -

    - S-CORE brings together members, technical leads, and specialized - teams to define and manage modules, propose requirements, and - ensure the platform evolves with clarity and purpose. -

    -
    -
    -
    -
    - -
    -
    -
    -
    -
    - -
    -
    -
    -

    Steering Committees

    -

    - Every core member can name a project lead. Project leads are - representatives of their entities, and jointly they´re steering - the project. Because of the project´s size, an additional role - “technical leads” was introduced in S-Core. Each project lead can - nominate one technical lead to support in operational topics like - project planning. In order to run the project, there are two major - committees: -

    -
    -
    -
    -
    -

    - Technical Lead Circle -

    -
    - -
    -

    - The Technical Steering Committee (TSC) is responsible for the - overall technical direction of the project. It ensures that - the project remains aligned with its goals and objectives, and - it provides guidance on technical decisions. -

    -
    -
    -

    - Project Lead Circle -

    -
    - -
    -

    - The Project Management Committee (PMC) is responsible for the - day-to-day management of the project. It oversees the - project's progress, manages resources, and ensures that - deadlines are met. -

    -
    -
    -
    -
    -
    - -
    -
    -
    -

    Communities

    -

    - Every S-CORE community has its focus topic, and every S-CORE - member is free to join, discuss and to shape the outcome. -

    -
    -
    -
    - Software Architecture -

    Software Architecture

    -

    - In this community, the overall software architecture of our - stack is planned. Join here to get the recent information about - next features for S-CORE. . -

    -
    -
    - Software Development Process -

    Software Development Process

    -

    - Due to our goal to deliver a stack which is safety certifiable, - we need well defined software development processes. This - community is continuously designing & improving our processes. -

    -
    -
    - Infrastructure -

    Infrastructure

    -

    - To enable a fast and reliable development, this community is - setting up the build infrastructure, the tooling, process - enabling, the CI/CD pipelines, and more… -

    -
    -
    - Testing -

    Testing

    -

    - To meet our quality goals, S-CORE needs to be tested – In this - community, experienced test managers and testers are ensuring - exactly this. -

    -
    -
    - Marketing & Communication -

    Marketing & Communication

    -

    - S-CORE can only be successful, when more and more members are - joining! – This community ensures, that the great results - -provided by S-CORE teams- are communicated to the automotive - community. -

    -
    -
    -
    -
    - -
    -
    -
    -

    - Community Voices – What Our Members Say -

    -

    - Community Voices captures insights and experiences from our - members, highlighting their role in shaping the platform and - driving innovation within the S-CORE ecosystem. Their feedback - reflects the impact, collaboration, and shared vision that fuel - our open-source journey. -

    -
    -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    Serhiy Hipskyy
    -
    CEO Universal
    -
    -
    -
    -
    - -
    -
    - -
    -
    - -
    - -
    - -
    -
    - -
    -
    -
    -
    -

    - On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Serhiy Hipskyy
    -
    CEO Universal
    -
    -
    -
    -
    - -
    -
    - -
    -
    - -
    - -
    - -
    -
    - -
    -
    -
    -
    -

    - On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Serhiy Hipskyy
    -
    CEO Universal
    -
    -
    -
    -
    - -
    -
    - -
    -
    - -
    - -
    - -
    -
    - -
    -
    -
    -
    -

    - On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    Serhiy Hipskyy
    -
    CEO Universal
    -
    -
    -
    -
    - -
    -
    - -
    -
    - -
    - -
    - -
    -
    - -
    -
    -
    -
    -

    - On the other hand, we denounce with righteous indignation - and dislike men who are so beguiled and. -

    -
    -
    -
    - - -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - - - - diff --git a/legacy-html/index.html b/legacy-html/index.html deleted file mode 100644 index f150e3c..0000000 --- a/legacy-html/index.html +++ /dev/null @@ -1,913 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    - -
    -
    -
    -
    -

    - From Proprietary - To Open Source -

    -

    - The industry has long tackled software challenges - independently – often duplicating efforts and building - closed, incompatible systems.

    - S-CORE changes this by uniting OEMs, suppliers and - developers around a common SW-platform. The goal of S-CORE - is to reduce complexity, promote re-use, gain speed & - enable scalable innovation. -

    -
    -

    - Join our global community building a common, - safety-critical runtime foundation for automotive - innovation. -

    -
    - Explore the projects - Get Involved - Visit Our Github -
    -
    -
    -
    - 3D illustration of a futuristic car with floating cubes -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -

    Latest News:
    S-CORE Release v0.5 - beta is available

    -
    - -
    -
    -
    -
    - -
    -
    Release Notes
    -

    - Find out more about the release and all components integrated and available. -
    - - - Release Notes - - -

    - -
    -
    - -
    -
    -
    - -
    -
    How to get started
    -

    - Follow this Guide to start you development with Eclipse S-CORE today! -
    - - - How to get started - -

    -
    -
    - -
    -
    -
    - -
    -
    Get in touch
    -

    - Get in touch with us on and discuss with the developers on Slack or via E-mail! -
    - - - Get in touch - - -

    -
    -
    - - -
    - -
    -
    -
    -
    -
    -
    -
    -

    Latest News & Events

    - - Discover more News/Events - - -
    - -
    -
    -
    - -
    -
    - -
    -
    -

    Coming soon: Eclipse S-CORE 0.5

    -

    - The automotive industry’s first open, safety-ready software stack is almost here.
    - Eclipse S-CORE brings the community one step closer to a shared foundation for software-defined vehicles. -

    -

    Eclipse S-CORE:
    - Open by Choice. Safe by Design.

    -
    -
    - Learn More -
    - -
    -     -
    -
    - -
    -
    - -
    -
    -

    Nov 12, 2025

    -

    - Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    -
    - -
    -
    -

    Eclipse Community Meetup, Japan/ Yokohama

    -

    - Introduction and update about recent S-CORE developments. -

    -
    -
    - Learn More -
    - -
    -     -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    -

    S-CORE In A Nutshell

    -
    -
    -

    Together...

    -

    S-CORE began in 2024 with five initial members: - Accenture, BMW, ETAS, Mercedes-Benz, and Qorix – “the coalition of the willing”.
    - Since then, both active participation and global interest have grown significantly.

    -
    -
    -
    -
    - -
    -

    OEMS

    -
    -
    - -
    -
    -
    - -
    -

    Tiers

    -
    -
    - -
    -
    -
    - -
    -

    SW-Supplier

    -
    -
    - -
    -
    -
    - -
    -

    Service Provider

    -
    -
    -
    - -

    ...we´re shaping an open-source and code-based SW-platform...

    -

    S-CORE solves the requirements of a future SDV with a collaborative, open, and modular approach. - Developed by and for the industry, it delivers a robust core architecture that reduces integration effort, - enhances safety, and accelerates development.
    - Rather than fostering competition through proprietary, - stacks, S-CORE enables collaboration through standardisation.

    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    - -
    -

    Open Source

    -
    -
    - -
    -
    -
    - -
    -

    Code Based

    -
    -
    -
    - -

    ...for "dynamic core" components with strict requirements of a future SDV.

    -

    - S-CORE bridges the OS–application gap and is being developed as a modular, - standards-oriented middleware. The goal: enable predictable, safe, and reusable execution - environments across diverse hardware and ECU types – without prescribing a fixed implementation.
    - - Its architecture is designed for safety-critical contexts – especially ADAS, Body, and Chassis – and supports compliance with ISO 26262 and ISO/SAE 21434. -

    -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    - -
    -

    Quality (ASPICE)

    -
    -
    - -
    -
    -
    - -
    -

    Safety (ISO 26262)

    -
    -
    - -
    -
    -
    - -
    -

    Security (ISO 21434)

    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -

    - The focus of S-CORE are safety-critical in-car components -

    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -

    - S-CORE aims to build-up all SW-platform layers below the - application layer and above the board support package of the - SoC. -

    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -

    - What are the deliverables of S-CORE? -

    -

    - Besides describing the SW-platform, S-CORE provides a huge - load of complementary deliverables. -

    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    -

    Why is S-CORE Needed

    -
    -
    - -
    -
    -
    -
    - -
    -
    Common Stack & Collaboration
    -

    - A common full-stack software runtime addressing shared - industry problems through joint solutions. -

    -
    -
    - -
    -
    -
    - -
    -
    Speed
    -

    - Accelerates development by working in open source with - code-centric, iterative methods. -

    -
    -
    - -
    -
    -
    - -
    -
    Abstraction & Extensibility
    -

    - Decouples HW and SW with flexible layers and enables - project-specific extensions of the stack. -

    -
    -
    - -
    -
    -
    - -
    -
    Quality & Efficiency
    -

    - A lean, no-frills solution using modern languages, - readable specs, and safe open source processes. -

    -
    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -

    Our Contributors

    -

    - S-CORE is backed by a diverse network of leading automotive - companies, technology providers, and open-source contributors. - These members play a vital role in driving innovation, shaping the - platform’s direction, and ensuring its success across real-world - applications. -

    -
    -
    -
    -
    -
    -
    - Member 1 -
    -
    -
    -
    - Member 2 -
    -
    -
    -
    - Member 3 -
    -
    -
    -
    - Member 4 -
    -
    -
    -
    - Member 5 -
    -
    -
    -
    - Member 6 -
    -
    -
    -
    - Member 7 -
    -
    -
    -
    - Member 8 -
    -
    -
    -
    - Member 9 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    -
    - Member 10 -
    -
    -
    - - -
    -
    -
    -
    -
    - - - -
    - -
    -
    -
    - - -
    - -
    - - - - - - - - - diff --git a/legacy-html/news.html b/legacy-html/news.html deleted file mode 100644 index b0e3b14..0000000 --- a/legacy-html/news.html +++ /dev/null @@ -1,560 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    - -
    -
    -
    - -
    -
    Upcoming Conferences
    - - - -
    - -
    - -
    - -
    -
    - - - - 5 Feb, 2026 -
    -

    - SIA 2026 | Future Proofing SDV Study Day,
    Paris, France -

    -

    - Presenter: Björn Reistel (ETAS)
    - Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" -

    - - Read More - -
    -
    - - - -
    - -
    - -
    - -
    -
    - - - - 21-23 Apr, 2026 -
    -

    - OCX 2026 | Open Community Exceprience,
    Brussels, Belgium -

    -

    - Presenter: tbd.
    - Topic: S-CORE | Background, Status and Insights to S-CORE 0.5 "Certifiable" -

    - - Read More - -
    -
    - -
    - - - - - - -
    -
    - - Show More - -
    -
    -
    -
    - - -
    -
    Previous Conferences
    - - - -
    -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - diff --git a/legacy-html/press_releases.html b/legacy-html/press_releases.html deleted file mode 100644 index 4dc11f4..0000000 --- a/legacy-html/press_releases.html +++ /dev/null @@ -1,448 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - - - - Nov 12, 2025 -
    - -

    - Source: Eclipse S-CORE Project -


    - -

    - Eclipse S-CORE (Eclipse Safe Open Vehicle Core) Project unites with Qualcomm to Advance Open-Source Middleware for Next-Gen Vehicles -


    -

    - November 12th, 2025 — The Eclipse Safe Open Vehicle Core (S-CORE) project today announced the active participation of Qualcomm Technologies, Inc. as a new member of its open-source community. - By leveraging Qualcomm Technologies Inc.’s Snapdragon® Digital Chassis™ solutions, S-CORE will run seamlessly on Qualcomm Technologies’ established high-performance hardware for future software-defined vehicles (SDVs). This collaboration further expands the reach of the S-CORE community, as a significant share of today’s safety-critical and secure automotive systems already rely on Qualcomm Technologies’ hardware.

    - - Hosted by the Eclipse Foundation under the purview of the Eclipse Software Defined Vehicle Working Group, Eclipse S-CORE, is an open-source initiative delivering a shared, safety-aligned middleware platform for high-performance automotive compute platforms. Developed by leading automotive and software companies — including Accenture GmbH, Aumovio SE, BMW Group, Elektrobit Automotive GmbH, ETAS GmbH, Mercedes-Benz Tech Innovation GmbH, Qualcomm Technologies, Inc., and Qorix GmbH — S-CORE provides a scalable, modular, and interoperable foundation for safety-critical components, reducing duplication, accelerating SDV development, and promoting industry-wide standardization.

    - - “Open collaboration is at the heart of solving the growing complexity of modern vehicle software,” said Mike Milinkovich, executive director of the Eclipse Foundation. “Through Eclipse S-CORE, we’re building a fully open, safety-aligned middleware foundation that helps automakers and suppliers focus on innovation instead of duplication. We’re delighted to welcome Qualcomm Technologies to this global community and the important work ahead.”

    - - “Qualcomm Technologies’ engagement with S-CORE represents a pivotal step toward democratizing access to high-performance automotive middleware,” said Laxmi Rayapudi, VP, Product Management, Qualcomm Technologies, Inc. “By aligning our Snapdragon Digital Chassis solutions with the S-CORE community, we’re empowering automakers and Tier-1 suppliers to innovate faster and deliver intelligent, connected, and safer vehicles.”

    - - The S-CORE project aims to establish a vendor-neutral, open-source software stack that addresses the increasing complexity of software-defined vehicles. Qualcomm Technologies’ contribution will streamline development workflows, reduce time-to-market, and foster a vibrant ecosystem of automotive software innovation — reinforcing the community’s shared vision to enable AI-driven, software-centric mobility at global scale.

    - - Snapdragon and Digital Chassis are trademarks or registered trademarks of Qualcomm Incorporated.
    - Snapdragon Digital Chassis is a product of Qualcomm Technologies, Inc. and/or its subsidiaries.


    -

    - -

    Eclipse S-CORE: "Open by Choice. Safe by Design."
    -
    -
    - -
    -
    - -
    -
    -
    - - - - Jun 12, 2025 -
    -

    - The Eclipse Foundation Launches the S-CORE Project: The Automotive Industry's First Open Source Core Stack for Software-Defined Vehicles -

    -

    - Source: Eclipse Foundation Canada -

    - - Read More - -
    -
    -
    -
    - -
    -
    -
    - - - - 18 Jun, 2025 -
    -

    - QNX to Serve as Foundational Operating System for Eclipse Safe Open Vehicle Core (S-CORE) Project -

    -

    - Source: BlackBerry Media Relations -

    - - Read More - -
    -
    - -
    -
    - - Show More - -
    -
    -
    -
    - -
    -
    -
    -
    - - -
    -
    - -
    - - - - - diff --git a/legacy-html/reference-implementation.html b/legacy-html/reference-implementation.html deleted file mode 100644 index 9aaed46..0000000 --- a/legacy-html/reference-implementation.html +++ /dev/null @@ -1,498 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    Join us

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    -

    - How to get in contact with S-CORE -

    -

    - If you want to get into contact with S-CORE, these are your primary entry points:

    - - Project Mailing List:
    - score-dev@eclipse.org -

    - - Architectural Discussion:
    - Join SDV's slack workspace and jump to - #score-project-channel-public - -

    - - Eclipse S-CORE Project Office Hours:
    - - Monday 13.00 - 14.00 (Weekly) - - -



    - Find all our meetings:
    - Open Eclipse community calendar - -

    - General Information / Alignment regarding S-CORE as a basis for distributions & products:
    - - Contact one of the project leads of SCORE - - -

    - -
    - -
    -
    -
    -

    - How to start your Contribution Journey -

    - -

    - Active Contributions to the S-CORE project are the basis for getting involved. - The S-CORE Project works according to the Eclipse Project Handbook and has named and elected project leads and committers - (see - Eclipse Safe Open Vehicle Core - - ).

    The direction of the S-CORE project is discussed and decided in the project lead circle, - the technical direction is created and upfront in the tech lead circle. Meeting notes are transparent via the - - S-CORE GitHub Discussions. -

    - -

    -

    - We aim to build a safety ready full stack architecture, - where components fit to each other in automotive grade Software Quality and performance. To achieve this, we follow a strict - - feature roadmap and architecture - - and a rigid - - software development process -

    - -

    - -

    - Contributions to the S-CORE project must therefore follow the technical direction of the project and the S-CORE architecture. - For an introduction on how to contribute, please check out our - How to Contribut Guideline. -

    -

    - - - -
    -
    - -
    - -


    - -
    -
    -
    -
    -

    - Stay Connected with S-CORE -

    -

    - Join the conversation, access exclusive resources, and follow us - for the latest updates. -

    -
    - -
    - -
    -
    - Join Icon -
    -
    Join S-CORE
    -

    Connect With Us!

    -
    -
    -
    - - -
    -
    - Download Icon -
    -
    Stay up to date!
    -

    Read our latest news!

    -
    -
    -
    - -
    -
    -
    - - LinkedIn - - - Slack - -
    -
    -
    Follow Us
    -

    - Stay in the loop on all platforms! -

    -
    -
    -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - diff --git a/legacy-html/townhalls.html b/legacy-html/townhalls.html deleted file mode 100644 index e44b83f..0000000 --- a/legacy-html/townhalls.html +++ /dev/null @@ -1,382 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    News & Events

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    -
    -
    -
    -
    - -
    -
    -
    - - - - Apr 11, 2025 -
    -

    - Eclipse S-CORE Townhall -

    -

    - Background information to S-CORE and Q&A session. -

    - - Read More - -
    -
    - -
    -
    - - Show More - -
    -
    -
    -
    - -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - diff --git a/legacy-html/training-modules.html b/legacy-html/training-modules.html deleted file mode 100644 index 7116404..0000000 --- a/legacy-html/training-modules.html +++ /dev/null @@ -1,1471 +0,0 @@ - - - - - - - Eclipse S-CORE - - - - - - - - - - - - - - - - - -
    - -
    -
    -
    -

    Join us

    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    -
    - -
    -
    -
    - -
    -
    -
    -

    - Start Your Contribution Journey -

    - -

    - Dive into the S-CORE contributor community by adhering to our guiding principles. - We strive for impactful, efficient contributions that evolve the project without - redundancy while connected to the "Development Workflow”. -

    -

    - Learn how the stack works — from core systems to application - support. -

    - -
    -
    - - - -
    - -
    -
    -
    -

    Our Guiding Principles

    -

    - S-CORE is built upon core principles that champion inclusivity, efficiency, and innovation within the open source automotive software community. - Our collaborative framework welcomes contributions from everyone, paving the way for more advanced and robust solutions. - Below are the guiding principles that steer the S-CORE ecosystem -

    -
    -
    -
    - Evolve, Everybody Can Join: -

    Evolve, Everybody Can Join:

    -

    - We recognize the power of collective intelligence and the strength of diverse contributions. - Everyone is welcome to participate, use, and join S-CORE, fostering a vibrant community united by shared goals and mutual growth. - -

    -
    -
    - No Re-Implementation: -

    No Re-Implementation:

    -

    - Our approach leverages existing solutions to optimize development processes. - By building on established findings and methodologies, we avoid redundancy, focusing our efforts on crafting innovative and efficient solutions. - -

    -
    -
    - Working Model - Shift Left: -

    Working Model - Shift Left:

    -

    - We adopt a proactive development model that prioritizes early testing and integration, - ensuring high quality and minimizing risks throughout the software lifecycle. -

    -
    -
    - S-CORE Ecosystem: -

    S-CORE Ecosystem:

    -

    - Our ecosystem thrives on collaboration and co-creation across various stakeholders, including universities, - industry partners, and EU commissions. We encourage dynamic contributions and collective efforts to achieve shared objectives. - -

    -
    -
    - Engage and Get Involved: -

    Engage and Get Involved:

    -

    - Join us on this transformative journey and explore opportunities to contribute to S-CORE's evolution. Visit our Get Involved pages for more details, - and learn about the S-CORE structure by browsing the About Us section for comprehensive insights. -

    -
    -
    -
    -
    - -
    -
    -
    -

    Broaden Your Impact Beyond Code

    -

    - Become actively involved with S-CORE — we are committed to continuous improvement through open collaboration. - Engage with a community of innovators and explore opportunities to contribute to ongoing projects and development processes. -

    -
    -
    -
    -
    -

    - Community Participation -

    -
    - -
    -

    - Extend your influence beyond code. Engage with the community through participation, - and contribute to various initiatives that support S-CORE's evolution.


    - Ways to Participate
    - Documentation enhancements improve project understanding and usability.
    - Event Participation: Involve yourself in community events, discussions and workshops.
    - Specialized Working Groups: Bring in your specific knowledge on processes, safety etc.
    - Feedback and Testing: Offer insights within the for project improvement.
    - -

    - -
    -
    -

    - Community Engagement -

    -
    - -
    -

    - Connect and Collaborate - Engage in lively discussions within the S-CORE community, sharing insights and collaboratively tackling challenges. - The community fosters innovation and collective growth.

    - A Vibrant Hub of Interaction
    - Join forums and contribute to dialogue.
    - Engagement Platforms
    - Forums and Channels: Discuss topics, share knowledge, and evolve solutions.
    - Feedback Mechanism: Receive updates and contribute insights to active projects.
    - -

    -
    -
    -
    -
    -
    - -
    - - -
    -
    -
    -
    -

    - Frequently Asked Questions -

    -

    - Get quick answers to the most common questions about S-CORE. - Whether you're just starting or deep into development, our FAQs - cover everything from training schedules to platform usage — - helping you find what you need without the hassle. -

    -
    - - -
      - - - -
    - - -
    - -
    -
    -
    -
    - -
    -

    - -

    -
    -
    - The S-CORE project serves as the central integration platform for various software modules. It ensures proper integration, provides common guidelines, mechanisms like build toolchains, and addresses overarching topics such as roadmap and milestone planning. -
    -
    -
    - - -
    -

    - -

    -
    -
    - Cross-functional teams are responsible for all phases of work, from defining architecture to conducting integration tests. They are usually assigned to the S-CORE main integration project or specific software modules -
    -
    -
    - - -
    -

    - -

    -
    -
    - A cross-functional team consists of Project Leads, Safety Managers, Quality Managers, Security Managers, Committers, and Contributors -
    -
    -
    - -
    -

    - -

    -
    -
    - Project management involves coordination between various technical committees, discussing technical decisions, architectural topics, and coordination of public relations . -
    -
    -
    -
    - -
    - -
    -

    - -

    -
    -
    - Releases and milestones are defined by Technical Leads and approved by Project Leads. Milestones mark important project stages, while releases structure development activities. -
    -
    -
    - -
    -

    - -

    -
    -
    - S-CORE utilizes GitHub for hosting, versioning, and contribution, and uses tools such as Sphinx for documentation . -
    -
    -
    - -
    -

    - -

    -
    -
    - Platform features are documented with requirements and architecture in the S-CORE main repository, which contains the integration repository -
    -
    -
    - -
    -

    - -

    -
    -
    - Project leads and committers are elected using the main integration S-CORE project mailing list, based on contributions and reputation within the project . -
    -
    -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Eclipse S-CORE is primarily designed and optimized for **High-Performance Computing Platforms (HCPs)** in automotive applications. The platform's components are architected to leverage dynamic memory management, process isolation, and the rich feature sets provided by safety-critical operating systems such as Linux and QNX. -
    -
    -
    -
    -
    -
    -

    - -

    -
    -
    - S-CORE supports C++ with the language set of C++17, considering additional elements from C++20 as needed. Rust is also supported with its safe subset. -
    -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Change Request types include Feature, Feature Modification, Component, and Component Modification . -
    -
    -
    -
    - -
    -
    -

    - -

    -
    -
    - Change Request Attributes include Unique ID, Status, Title, Description, Safety, Security, Change Request Type, Affected work products, and Milestones . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - GitHub is used for hosting, versioning, contribution, and documentation via Sphinx . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Technical Leads manage the platform development, control multiple modules, and handle escalations . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Safety is ensured through assumptions of use and a general safety concept outlined in the safety documentation . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Features and components are integrated into the platform using change requests and verified through tests . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Problems are reported through GitHub Issues, including documentation and resolution planning. -
    -
    -
    -
    - -
    -
    -
    - - -
    -
    -
    -
    -
    -

    - -

    -
    -
    - Contributions require exhaustive descriptions, requirements, and sometimes initial architecture drafts submitted as Feature Requests -
    -
    -
    -
    - -
    -
    -

    - -

    -
    -
    - Feature Requests are reviewed by the Technical Lead Circle before acceptance or declination -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Contributors should create an account using corporate email, link it to their employer, and ensure proper email configuration with Git -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Proper attribution requires verifying membership information in the Eclipse Membership Portal and ensuring corporate email usage . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - The Contribution Request Guideline details the process of submitting new features and tools . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - Regular reviews occur in Technical Lead Circle meetings for accepting or declining contributions . -
    -
    -
    -
    - - -
    -
    -

    - -

    -
    -
    - The Technical Lead Circle, together with software module project leads and community leads, maintains the backlog and roadmap. -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -


    -
    -
    -
    -
    -

    - Stay Connected with S-CORE -

    -

    - Join the conversation, access exclusive resources, and follow us - for the latest updates. -

    -
    - -
    - -
    -
    - Join Icon -
    -
    Join S-CORE
    -

    Connect With Us!

    -
    -
    -
    - - -
    -
    - Download Icon -
    -
    Stay up to date!
    -

    Read our latest news!

    -
    -
    -
    - -
    -
    -
    - - LinkedIn - - - Slack - -
    -
    -
    Follow Us
    -

    - Stay in the loop on all platforms! -

    -
    -
    -
    -
    -
    -
    -
    - - -
    -
    - -
    - - - - - - - From a4e41c31f448dfa7cf2e3b119321ef9f7c44e3e3 Mon Sep 17 00:00:00 2001 From: Christian Heissenberger Date: Wed, 18 Feb 2026 10:29:30 +0100 Subject: [PATCH 4/4] fix: align carousel arrow behavior across about-us and homepage contributors sliders - show homepage news/contributor nav buttons reliably by scoping slider nav logic to each wrapper - keep white arrows only on about-us dark contributors section - preserve visible hover state for dark-background arrows --- content/_index.md | 12 +++--- content/about-us.md | 2 +- static/css/contributor-slider.css | 16 +++++++ static/js/news.js | 71 ++++++++++++------------------- 4 files changed, 51 insertions(+), 50 deletions(-) diff --git a/content/_index.md b/content/_index.md index fa824f3..bf1abfe 100644 --- a/content/_index.md +++ b/content/_index.md @@ -333,13 +333,13 @@ extra_scripts: + + - - diff --git a/content/about-us.md b/content/about-us.md index cd11976..5011924 100644 --- a/content/about-us.md +++ b/content/about-us.md @@ -121,7 +121,7 @@ breadcrumb_html: | -
    +

    Our Contributors

    diff --git a/static/css/contributor-slider.css b/static/css/contributor-slider.css index 4475092..358f7c3 100644 --- a/static/css/contributor-slider.css +++ b/static/css/contributor-slider.css @@ -104,6 +104,22 @@ border-color: #161616; } +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-prev, +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-next { + border-color: rgba(255, 255, 255, 0.55); +} + +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-prev img, +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-next img { + filter: brightness(0) invert(1); +} + +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-prev:hover, +.esc-our-contributors-container-section.contributor-nav-dark .contributor-slider-content .custom-next:hover { + border-color: #ffffff; + background-color: rgba(255, 255, 255, 0.14); +} + .contributor-slider-content .owl-dots { display: none; } diff --git a/static/js/news.js b/static/js/news.js index 974a4fd..0c89e4f 100644 --- a/static/js/news.js +++ b/static/js/news.js @@ -1,9 +1,11 @@ -$(function () { - const $carousel = $(".news-slider"); - - const responsiveConfig = { - 0: { items: 1 }, - 992: { items: 2 }, +$(function () { + const $carousel = $(".news-slider"); + const $carouselWrapper = $carousel.closest(".owl-carousel-wrapper"); + const $navButtons = $carouselWrapper.find(".custom-prev, .custom-next"); + + const responsiveConfig = { + 0: { items: 1 }, + 992: { items: 2 }, 1200: { items: 3 }, }; @@ -17,43 +19,26 @@ $(function () { autoplayHoverPause: true, }); - function getVisibleItems() { - const winWidth = $(window).width(); - let visibleItems = 1; - - Object.keys(responsiveConfig) - .map(Number) - .sort((a, b) => a - b) - .forEach((bp) => { - if (winWidth >= bp) { - visibleItems = responsiveConfig[bp].items; - } - }); - - return visibleItems; - } - - function updateNavVisibility() { - const data = $carousel.data("owl.carousel"); - if (!data) return; - - const totalItems = data._items.length; - const visibleItems = getVisibleItems(); - - if (totalItems <= visibleItems) { - $(".custom-prev, .custom-next").hide(); - } else { - $(".custom-prev, .custom-next").show(); - } - } - - $(".custom-next").on("click", function () { - $carousel.trigger("next.owl.carousel"); - }); - - $(".custom-prev").on("click", function () { - $carousel.trigger("prev.owl.carousel"); - }); + function updateNavVisibility() { + const data = $carousel.data("owl.carousel"); + if (!data) return; + + const totalItems = data._items.length; + + if (totalItems <= 1) { + $navButtons.hide(); + } else { + $navButtons.show(); + } + } + + $carouselWrapper.find(".custom-next").on("click", function () { + $carousel.trigger("next.owl.carousel"); + }); + + $carouselWrapper.find(".custom-prev").on("click", function () { + $carousel.trigger("prev.owl.carousel"); + }); updateNavVisibility(); $(window).on("resize", updateNavVisibility);