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 S-CORE
Connect With Us!
Stay up to date!
Read our latest news!
Follow Us
Stay in the loop on all platforms!