Find out how you can contribute to KDE, learn valuable skills using bleeding edge Free Software technologies and get compensated.
There are already loads of proposals on the GSoC ideas page
Which one are you going to do?
3 Likes
@carl given the recent activity on here regarding display of calendar data in Plasma applets, maybe consider a project idea to make the Merkuro QML API viable for Plasma usage?
Could be just the functional bits or even some of the UI.
Potentially laying the foundation for a QML addon framework for PIM?
1 Like
This is not a bad idea. There is already some sort of generic QML bindings for Akonadi here: src/components · master · PIM / Merkuro · GitLab with e.g. ComboBoxes for selecting an Akonadi::Collection or a Plasma applet for the contact module of Merkuro: src/contacts/applet · master · PIM / Merkuro · GitLab
Only issue is that we are trying to move away a bit from the deep integration of apps with Plasma since this is not working well with Flatpak at all. Ideally Merkuro and Akonadi would be part of the system image in an immutable like on other platforms like Android or macOS/iOS and then this won’t be a problem, but so far as wasn’t able to convince KDE Linux’s devs of doing the same…
2 Likes
Ah, nice!
I only had a quick look at the calendar plugin and that already looked quite good.
Right but the QML modules could be application independent, like the C++ PIM libraries.
E.g. instead of being org.kde.merkuro.calendar it could be org.kde.pim.calendar or similar.
As a first step it should be good enough to be able to load the Merkuro modules in a Plasma applet context.
I guess at some point Flatpak will have to come up with a way to package services.
2 Likes