Postings by Jonathan Riddell

welcome plasma-active-window-control

Just passed kdereview and moved into extra/base is Plasma Active Window Control.

Plasma Active Window Control is a plasma widget that you can embed in
your panel to control your active window with e.g. close or maximise
operations. Useful for decorationless window management.

New maintainer is Chris Holland. Do say hello.


KDE Review passes

Welcome the following projects which passed kdereview process

plasma-simplemenu now in selfrelease/extra and released on
pulseaudio-qt now in selfrelease/extra and released on
rust-qt-binding-generator now in selfrelease/extra
plasma-redshift-control now in selfrelease/extra

We really do need to sort out the terminology for
extragear/extra/self-released things.


Welcome Latte Dock to KDE

Latte is a dock based on plasma frameworks that provides an elegant
and intuitive experience for your tasks and plasmoids. It animates its
contents by using parabolic zoom effect and tries to be there only
when it is needed.

It's been part of KDE for a while but the incubation process stalled.
With the creation of a new home wiki page
<a href="" title=""></a> and User wiki page
<a href="" title=""></a> I've been able to set the
incubation to green.


KDE Review reviews

I've made a list of kdereview projects and their current status as I
understand them and e-mailed the maintainers for updates
<a href="" title=""></a>
(this is linked from the lifecycle wiki page).

Feel free to help keep that page up to date.

I moved kpeg and kdot to unmaintained as they haven't had any activity
since we last discussed them in 2017.


Kopete and Libjingle

This patch needs tested for Kopete
<a href="" title=""></a>

But I don't know how to test it. Does anyone use jabber and video conferencing through it with libjingle?

I signed up for accounts at this server
<a href="" title=""></a> and I can send messages
from Kopete but messages don't arrive in Kopete when sent from their
web client. And I see no options to use video conference in Kopete as
would use Jingle.

If there's nobody who uses this any more I think we should remove Kopete to unmaintained.


new weegie

I was updating weegie and rebooted but it didn't surface, responded to
pings but not to ssh.

Since it was running vivid it was time to update it anyway. The
reason it hasn't been is I had hoped to change it to Chef setup but
turns out Chef doesn't work on ARM for no good reason and with no good
error message so i ran out of energy.

Anyway I've set up a new weegie now running trusty and copied over the
main content.

Please remove]

someone should take over kubuntu-bugs list

----- Forwarded message from Jacek Nykis via RT < ... at lists dot> -----

CC: <a href="mailto: ... at jriddell dot org"> ... at jriddell dot org</a>
Reply-To: <a href="mailto: ... at lists dot"> ... at lists dot</a>

C++ multiple classes doing similar stuff

In isoimagewriter I've multiple classes doing ISO verification. How
this is done differs per distro so I've different classes for Neon,
Kubuntu, Arch etc. They share a common parent class to not duplicate
too much code. But I still need to create each class and call it

In a more dynamic language I'd make an array of these classes for loop
over the array to call them. What's a good way to do something
similar in c++?

I worry the answer will include templates and other scary parts of c++.


libqaccessibilityclient now in kdereview

libqaccessibilityclient is now in kdereview. It's in a git repo
called libkdeaccessibilityclient but we filed a sysadmin request to
rename it.

We just released 0.2.0 in unstable (for some reason 0.1.1 was released
in stable some years ago).

What is it?
Since it's hard to grasp all the bits related to accessibility, I'll try to
explain what the lib is for.
Most of the stack is part of Qt 5, so nothing to worry about, that's the part
that lets applications expose their UI over DBus for AT-SPI, so they work
nicely with assisitve tools (e.g. Orca).

who is authorised to move repos around?

I'm unclear who is authorised to move git repos around, e.g. from
playground to kdereview to kde-extra

It used to be only sysadmins which seems like a political burden on a tech team.

Now anyone can edit repo-metadata. So can anyone move repos around as
long as rules and conventions are followed?

