Replies: 6 comments 1 reply
-
Hi Todd, Marco Cavallini |
Beta Was this translation helpful? Give feedback.
-
Not yet... branding hasn't really been on my radar so far, but I'll try submitting an entry to see what they say.
Ahem, but no, that is incorrect. |
Beta Was this translation helpful? Give feedback.
-
Matt, The form looks to take around 5 minutes to fill out. They at least made it easy. Thanks for looking into it. Todd |
Beta Was this translation helpful? Give feedback.
-
OK, I've submitted both a 'Participant' form for the project, and a 'Compatible' form for the layer itself. I'll post here if/when I get a response. |
Beta Was this translation helpful? Give feedback.
-
@madisongh very good! /marco |
Beta Was this translation helpful? Give feedback.
-
The project is now a registered Yocto Project participant. (All we need now is a logo to replace the text on the Participants page.) The dunfell and gatesgarth branches will be reviewed by the TSC for the 'Compatible' mark, and Nico said he'd see if we can get the same for the dunfell-l4t-r32.4.3 branch, but since it's not just named 'dunfell', it may not be eligible. We'll have to bear that in mind going forward, and each future release branch will also need to be submitted for the 'compatible' mark. It should be easier for the subsequent approvals, though. |
Beta Was this translation helpful? Give feedback.
-
Apologies in advance for wasting time on a non-technical topic.
Has anyone filled out the Yocto compatible form for meta-tegra at https://www.yoctoproject.org/ecosystem/branding/compatible-registration ?
I don't feel comfortable representing meta-tegra, or I would fill it out. As far as I can tell, using the word Yocto in the README.md file requires compatibility registration. From https://www.yoctoproject.org/logos-and-guidelines :
Beta Was this translation helpful? Give feedback.
All reactions