KDE PIM mentorship request

[Ihor Antonov]

On Monday, 15 June 2020 04:44:39 PDT Daniel Vrátil wrote:

Thanks to everyone who replied!

> Thanks for stepping up! There's plenty of things to do and another pair of
> hands always helps :)

> The best course of action is to get the entire KDE PIM built from current
> master into a prefix. kdesrc-build is the best tool for this, see the
> Development page on our wiki [0].
> [0] https://community.kde.org/KDE_PIM/Development

In the process of building it. 
 
> Then you can start playing around with it :)

Do you recommend using KDevelop or QtCreator? Or maybe something else.
Spartan scenarios like vim + language server are not foreign to me too.

 
> Once you get everything compiled and running, just pick one of the tasks
> you've listed above and start working on it. If you need any help, just feel
> free to ask. Someone from the team will gladly help you or point you in the
> right direction.

> /Daniel

Thanks Daniel, I most certainly will!

Also thanks to Glen, Martin and Ingo for sharing useful links. 
I am familiar with docker, but it is not quite clear how to test UI software 
from docker. Setting up X forwarding is a bit cumbersome (left alone Wayland 
scenarios). What is the "mainstream" way of test-driving your own work 
(without breaking things installed with package manager) ?


-- 
Ihor Antonov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20200615/251e861c/attachment-0001.sig>