We the Debian Qt/KDE Team want to early-announce [maintainer warning] our decision to remove Qt4 from Jessie+1. This warning is mostly targeted at upstreams.
Qt4 has been deprecated since Qt5's first release on December 19th 2012, that means almost two years ago!
So far we had bugfixes-only releases, but upstream has announced that they will end this support on august 2015. This already means we will have to do a special effort from that point on for Jessie in case RC bugs appears, so having it in Jessie+1 is simply a non-go.
I just want to inform you (those who are still running KDE 4) that we released a new version of your favorite network applet. This new release brings to you many bug fixes and should make your life easier. We really recommend to update to the new version as we, not intentionally, introduced some new issues in the previous version. Together with the new release of plasma-nm we also released our libnm-qt library which is also needed if you want to have fixes from plasma-nm properly working.
Aaron Seigo is a seasoned open source developer who leads the Plasma team at KDE. He also tried to bring a Linux-based tablet to the market through his Vivaldi project. He recently joined Kolab Systems, and we talked to him as well as Kolab CEO Georg Greve to understand what Kolab does and how Aaron, a KDE developer, will help the company.
Pisi Linux has continued its activities after 1.0 and we reached our second stable version 1.1. This version resulting from intensive studies; strong, stable, comfortable to use, safe and so fast. The strength of the structure to prevent damage to your system uses hardware safely to the end. Also in this release, along with many innovations were offered to us.
KDM was dropped from Plasma 5. KDM includes code from XDM dating back to 1988! It had served it's job well. However, we're now at a point where we need the backend to be Wayland ready and we want to use more modern QML in the front end. When you have to replace both the back and front ends, it's a sign to just start from scratch.
There was some work done 2 years ago into sharing code with LightDM. In the meantime a separate project was started, SDDM which is (yet another) display manager.
Although personally I was very happy with what we had with LightDM it definitely doesn't make sense to split resources, so we focussed everything on SDDM and I have been helping work on that transferring knowledge from my old project.
DWDs are not CSDs, and all theming and drawing is handled by the window manager and decoration. In addition, applications only export the structure of their widgets, they do not pre-draw or draw the widgets themselves. Applications would have little or no say in how their decorations look, just like traditional SSDs.
That being said, we don’t want DWDs to be absolutly rigid, we are looking at ‘safe’ ways applications can do basic branding on themselves in a reasonable manner, which decorations could potentially integrate without excessive effort. The main thing we are looking at is allowing applications to offer a colour pallet which decorations could use to tweak their appearance, but DWD ultimately would put the power in your hands and options would also be provided to disable unwanted hints and effects for more consistency. A primary sentiment with DWDs is that the user would be completely in control of all aspects DWDs would provide.
14 years ago, I started creating an image viewer. Back then it felt like a good project to get started with graphical application development for my newly installed Linux system. Little did I know... In 14 years Gwenview went through one toolkit change (GTK+1.2 to Qt2/KDE2), got ported to Qt3/KDE3, moved from SourceForge CVS to KDE Extragear, got ported to Qt4/KDE4, became the default image viewer of KDE4 and finally got ported to Qt5/KF5.
You may be aware I spend most of my free time these days on some other project. I am not completely out of Qt and KDE development however: I have a number of small side projects, many of them Qt-based, to which I want to give a bit more visibility. Stay tuned for more announcements.