Longer term, we hope to publish the results of this project to be explored as part of the https://github.com/open-telemetry/opentelemetry-ecosystem-explorer project (https://explorer.opentelemetry.io/). But first, I think we should also create a minimal UI that can be published as a github pages static site alongside this project.
For both cases, I think it would be useful to provide an aggregate of the conformance data that can then be consumed by the frontends or other consumers. We can either gate PRs on updating it, or have a nightly job that ensures everything is up to date.
We should be able to view the conformance reports for an individual library / domain, as well as a high level overview that spans all languages. As we grow our list of tested artifacts, we'll likely need to evolve this UI over time, but as a starting point we can do something like what was done in the POC.
We can create various views, like an overview list:
A signal conformance overview:
Conformance reports by attribute:
Longer term, we hope to publish the results of this project to be explored as part of the https://github.com/open-telemetry/opentelemetry-ecosystem-explorer project (https://explorer.opentelemetry.io/). But first, I think we should also create a minimal UI that can be published as a github pages static site alongside this project.
For both cases, I think it would be useful to provide an aggregate of the conformance data that can then be consumed by the frontends or other consumers. We can either gate PRs on updating it, or have a nightly job that ensures everything is up to date.
We should be able to view the conformance reports for an individual library / domain, as well as a high level overview that spans all languages. As we grow our list of tested artifacts, we'll likely need to evolve this UI over time, but as a starting point we can do something like what was done in the POC.
We can create various views, like an overview list:
A signal conformance overview:
Conformance reports by attribute: