The Eclipse Automotive Integration for AutoSD provides manifest files and tooling to build one or more AutoSD images to build, run and test Eclipse SDV projects and blueprints, allowing one to easily swap deployed components, create blueprints and so on. Either locally or in a CI/CD pipeline.
| Repository | Commits | Reviews | Issues |
|---|---|---|---|
| https://github.com/eclipse-autosd/eclipse-autosd | 29 | 5 | 7 |
| https://github.com/eclipse-autosd/.eclipsefdn | 7 | 1 | 0 |
There have been 36 commits made by 4 people on 2 repositories over the last 12 months.
There have been 7 issues submitted by 1 people on 1 repositories over the last 12 months.
There have been 6 reviews submitted by 1 people on 2 repositories over the last 12 months.
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/automotive.autosd
TruewriteThis project has a total of 1 repositories in its associated GitHub organization eclipse-autosd
.
The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset:
SDV Maturity badges recognise achievements made by the project towards the SDV maturity assessment goals. Learn more on the dedicated page .
These badges only apply to the SDV Working Group .
Warning
This page is under construction
We are currently working on a definition and prototype for SDV badges, please see the SDV Process .
Is the project used to showcase the resolution of a real-life situation, either individually or integrated with other Eclipse SDV projects? See the SDV Blueprints project for more information.
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Requirements e.g. defining, versioning and managing, traceability, coverage, etc? For more details on the needs for the different levels of the Requirements Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Testing e.g. defining, versioning and managing, traceability, coverage, types of tests etc? For more details on the needs for the different levels of the Testing Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Documentation e.g. types of documents depending on contents, versioning, etc? For more details on the needs for the different levels of the Documentation Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Coding Guidelines e.g. defining, adhering, managing issues etc? For more details on the needs for the different levels of the Coding Guidelines Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Releases e.g. defining a process, versioning and managing, release notes, coverage etc? For more details on the needs for the different levels of the Release Process Criteria read its definition here .
This project has not registered any activity on the criteria.
Is the project respecting OSS good practices files in their repositories? See also the legal documentation checker for more information.
<a href="https://metrics.eclipse.org/projects/automotive.autosd" alt="OSS Best Practices badge for automotive.autosd"></a>
Repo eclipse-autosd has some of the recommended files.
Found categories: AUTOMATION, LICENSE, README