To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
name: hybris-2404
description: A content snap containing libhybris, compatible with the gpu-2404 interface
upstream-relation: We’re a downstream of libhybris
interfaces:
<interface-name>: gpu-2404
request-type: auto-connection
reasoning: Automatically use libhybris drivers on Ubuntu Touch
On Ubuntu Touch we cannot use mesa-2404 with hardware acceleration. Application snaps installing on Ubuntu Touch should select hybris-2404 automatically if it is available on the system.
Regarding the request, it looks certainly reasonable to me (#voteFor). Given that the snap likely exposes binaries and/or libraries (libhybris), publisher vetting will be needed in order to complete the request.
To complete the publisher vetting, the publisher of a snap should be genuinely associated with the upstream project or belongs to a trusted group (e.g., Snapcrafters, Canonical, Verified Accounts).
Can you please clarify whether you already meet this criteria? Otherwise, we can start discussing what would be the best way to move this request forward
Sorry for the delay in my response, let me provide some context. According to the current [publisher vetting policy](Process for performing Snap Publisher Vetting) it is not possible to proceed with this request. However, this request looks legit to me, and some other reviewers agree with that.
I’ve added this topic to my next sync meeting with @pedronis to see what would be the best to move forward. I hope I will be able to provide more information during the next week.
I discuss about this request with @pedronis and it might be fine to grant it if we are able to limit the auto-connection to Ubuntu Touch systems. We already use the content of /etc/os-release for similar purposes. Could you please share what this file looks like in a Ubuntu Touch system?
I wanted to provide a small update for you here. We are currently only able to limit auto-connection based on the ID field in the /etc/os-release file. Given we would need to limit based on the VARIANT_ID field for this request, we are exploring expanding our current implementation to support this. Thank you for your patience!