List of active repositories:
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/automotive.autowrx
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.
[![Documentation badge for automotive.autowrx](https://metrics.eclipse.org/badges/automotive.autowrx_badge_documentation.png)](https://metrics.eclipse.org/projects/automotive.autowrx "Documentation badge for automotive.autowrx")
Has a Documentation URL in the API.
https://digital-auto.github.io/playground/
Has a Getting Started URL in the API.
https://digital-auto.github.io/playground/basics/
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.
[![OSS Best Practices badge for automotive.autowrx](https://metrics.eclipse.org/badges/automotive.autowrx_badge_oss_best_practices.png)](https://metrics.eclipse.org/projects/automotive.autowrx "OSS Best Practices badge for automotive.autowrx")
Repo autowrx.git has some of the recommended files.
Found files: README, DEPENDENCIES, BUILD
Repo backend-core.git has some of the recommended files.
Found files: BUILD, DEPENDENCIES, LICENSE, README
Repo docs.git has some of the recommended files.
Found files: AUTOMATION, README
Repo instance-overlay.git has some of the recommended files.
Found files: README
Repo ui-automation-test.git has some of the recommended files.
Found files: README, DEPENDENCIES