Bug 10513

Summary: Show Yocto Project compatible status in the layer index
Product: [Yocto Project Subprojects] Layer Index Reporter: Paul Eggleton <bluelightning>
Component: Layer IndexAssignee: Amanda Brindle <amanda.r.brindle>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: bluelightning, brian.avery, joshuagloe, leonardo.sandoval.gonzalez, patrick.ohly, randy.macleod, tim.orling
Version: unspecified   
Target Milestone: 2.4 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 15093    

Description Paul Eggleton 2016-10-27 23:24:33 UTC 
Have a manually controlled flag in the layer index that allows turning on display of "Yocto Project Compatible" logo against a layer. Initially this would just be on the detail page for the layer, and should link to information about the Yocto Project Compatible certification programme so that people can find out what it means.

If the flag is set, it indicates that the layer has been submitted and successfully passed review for the Yocto Project Compatible certification. Being that the layer index points to a living repository it's possible that it may fall out of compliance; we will have tools to validate this periodically (covered by separate bugs) so that an authorised person can remove the flag if the compliance issue isn't just temporary. Presumably the flag will need to be per-branch as well.
Comment 1 Paul Eggleton 2017-05-17 20:33:27 UTC 
This may be obviated by bug 11452, I'm not sure at this stage.
Comment 2 Leonardo Sandoval Gonzalez 2017-06-01 15:50:01 UTC 
Anibal & Paul agreed to implement this functionality in the back-end, meaning the the yocto compatible script will be executed per layer and the results stored into the DB. The remaining UI/UX work will be filed it as a separate bug.
Comment 3 Joshua Lock 2017-06-01 16:00:14 UTC 
(In reply to comment #2)
> The remaining UI/UX work will be filed it as a separate bug.

Please CC me on that. Have we identified an engineer to work on that? Do we need help from the UX team in London?
Comment 5 Tim Orling 2023-11-02 23:19:34 UTC 
This was continued in bug #15093