I wonder if it should be a task moved to a team such as the release
team (but then that's not a well defined team).

I'm asked because I was asked to review atcore being moved around
<a href="" title=""></a>


imagewriter in kdereview

Please review imagewriter which I've just had moved to kdereview.

It's a simple tool to write ISO images to a USB key. It should be
cross platform and work on Linux, mac, windows.

It's based on ROSA Image Writer and the ROSA maintainer has agreed to
maintain it in KDE. Compared to ROSA I've switched to i18n and used
kauth and made the ROSA branding optional.

Scarlett has started making an AppImage for it although I don't know
if it'll work with KAuth
<a href="" title=""></a>


Request for refund of equipment

Kubuntu Council, I'd like to request the Kubuntu Fund refunds some
equipment I bought for the Plasma sprint this week

<a href="" title=""></a>

€89.46 and €4.99 which comes to £80.58

It's for media and drives to read and write audio CDs, data CDs and
floppy disks. Using this we were able to fix Dolphin's support for
floppys and K3b's support for data CDs.
<a href="" title=""></a>

Kubuntu fund currently has £10,847 in it.


Suggestion to Remove KFloppy and hold back K3b

We tested some legacy media at the Plasma sprint

<a href="" title=""></a>

I recommend KFloppy be removed from Applications releases. It
couldn't find my floppy drive and when I hacked the code to tell it
where to look it depended on an external tool fdformat which didn't
work anyway.


cantor and kaccounts-integration use KDE_APPLICATIONS_VERSION_MAJOR as
the SOVERSION to their libraries. This is strange because it's a
variable which only changes every few releases when the year changes.
SOVERSIONS should change every time there's binary incompatibility,
which if you're unsure can just be every release (marble does this) or
you can not use an SOVERSION and put the library in a sub directory
and call it a private library.

Is a new variable needed? KDE_APPLICATIONS_SOVERSION which gets
changed every release?


Porting Notes: KNotifications sound theme

KNotifications uses sound which you set in your .notifyrc file.

To prevent overlapping files the name of the files were renamed when
moving from kde-runtime to plasma-desktop.

You will nedd to update your .notifyrc file for this, e.g.
is now

I've added this to
<a href="" title=""></a>



I've tidied up the kdiagram packaging for neon

<a href="" title=""></a>


Munich Sprint

There's a sprint in Munich with our favourite large Plasma rollout,
Limux at the end of May

<a href="" title=""></a>
May 27/28/29

They will provide office space and three meals a day but no
accommodation or travel. I usually book at a room at the nearby
Motel-1 hotel.

No particular theme but I expect me and Harald to be there for KDE neon.


CI Version number change

I noticed that our version numbers mean we can't reliable upgrade the foundation

1.0+git20160201+15.10 can't be upgraded to 1.0+git20160101+16.04
because the build for the newer foundation happens to be a bit older.

So I changed it to 1.0+p15.10+git20160201 which can be upgraded to

The p stands for platform.

This will affect new builds of software built from version control on
our CI deployments.

Let me know of any problems


5.7 Kickoff Meeting Minutes

We met and discussed Plasma 5.7

** Agree to move Todo list to Phabricator
Now at <a href="" title=""></a>

** Schedule for 5.7 beta 16 June (d_ed to lead), 5.7.0 tag on Thu 30th
June, 5.7.0 release Tue 5th July
<a href="" title=""></a>
<a href=";ctz=Europe/London" title=";ctz=Europe/London"></a>

** jensreu, Sho_, bshah to lead 5.7 beta test day on Sunday 19th
June/Mon 20th June

** colomar and jensreu working on Plasma vision, to be discussed at
future Monday meeting

Then we reviewed existing

old images

Is there any problem if I tidy up <a href="" title=""></a> by
removing the old kubuntu ci snapshot and the kubuntu-plasma5 image


zanshin 0.3

There's a request for Zanshin 0.3 packages incase anyone is interested
in helping

<a href="" title=""></a>



forwarding from irc because sgclark is away this week

<bshah> sgclark: your recent commit to kdeplasma-addons added git markers
<bshah> (debian packaging)
<bshah> bshah@archbox ..ea-tooling/git/plasma/kdeplasma-addons
(git)-[kubuntu_unstable] % git grep HEAD
<bshah> debian/control:<<<<<<< HEAD
<bshah> debian/plasma-widgets-addons.install:<<<<<<< HEAD

kde-build-metadata for beta branches

I've branched Plasma for the 5.5 beta and will make a final release in
a couple of weeks. Before I make the final release I want to check in if it has any complaints in builds of the Plasma/5.5
branch. But currently uses kde-build-metadata points
only to master and to current stable which is Plasma/5.4.

Can I change kde-build-metadata to Plasma/5.5 while the branch is in
stable or will that mess up other uses of kde-build-metadata?


Muon in need of a maintainer

Muon, the Apt package installer UI is in need of a maintainer. It has
been split out from Discover and Updater which are application focused
and to some extent work with multiple backends. Muon is package
focused and covers the surprisingly important use case of technical
users who care about libraries and package versions but don't want to
use a command line. It'll probably move to unmaintained unless anyone
wants to keep an eye on it so speak up now if you want to help out.



All welcome

<a href="" title=""></a>


Standing down as release manager

With 15.10 successfully released I'm standing down as release manager
of Kubuntu.

Making Kubuntu over the last 10 years has been a fantastic journey.
Even since I first heard about a spaceman making a Linux distro using
Debian but faster release cycles I've known this would be something
important and wanted KDE to be part of it.

Standing down as release manager for Kubuntu

With 15.10 successfully released I'm standing down as release manager
of Kubuntu.

Making Kubuntu over the last 10 years has been a fantastic journey.
Even since I first heard about a spaceman making a Linux distro using
Debian but faster release cycles I've known this would be something
important and wanted KDE to be part of it.

wily release candidates testing needed

release is due tomorrow, we have images that need testing, all help appreciated

<a href="" title=""></a>


plasma-sdk in kdereview

Plasma SDK contains a few handy developers tools for Plasma

plasmathemeexplorer, plasmoidviewer, plasmaengineexplorer and the icon
browser cuttlefish

It gets released with Plasma but is still in extragear. I'd like to
move it to kde/workspace in git and I've just asked for it to be moved
into kdereview to start that. Please have a review of it and see if
it's good enough.


Fwd: Please package Akonadi 1.13 with bugfix for 14.04 LTS backports

----- Forwarded message from Stephan Diestelhorst <stephan. ... at gmail dot com> -----

Reply-To: Stephan Diestelhorst <stephan. ... at gmail dot com>
Sender: <a href="mailto: ... at canonical dot com"> ... at canonical dot com</a>

Hi there,

I am a very happy user of the Kubuntu Backports PPA, but have recently
been bitten by this bug here:
<a href="" title=""></a>

Is there any chance you guys could please pack