KDE PIM mentorship request

[Daniel Vrátil]

On Monday, 15 June 2020 23:27:41 CEST Ihor Antonov wrote:
> 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.

Both KDevelop and QtCreator are amazing and really good for Qt-based 
development. VSCode is also pretty good. If you've never used any of them, 
just try them and see which one suits you best. All of them use clang for 
parsing, highlighting and autocompletion, so on the language side you get 
basically the same experience everywhere.

I myself am a terminal person, so I use Vim+YCM and I'm really happy with it 
:)

> > 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) ?

For X11 it's actually fairly simple, you just expose the X11 socket into the 
container and graphical applications will magically work. The PIM docker [0] 
does all the magic for you. The advantage of this approach really is a 
complete isolation of the development version of PIM from the rest of the 
system, so there's no risk of accidentally corrupting/breaking your stable 
"production" PIM. I created the container to make it easier for new 
contributors to start contributing to PIM, I don't use it myself, though as I 
find it a bit too clumsy for some complex development/debugging. I'm a maniac, 
so I just use git master as my production setup. I can't say I'd recommend 
this for everyone, but at the same time it has worked really well for me for 
many years. And when something breaks I'm at least motivated to fix it quickly 
:D

/Daniel

[0] https://invent.kde.org/dvratil/kdepim-docker


-- 
Daniel Vrátil
www.dvratil.cz | dvratil at kde.org
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
-------------- 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/20200616/523713a5/attachment.sig>