for what seems an eternity i've been running linux as my daily driver and evangilising to anyone that would listen.  however working as a carpenter and having a young family didn't leave much energy, let alone time to contribute.  but over the course of the last year slowly my contributions have been increasing.  as we age our bodies aren't capable of the physical things that you used to be easy and this combined with some other events have allowed me to able fulfil a long held ambition and contribute in a meaningful way to KDE and neon.  anyway enough self-reflection from this antopidean.

thanks to the patience of @jriddell, @sitter and @sgmoore i'm very happy to be helping get neon out the door, so to speak.  after the big plasma 6 push that started in March, i've been improving my ruby skills  trying to get neon's tooling into the best possible shape.  as qt6 started to filter down from unstable, it became apparent that compilation time saving hack of building qt5 and kde frameworks5 once for unstable and copying into the stable and user archives wasn't scaling any longer and couldn't be applied to qt6 and kf6.  after changing unstable to track the latest qt6.6 beta's at the request of the plasma devs, stable and user started building their very own qt5 and kf5.  besides a few late nights and much swearing at versioning problems it all went swimmingly. \0/

lately my energies have been split between trying to get more apps with a decicated kf6 branch into the experimental overlay and trying to keep up with the rapid rate of apps in unstable whose master branch has gone qt6/kf6 only.  as sgmoore pointed out porting pim6 alone has been quite the process.  with a raft of new red/failed job build's in unstable and qt6.6 beta4 just released, it looks like the pace isn't going to slow down for the forseeable future.  anyhow i'll sign off with the obligatory screenshot. cheery bye ;]

kate6_on plasma6 on neon_unstable.png, Sep 2023
kate6_on plasma6 on neon_unstable.
kate6_on plasma6 on neon_unstable.