There have been 404 commits made by 29 people on 20 repositories over the last 12 months.
There have been 180 issues submitted by 17 people on 17 repositories over the last 12 months.
There have been 321 reviews submitted by 25 people on 20 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.uprotocol
TruereadThis project has a total of 47 repositories in its associated GitHub organization eclipse-uprotocol
.
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 .
Assessing release v0.7.0 of component up-rust.
See the manifest file for this component at https://github.com/eclipse-uprotocol/up-rust/releases/download/v0.7.0/sdv-manifest.toml .
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.
<a href="https://github.com/eclipse-sdv-blueprints/fleet-management" alt="SDV Blueprints integration badge for automotive.uprotocol - up-rust"></a>
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 .
<a href="https://metrics.eclipse.org/projects/automotive.uprotocol" alt="Requirements badge for automotive.uprotocol - up-rust"></a>
Has a requirements traceability URL defined.
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 .
<a href="https://metrics.eclipse.org/projects/automotive.uprotocol" alt="Testing badge for automotive.uprotocol - up-rust"></a>
Has a tests traceability URL defined.
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.uprotocol" alt="OSS Best Practices badge for automotive.uprotocol - up-rust"></a>
Repo up-rust has some of the recommended files.
Found categories: AUTOMATION, CONTRIBUTING, README, BUILD, LICENSE, NOTICES, CONDUCT