Sprinter development came ahead quite nicely in the last week. Over the weekend I cleared everything for a v0.1 release. I didn't roll a tarball due to the aforementioned headachy-flu-thing, but it has been tagged in the repository along with the creation of a stable branch.
Work on v0.2 is already underway, starting with a small refactor of the main worker thread code to simplify it and build in some runtime checks available in debug builds to ensure things are running in the threads expected. I also ported the activities runner which exposed two issues in the Frameworks 5 version of libkactivities (one I fixed; one related to KDBusConnectionPool I'm still investigating, though there is a work-around for it in the runner plugin for now). So yes, it's now at the point where porting runner plugins makes sense. If you wish to help, checkout the repository and look at the TODO list for a full list of runners needing porting. I've added a docs/Porting_KRunner_Plugins.txt that should get you started; there is also a Runners.txt that provides a more thorough look at how Sprinter plugins work.
Most importantly, Sprinter is a guinea pig project for the KDE sysadmin's experiment for our future git infrastructure. Which means that you can find all development here: https://git-next.kde.org/kde/sprinter/ There is still a repository on git.kde.org (and I am tracking it for translations) but primary development is now happening on git-next.kde.org while the evaluation of gitlab is ongoing. To see what this new github-ish tool loos like and why the admins are testing it, see my post here.
Luminosity of Free Software episode 17
I wanted to record this one tonight, but given how I'm feeling it just wasn't in the cards. So it is tee'd up for next Friday instead. I'll post a reminder before then, but as a teaser I'll be covering systemd, which I covered briefly in Episode 4 as part of the topic on fragmentation. Given Debian's recent adoption of it, and Ubuntu's following along, it seems like a great time to look at the technical side of systemd. I'll also be taking a peak at GCompris as it makes its transition to QtQuick. I am open to one more topic (in addition to the usual Q&A of course), so if you have a burning question about something I haven't covered previously, leave it in the comments section below.