How To Contribute

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 .

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!