I love project stats, and I completely obsess over bug reports.
Whilst collecting data for another post, a mystery libreoffice autocomplete popup me to plot something I hadn't thought of plotting.

What days of the week are bugs opened and closed?

Resolved can mean one of a few things; fixing the bug with a change in the code, marking it as a duplicate of another bug or in some cases closing it as not a direction we want to go with Plasma.

Observations

People report more on weekdays than weekends

The difference surprised me. I think it gives a strong indication that Plasma 5 is being used more for work than as a hobby, with people more likely to encounter an area needing to improvement during the normal office week.

Obviously we don't know for sure and we can't pull useful timestamp information without knowing timezone of the user, but indications seem to be there.

Bugs are resolved on a weeked at 50% of the rate of the weekday

This isn't too surprising given that some Plasma maintainers like myself work for Blue Systems or Red Hat and we tend to work office hours.

What's encouraging is that, whilst slower, this shows that a significant amount of work does happen outside office hours; both employees taking the extra time to care for Plasma and our community contributors stepping up to work here. There's some shift between the people doing weekday and weekend bug closing.

We get more bugs open than we close

Naturally our graph will show that we have some open bugs, but if we assume this rate continues our number of open bugs will continue to rise.

It's not as bad as this graph makes it look as there also a lot of bugs in a zombie "needs info" state, where we're waiting to hear back from a user either with more information or to confirm their issue is fixed.

We definitely need more help here, I want Plasma to be bug free.

It's all about Tuesdays

Tuesday is apparently the day for the most reports getting handled. It's also the day Plasma 5.4 gets released.

I always knew Tuesday was an underrated day of the week.

At the start of September I'm going to be taking a vacation from Blue Systems work; ignoring all things Plasma and spend an entire week to spend some time on some other projects.

This will be the second time I'll be attending Randa. Last year was simulatenously one of the most hard-working enduring sprints possible yet also one of the most enjoyable weeks in close proximity to some of my best friends.

This year I intend to devote all my time working with the KDE Connect team.

As there is so much cross-project work, it's a lot easier when I can talk to the right people, making Randa the right opportunity.

Some of my project plans during that week - KDE Connect

Smaller Connections?

Android Wear is becoming more than a gimmick. What should KDE Connect integrate? Should we make the media player remote work? Desktop notifications? Blood Pressure monitor as you read certain email threads... certainly some potential.

Desktop to Desktop

The main thing KDE Connect works is where you are in close proximity to your phone and desktop, but don't want to keep physically switching between everything. For most normal people, a phone and a desktop is enough...but some of us have two machines that we have to switch between and most the same principles of mouse sharing, notifications(?) and files applies.

Most of the relevant code exists; it just needs that final bit of UI on top.

KDE Connect for SMS Messaging in KTp

I ported all the wonderful work by Alexandr Akulich to Qt5 with the KDE connect refactoring, and it's all merged, bitrotting slowly, it just needs that final push of work to get it out the door.

Fundraising

I'm one of many many who will be at Randa working on a huge range of interesting projects.

We need money in order for sprints like Randa to go ahead; it costs money to get everyone under the same roof, and the organisation at Randa is done in a way that keeps everyone productive.

Whilst I'm lucky enough to fund my own flights, me from yesteryear would have struggled, and we are all giving up our time to work on KDE. We also need support to help get everyone doing great stuff there.

Please donate to the fundraiser using the giant link below

As retrofitting high DPI support into such a large range of both KDE and third party applications is risky to do without breakage, progress is deliberately slow and gradual in order to do this right.

The good news is I get to write lots of blog posts as we make the continual steps forwards.

Iterative Progress

Plasma 5.3 (last release)

* High DPI Scaling via a hidden config option for early testing

Plasma 5.4 (this release)

* User facing dialog with the screen management settings for scaling

Plasma 5.5+ (future releases)

* Automtatically enabled. Providing we see positive feedback in this release.

The New Setting

Plasma 5.4 brings a new setting to adjust the screen scaling to match your device.

In the new setting we've tried to simplify things to a simple slider which adjusts both font size which we have full control over, and then above a certain threshold adjusting the entire UI which we can only do at integer values (i.e doubling the size). This is to support the semi-high screens and the current generation all in the same place.

It's still far from what I'd like to achieve overall, but it does the job of making some devices usable.

What Can We Expect From This Release?

With High DPI support enabled you will see one of three things amongst your applications:

• The app sized sensibly, looking absolutely gorgeous on your new screen.
• The app sized sensibly, but some aspects may not necessarily make the full use of the higher resolutions available.
• The app not scaled at all remaining really small. We should see the font size increase to fit, but icons, dialogs, checkboxes may remain annoyingly small.

We've tried to make sure the most common, important KDE applications (Dolphin, Konsole, Kate and so on) fit into that top category. An app like xfig or dia, will remain in the bottom category until Wayland.

There's also a slim chance there may also be some breakage.
If so please do file a bug report as soon as possible and tag me to the CC list.

Props especially go to Christoph Cullman and Alex Fiestas for their help on some of the applications.