Hello Quentin,<br /><br />Thanks for your reply,<br /><br />
<blockquote><span style="white-space-collapse: preserve;">what this is supposed to represent or in which scenario this would be a diagram</span></blockquote>
The diagram is the detailed process of how bitbake will handle building a recipe that depends on other recipe, and show the details of the working directory of a recipe which I noticed that lot of Yocto developers get confused with.<br /><br />
<blockquote><span style="white-space-collapse: preserve;">I've seen you've continued to post a few things here and there on LinkedIn too, nice :)</span></blockquote>
I have lot of contributions in mind: diagrams, documentation, classes, new bitbake binary ideas based on Bitbake python library, for example you can have a look at : bitbake-recipe which looks for all recipes that start with a given input, and show its path, version, and other information (Covering limitation of devtool and bitbake-layers on the topic of looking for recipes): GitHub link:&nbsp;<a href="https://github.com/bhstalel/bitbake-recipe" target="_blank" rel="noopener">https://github.com/bhstalel/bitbake-recipe</a><br /><br />I would like to start contributing, but I need a quick meeting with a contributor to explain to me the meetings, patch sending process ,... etc<br /><br />I will take your comments about "<span style="white-space-collapse: preserve;"><strong>sysroot-destdir</strong>" </span>into consideration and I will start fixing the diagram and prepare the SVG format.<br /><br />Thanks,<br />Talel