Dasharo
Dasharo Openness Score improvements
The problem you're addressing (if any)
Dasharo Openness Score is niche almost no one knows about it, despite the fact people asking questions about it.
Describe the solution you'd like
We should improve visual representation of Dasharo Openness Score as well as consider including it as mandatory part of Dasharo Certification Program (together with other validation results e.g. .
Where is the value to a user, and who might that user be?
The value to users and whole open-source firmware community is wide adoption and user friendly look and feel for standardize measure of openness. We often are asked about explaining level of openness with clear score we hope to delegate to nice looking charts and badges.
Describe alternatives you've considered
N/A
Additional context
Pasting a comment from Openness Score PR, because it is relevant:
- Script should run as part of CI/CD
- Dasharo Openness Score should be published as part of the newsletter.
- Dasharo Openness Score should be published as part of the DUG.
- We should target the production version for DUG#2.
- CI/CD should compare the Dasharo binary with reference binaries we obtained from hardware. We should not care about the privacy of hardware in the lab since it can already be considered public domain.
- Dasharo documentation should be adequately improved to explain our methodology.
- Versioning should be added. (milestones created, tags will be placed accordingly)
For which releases and which platform do we plan to provide Openness Score?
For every possible platform that makes sense
@macpijan @miczyg1 am I correct we will have CI/CD integration part as part of Novacustom integration? We also probably addressed the newsletter part, as well as the DUG part, since I will show the status. Unfortunately, I can't see Opness Score being an integral default part of Dasharo Community or Entry Subscription Releases. The documentation part also seems to be addressed, as well as versioning.
I guess we have to clean that up. We did all that stuff without bumping the version of the Dasharo Openness Score, which is incorrect.
@BeataZdunczyk cc
am I correct we will have CI/CD integration part as part of Novacustom integration?
Not really. We have integrated that in our release scripts, though.
Yes, so basically, we just addressed Dasharo Openness Score should be published as part of the newsletter. only for now
I guess we have to clean that up. We did all that stuff without bumping the version of the Dasharo Openness Score, which is incorrect.
But we haven't changed a single bit in Openness Score code yet since v0.1... So it is no eligible for v0.2, neither the items in v0.2 milestone have been fulfilled
Quick status:
- Script should run as part of CI/CD - STAGING
- Dasharo Openness Score should be published as part of the newsletter. - DONE
- Dasharo Openness Score should be published as part of the DUG. - STAGING?
- We should target the production version for DUG#2. - We are past DUG#2, STAGING
- CI/CD should compare the Dasharo binary with reference binaries we obtained from hardware. We should not care about the privacy of hardware in the lab since it can already be considered public domain. - STAGING
- Dasharo documentation should be adequately improved to explain our methodology. - DONE already in v0.1: https://github.com/Dasharo/Openness-Score/blob/main/docs/source/methodology.rst
- Versioning should be added. (milestones created, tags will be placed accordingly) - DONE https://github.com/Dasharo/dasharo-issues/milestone/10, tag v0.1 was placed on 31st May when the code and documentation has been completed.
But we haven't changed a single bit in Openness Score code yet since v0.1... So it is no eligible for v0.2, neither the items in v0.2 milestone have been fulfilled
Because some requests are not exactly Openess Score code changes.
Dasharo Openness Score should be published as part of the DUG. - STAGING?
During DUG#3 there will be the status presentation and DUG#4 should contain some reports for Dasharo releases.
We should target the production version for DUG#2. - We are past DUG#2, STAGING
Integration with NovaCustom will be the first production run I guess MSI can be another.
I think this has been integrated for NovaCustom laptops. I don't know for other devices that use Dasharo, I suggest to close the issue @pietrushnic if this is the case for all devices.
@wessel-novacustom, thanks for the ping. @miczyg1 do you think we have to keep this issue? TBH, I'm not sure if anything from v0.2 was implemented.
Not all points have been addressed yet: https://github.com/Dasharo/dasharo-issues/issues/276#issuecomment-1738705507