no, feel free to assign it to yourself if you want to work on it

r25c is now used with Qt6.5 minimum

Merged in https://invent.kde.org/education/gcompris/-/commit/3c32a81f0bd69aa5cb287f156ba78dec43955b2d

https://invent.kde.org/education/gcompris/-/merge_requests/212

Looks good to me, thank you!

yes, for sure, you have better knowledge to do it!

For ColorOverlay this seems to be a correct start, even if I didn't manage to reproduce the exact same colors, @timotheegiet :

seems no more needed

duplicate of https://phabricator.kde.org/T16078...

https://invent.kde.org/education/gcompris/-/merge_requests/188

https://invent.kde.org/education/gcompris/-/merge_requests/185/diffs

the remaining ones will be done 1 by 1 when faced

Only aab missing now

muted attribute has been added to MediaPlayer object in GCAudio and used to stop the audio when true

https://invent.kde.org/education/gcompris/-/commit/fe5672c3068e7ef5739a1ff9bc267c54bb18951b

For this, we can now consider the minimal version is Qt6.5, so no need to try to be compatible with older versions. Maybe there are new solutions that have been implemented in Qt meanwhile

fixed in https://invent.kde.org/education/gcompris/-/commit/43fdd729c8d26b67f5b7e1e17bbcf001d1a74a0d

Missing box2d and aab generation.

No more true with Qt6.5?

Some basic code has been done in https://invent.kde.org/education/gcompris/-/commit/ea01b681e31212fcd24720d09134c1e31bb15e4d. This is not promising like that: compilation time goes from a few seconds to minutes, rcc/plugins are not compatible.
Need to dig more/differently to be able to switch between rcc/plugins IF plugins are faster/less consuming and there is a good reason to switch

Most have been taken care of in branch work/qt6_cleaner

yes, at higher levels it would be nice to have to handle 2 or 3 blocks of tens

In T17010#301666, @joseph wrote:

do we really want to translate it?

I don't know what capacities our translation teams have. Although I think blogging is very important for communication within the community, the posts likely have limited impact and are rather time sensitive: in a few years they may not be read by many people at all. I think using the translation teams for other aspects of KDE work may be more worthwhile if we have to choose where to put these resources.

Website is published (https://invent.kde.org/websites/mentorship-kde-org/), let's review the content and make sure the procedure is ready for SoK contributors.