The Eclipse Safe Open Vehicle Core project aims to develop an open-source core stack for Software Defined Vehicles (SDVs), specifically targeting embedded high-performance Electronic Control Units (ECUs). Please check the documentation for more information. The source code is hosted at GitHub.
The communication mainly takes place via the score-dev mailing list, Discussions and GitHub issues & pull requests (PR).
We have a Slack channel for community discussions here Eclipse S-CORE Slack Channel.
Please be familiar with the Code of Conduct.
Please note that for the project the Eclipse Foundation’s Terms of Use apply.
Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA).
For more information, please see the Eclipse Committer Handbook: https://www.eclipse.org/projects/handbook/#resources-commit
To complete and submit a ECA, log into the Eclipse projects forge (you will need to create an account with the Eclipse Foundation if you have not already done so). Click on "Eclipse Contributor Agreement" and complete the form. Be sure to use the same email address when you register for the account that you intend to use when you commit to Git.
In addition, you need to sign the DCO to contribute to the project.
Please refer to the README.md for further information.
This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on Non-functional Stakeholder_Requirements. During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure).
Improvements are adding/changing processes and infrastructure, bug fixes can be also on development work products like code. In case you want to fix a bug or contribute an improvement, please perform the following steps:
- Create a PR by using the corresponding template (Bugfix PR template or Improvement PR template). Please mark your PR as draft until it's ready for review by the Committers (see the Eclipse Foundation Project Handbook for more information on the role definitions). Improvements are requested by the definition or modification of Stakeholder Requirements or Tool Requirements and may be implemented after acceptance/merge of the request by a second Improvement PR. The needed reviews are automatically triggered via the CODEOWNERS file in the repository.
- Initiate content review by opening a corresponding issue for the PR when it is ready for review. Review of the PR and final merge into the project repository is in responsibility of the Committers. Use the Bugfix Issue template or Improvement Issue template for this.
Please check here for our Git Commit Rules in the Git Guidelines.
Please note, that all Git commit messages must adhere the rules described in the Eclipse Foundation Project Handbook.
Please find process descriptions here: process description.