Skip to main content

Eclipse Autowrx

Eclipse Autowrx is the open source implementation of digital.auto (http://digital.auto), an industry-wide initiative enabling the automotive industry to establish a new, digital-first approach for the…

Activity - by type

  • There have been 852 commits made by 12 people on 5 repositories over the last 12 months.
  • There have been 1 issues submitted by 1 people on 1 repositories over the last 12 months.
Commits per month
Issues per month

Activity - by repositories

Repo Commits Issues
https://gitlab.eclipse.org/eclipse/autowrx/autowrx 557 1
https://gitlab.eclipse.org/eclipse/autowrx/backend-core 230 0
https://gitlab.eclipse.org/eclipse/autowrx/docs 38 0
https://gitlab.eclipse.org/eclipse/autowrx/ui-automation-test 17 0
https://gitlab.eclipse.org/eclipse/autowrx/instance-overlay 10 0

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

Security related information is not yet available for this project. In order to gather such information automatically, Self Service of GitHub resources needs to be enabled for this project.

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.

Blueprints integration

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.

Requirements

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.

Testing

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.

Documentation

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

[![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")

Coding Guidelines

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.

Release process

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.

OSS Best Practices

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

[![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")

Back to the top