I’ve been involved since around 2001, during which time I’ve worked on a number of areas within the community. I ended up maintaining the panels and parts of the desktop shell in KDE’s 3.x desktop and from there ended up doing the ground-up redesign of the shell we now know as Plasma.
That introduced some radical (at the time) concepts such as device-independent UIs, strong business/UI separation, animation rich interfaces, visual integration of desktop services and visual distinction between the desktop shell and applications running in them.
Outside of technical work, I was also president of KDE’s global non-profit foundation, KDE e.V., and oversaw improvements in how we manage intellectual property, standardizing developer sprints, rigorous reporting and more. It was during this time that I was named one of the top 50 most influential people in IT by silicon.com.
Kubuntu has one definite advantage. It's predictable. Predictable in the sense that it will never give you a fully satisfying experience out of the box, and it will do its best to be controversial, bi-polar and restrained by default. You get a very good and modern system, but then it's almost purposefully crippled by boredom, a conservative choice of programs and missing functionality. Why, oh why. It could be such a shiny star.
Utopic Unicorn is a pretty solid release, but it does suffer from some alarming issues. The graphics stack, first and foremost. Desktop effects are also missing, and Samba printing is simply disappointing. The rest worked fine, the system was robust, there's good evidence of polish and improvements, but then it lacks pride and color. I would say 8/10, but that's not enough to win people's hearts. We've all been there, every six months, so something new is needed. Maybe Plasma 5? Aha! Stay tuned.
Franklin is a 39 year old FOSS activist based in Taipei. He has coordinated KDE's zh_TW translation team since 2006, and is the core developer of ezgo (Chinese), a compilation of educational software used by schools all over Taiwan. ezgo, which in its Linux installation uses KDE by default, blends more than 100 free software applications into one localized, easy to use package.
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.