No , we are using a different cloud provider / partner this time. That requires all the 'students' to have a valid account with our partner (Digital Ocean), and all the hands on will be done using DO

The problem is fixed now. You should be able to register again! Sorry about that.

hey Robert, It is odd. And it was not expected. We are aware of the issue, and have reached out to LF Events team and asked for help.

heh.. I don't mind either way.. I could have sent a proper patch too, i quickly sent it to share with everyone.. yeah, i read about that too.. and found https://github.com/sphinx-doc/sphinx/issues/837

yes, that seems correct. I don't think we should continue to use the include directive here. Since you try to make one section (for 3.4 and 4.0) with the migration and the release notes, I think somet

oh... It's because the file release-notes-4.0.rst is included with a ..include statement. The variable mapping is done with a custom Sphinx extension (yocto-vars.py) which is triggered for the 'source

I can reproduce the issue when building locally. I am using Sphinx==4.4.0

hey Talel, Thanks for reaching out! You are welcome to attend any of the public Yocto developers meetings, if nothing else you will meet and hear directly from the core developers. However it's not st

docs.pythong.org is where we stole the idea of the switcher ;-) Would anyone be able to figure out if their 'publishing' script is available anywhere? if we could mimic that somehow that might be good

Yes, this part is indeed poorly implemented. But I don't think we can remove the transition branch until we fix it, so I don't think we can take this patch now. perhaps we should maintain the overall

I don't understand. With this change, we no longer build the pages we reference here: https://docs.yoctoproject.org/releases.html#outdated-release-manuals Or am I missing here?

I agree with Quentin here. Until we have a better mechanism (to rebuild only modified branches not all of them each time, ..) I think we should continue to build them all.

hey, Not really. We definitely believe that the Yocto Project Compatible program is a valuable tool for our ecosystem. However, layers on git.yp.org are not required to be compatible. But that's a goo

Dear all, The next Yocto Project (virtual) Summit will take place on Nov 30 - Dec 2, 2021. While we are finalizing the registration tools, we've already opened the CFP, and we are, as always, looking

Dear all, As some of you may have read over the past days, there has been an ownership dispute over the freenode.net network. The IRC network has been used by the Yocto Project and many other projects

I think the question of setting up Matrix for our community is a valid question, though I think it's orthogonal to the current problem. If freenode goes away , we need an alternate plan to move *right

Thanks for your email. We are aware, and have started to look into that. It looks like some open source communities have started to move to https://www.oftc.net/ or https://libera.chat/.. If anyone wa

I think we should indeed improve that a bit. As far as I know, the only place for the release notes is the 'email' sent to yocto-announce, which includes the content from this file:http://downloads.yo

Well, in fact no , we shouldn't, is a short answer ;) Here is the long answer.. For bitbake and YP, we currently publish: master, master-next and 'stable' branches (e.g. 1.46, 1.48, 1.50 for bitbake d

hey! Thanks for starting this! sort -V is even better since it does "natural sort of (version) numbers within text", let's get ready for 3.10 ;) And using -V, how about something along these lines: v_