Eclipse Pullpiri provides a service orchestrator framework for in-vehicle services and applications.
The Eclipse Pullpiri project includes several key features within its scope, such as supporting APIs for the state transition of vehicle services, ensuring compatibility for workload manifests between cloud environments (K8S) and vehicles (Bluechi & SOAFEE specifications), and enabling and managing predefined scenarios and policies.
The Eclipse Pullpiri project does not cover several features, including implementations for basic controlling services like launch, stop, create, or delete, deployment or retrieval of workloads from a cloud registry, management of non-containerized services, and functional areas supported by general container runtime and systemd.
Repo | Commits | Reviews | Issues |
---|---|---|---|
https://github.com/eclipse-pullpiri/pullpiri | 523 | 130 | 117 |
https://github.com/eclipse-pullpiri/.eclipsefdn | 2 | 2 | 2 |
There have been 525 commits made by 17 people on 2 repositories over the last 12 months.
There have been 119 issues submitted by 12 people on 2 repositories over the last 12 months.
There have been 132 reviews submitted by 13 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.pullpiri
True
read
This project has a total of 2 repositories in its associated GitHub organization eclipse-pullpiri
.
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.2.1 of component pullpiri.
See the manifest file for this component at https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/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.
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 .
<a href="https://metrics.eclipse.org/projects/automotive.pullpiri" alt="Requirements badge for automotive.pullpiri - pullpiri"></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.pullpiri" alt="Testing badge for automotive.pullpiri - pullpiri"></a>
Has a tests traceability URL defined.
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/test_summary.xml
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/agent_licenses.html
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/fmt_summary.md
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/deny_summary.md
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/tarpaulin-report-common.html
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/tarpaulin-report-tools.html
- https://github.com/eclipse-pullpiri/pullpiri/releases/download/v0.2.1/tarpaulin-report-server.html
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 .
<a href="https://metrics.eclipse.org/projects/automotive.pullpiri" alt="Coding Guidelines badge for automotive.pullpiri - pullpiri"></a>
Has a reference document for coding guidelines.
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 .
<a href="https://metrics.eclipse.org/projects/automotive.pullpiri" alt="Release process badge for automotive.pullpiri - pullpiri"></a>
Has a reference document for releases.
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.pullpiri" alt="OSS Best Practices badge for automotive.pullpiri - pullpiri"></a>
Repo pullpiri has some of the recommended files.
Found categories: BUILD, AUTOMATION, LICENSE, README, DEPENDENCIES