It’s been two months since my previous KF6 progress report. Clearly an update is long overdue, it’s time to make it happen!
An actual Qt 6 is not published yet and we didn’t branch for KF6 yet either. Still as can be seen on the KF6 Workboard there are plenty of tasks in our backlog which can be acted upon now. No need to wait to participate, all the work done now will make the transition to KF6 easier later on anyway.
On the workboard, we currently have 25 tasks in progress and 8 tasks done. That’s still quite some activity brewing. We got fewer tasks done than since the previous report but nothing to worry about I think. A bit more disappointing to me is that they are mostly done by our core contributors (although to be fair we got less known names in the in progress tasks). Anyway, I will say it again then: there is work for everyone, it’s a very good time to get your feet wet contributing to KDE Frameworks. Don’t be shy! We’re nice. ;-)
Anyway, let’s see the tasks done during the past few weeks (in no particular order):
If you pay close attention, you will see that some of those tasks involved patches outside of KDE Frameworks. This is to be expected (and there are more such tasks), if we want the transition to be easier for the community later on, it’s a good thing to get our applications ready as well. In any case, thanks to everyone involved!
Per usual, I will use the opportunity to look at the community analytics for KDE Frameworks itself. That’s why I ran my scripts against the repositories in the frameworks section of the KDE repositories tree. Of course, this means we won’t capture some of the activity from the tasks above (since as I mentioned some activity is outside KDE Frameworks itself) and it also means we’ll capture some activity unrelated to the KF6 transition. Still I think it’s interesting to see how KDE Frameworks itself is doing.
Let’s start with the commit activity since the previous KF6 Progress Report.
During that time frame, we got 74 different committers. That’s quite a lot indeed and more than the last time! Of course some of our usual suspects stick out as very active, but it’s nice to see so many other names present and helping with KDE Frameworks.
Now, how does the code contributor network looks like?
Unsurprisingly, we find our usual suspects again as very central to the network. Like the last time we find a couple of lesser known names (at least to me) in that set of central people… interestingly those names are the same than the last time. This means we had some recruiting happening and the retention seems good. This is great news! As I keep reminding everyone, high centrality is not an end in itself, in such networks it healthier to have a mix of tightly and loosely connected nodes, it’s exactly what we got here.
Next time, your name could be in visualizations like the ones above!
Check out the KF6 Workboard and pick a task to help us toward this great transition. If you need help to get started, feel free to contact us on the #kde-devel IRC channel on Freenode.