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.

Thank you all for all the proposals. In order to not to wait too much and miss the beginning of the SoK, we went with mentorship.kde.org.
I've uploaded a first version of the website in https://invent.kde.org/websites/mentorship-kde-org and have created some issues to keep a track of the remaining work.
Now is the time to update the texts, design the website, ensure we have everything written and we are ready to start SoK soon!

In T17010#300898, @kbkmde wrote:

collaborative learning programs probably captures what is desired, see https://www.researchgate.net/publication/305160722_Cooperative_and_Collaborative_Learning_Definitions_and_Applications_in_Japanese_Universities but it is too long a name.

Thank you all for your inputs!

version 2023-11-21 contains it

Thank you for the ideas!
If I have to filter a few, I would remove build/develop as it looks like too developer oriented (and build.kde was previously a Jenkins instance if I'm not wrong).

GCompris code: https://invent.kde.org/education/gcompris/-/merge_requests/159
GCompris data code: https://invent.kde.org/education/gcompris-data/-/merge_requests/9

If there is no other proposition regarding the name of the website, I'll ask for the git repository creation on November 25/26th and I'll push the code from my local repository in it (https://invent.kde.org/jjazeix/mentorship-kde-org).

Benson proposes:

May wish to use a name such as contribute.kde.org or grow.kde.org as it
might be a little more welcoming to people new (and perhaps not so new)
to KDE.

Basic code in https://invent.kde.org/jjazeix/mentorship-kde-org/-/tree/master (copied from eco.kde.org so it's the same theme for now)

Done by Bruno in https://invent.kde.org/education/gcompris/-/commit/24e08efd73ae93c663fe03be830516afd31447f8 and https://invent.kde.org/education/gcompris/-/commit/1d9d06f1888942ea46c6d63a1c760dcad7d27cd4

Done by Bruno in https://invent.kde.org/education/gcompris/-/commit/af556053b55284ed878b995dac045a0d3df45bc4

Fixed in https://invent.kde.org/education/gcompris/-/commit/d434bb173f0361eecef61270a5c65be8aaf328ea

yes, house numbering is also a great idea! Regarding the theme, @timotheegiet will be able to give more insights as he is the one in charge of the graphics/theme.
The code should not change much depending on if we do houses or wagons

If we go this path, we already have a locomotive and wagons for click_on_letter, it could be nice. Also regarding multiple answers, we have some components (AnswerButton in src/core) in missing_letter that could be reused.

The idea is interesting, do you have any idea on how to make it teacheable/playful (more than just displaying a question and an input text)?