Good idea. I've done it now!

hi there, The Yocto Project is looking to hire a technical writer to develop and maintain the many documents the project supplies the greater community, including the official Yocto Project documentat

Dear all, We are very excited to be part of the Outreachy program again for the December round this year, let me congratulate Ida and Dorinda for being accepted as interns for the next three months. I

<charles.davies@...> wrote: This is correct. When at least one (binary) package is needed from a recipe, then the recipe is built, and all the resulting packages are built. So when you inclu

hi Vasyl, Ah, you're right. It was possible with the previous docs, but not anymore. With the Sphinx based docs the whole Yocto Project docs is just "one set", not a collection of 'manuals'. So curren

hey Vasyl, Can you please describe what you are doing in the webpage? It should still work. You need to select "All in one Mega manual" in the dropdown menu on the top left corner of the page. When yo

hi there, The The Yocto Project is looking to hire a build and integration engineer to join our developers community and assist the Yocto Project Architect in a wide array of tasks. We expect to build

Hey Paul, First of all, thank you so much for doing this. It's very much appreciated, I am very happy to see our community members willing to contribute to such a great internship program. As I mentio

<holzmayr@...> wrote: which I assumed was the case here, given the description. But you're right. Disclaimer: I am not familiar with multiconfig... I believe in this use case the out

in the outer rootfs image recipe, you can create a task which creates your custom 'bundle' (e.g. do_custom_image), and set: do_custom_image[depends] += "inner-recipe:do_image_complete" It will ensure

It is not lost. It was not migrated yet. It is on the doc “front page “ and i have one item in the todo list to deal with docs boilerplate, the history section is part of that. Many thanks for looking

unrelated.. but I just spotted this ^. I am cc'ing Anibal new email address. it's in a few other places.

hi Paul, Right. It's a per list configuration item. I have changed for yocto list for now, and set it to 'reply to group'. we will take care of all lists (and on lists.openembedded.org as well). Thank

INIT_MANAGER was added in 3.0, see: https://git.openembedded.org/openembedded-core/commit/?id=8d0b4704a526a48cd5e67df61b613424bbbdccde this is the 'old' (pre 3.0) method, and it can (and should) be re

there is that. And looking at the history on the server, most of the existing tags came from the web. But a hashtag is created automatically when using '#' in the email subject. that's how #define was

#hashtags

Ok.. you're right. Well at least my answer is not complete ;) This is correct. We should encourage everyone to report, and even better propose a fix, to the relevant layer, when the 'problem' is appli

A good rule of thumb is to never modify a metadata that is not yours. That applies to everything: * if you need to modify a bb file from a 3rd party library, create a bbappend file in your layer * if

thanks Vineela it looks good on the website now.

hi there, we have put in place a dashboard that shows our community engagement and stats. We are using a service from Bitergia for that, and they are using open source tools from the LF CHAOSS project

hi, thanks for reporting, you're right.. and the Development tasks manual entry is listed twice.. We will investigate and fix that! cheers