Plasma at QtCon

QtCon opening keynote
QtCon opening keynote

QtCon 2016 is a special event: it co-hosts KDE’s Akademy, the Qt Contributor summit, the FSFE summit, the VideoLan dev days and KDAB’s training day into one big conference. As such, the conference is buzzing with developers and Free software people (often both traits combined in one person).

Naturally, the Plasma team is there with agenda’s filled to the brim: We want to tell more people about what Plasma has to offer, answer their questions, listen to their feedback and rope them in to work with us on Plasma. We have also planned a bunch of sessions to discuss important topics, let me give some examples:

  • Release Schedule — Our current schedule was based on the needs of a freshly released “dot oh” version (Plasma 5.0), Plasma 5 is now way more mature. Do we want to adjust our release schedule of 4 major versions a year to that?
  • Convergence — How can we improve integration of touch-friendly UIs in our workflows?
  • What are our biggest quality problems right now, and what are we going to do about it?
  • How do we make Plasma Mobile available on more devices, what are our next milestones?
  • How can we improve the Plasma session start?
  • What’s left to make Plasma on Wayland ready for prime-time?
  • How can we improve performance further?
  • etc.

You see, we’re going to be really busy here. You won’t see results of this next week, but this kind of meeting is important to flesh out our development for the next months and years.

All good
All good? – All good!

8 thoughts on “Plasma at QtCon

  1. “How do we make Plasma Mobile available on more devices, what are our next milestones?”

    ZTE has launched Project CSX (Crowd Sourced X), where “X” idea can be anything within ZTE’s mission and capabilities. An opportunity for everyone in the community to participate in the design of new phones and/or accessories!

    Please vote in the CSX thread on the Z-Community website for Xiaodong Qi (i2000s) idea that ZTE provide the following options for people to choose from when buying a phone model:
    (a) Preinstall Ubuntu as the only OS
    (b) Preinstall Android as a primary OS with Ubuntu as a secondary OS
    (c) No OS installed but either Android, Ubuntu, Plasma Mobile or any other mature/stable OS’s could be installed from images by consumers at their own risk.

    You need to register and/or log-in on the ZTE forum to vote up the idea by 10th September 2016 for it to be considered by the R&D team of ZTE. ZTE are one of the leading smartphone manufacturers/sellers in the US, EU and developing countries. An Ubuntu Touch phone option or even no OS preinstalled!

    1. thank you! I was following this project from begin and was hoping that an idea like this would take off… and it did: currently Nr. 1 with 160 up votes… oh wait… 161 (that was me:)

      Also check out this:
      via german site:
      and the git:

      If he could support Plasma Mobile in his script that would be awesome. Ah I just saw you also commented at CNX :)

  2. Conc. “How do we make Plasma Mobile available on more devices, what are our next milestones?”

    Can you give some insight, what your planes are / what these milestones are…?

  3. Two interesting comments by Lewis Rockliffe have recently been posted on Bhushan Shah article: Plasma Mobile : New base system

    Lewis Rockliffe: So, why aren’t you guys using Mer as a base system like Sailfish OS? or open embedded like Asteroid OS?

    These are two examples of mobile systems using libhybris and wayland to run Qt-based UX Layer on android hardware, and on the Mer side we have a number of hardware adaptations available that you could use to put a Plasma Mobile system on as well as working documentation and a great community around creating adaptations for new devices.

    It just seems a shame to working on something that is so similar, yet different enough that it wont take advantage of other work thats already been done in this area.

    Bhushan Shah: No, it won’t be possible to run CyanogenMod and Plasma Mobile side by side in single installation. To use Android binary blobs we use libhybris hwcomposer backend in KWin/Wayland.

    Lewis Rockliffe: Actually, with libhybris this is possible, and something we’ve been working on in the sailfish community ports.

Comments are closed.