Git commit ce94f3398e4abf08bc5620f8ca7cdaccc5f9371f by Ben Cooksley.
Committed on 24/06/2017 at 02:05.
Pushed by bcooksley into branch 'master'.

Move Atelier and AtCore to KDE Review proper.
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
Fixes T6383

R +0 -0 projects/kdereview/atcore/i18n.json [from: projects/playground/base/atcore/i18n.json - 100% similarity]
R +1 -1 projects/kdereview/atcore/metadata.yaml [from: projects/playground/base/atcore/metadata.yaml - 085% similarity]
R +0 -0 projects/kdereview/atelier/i18n.json [from: projects/playground/base/atelier/i18n.json - 100% similarit

Hello,

Elisa is now in kdereview and aiming for extragear/multimedia.

It is a music player from a design from Andrew Lake.
It is using Qt multimedia for playback and a few KDE frameworks. Its UI is
using Qml.

Its aim is to be simple to use and hopefully in the future powerfull when
needed.

It should be usable without needing online services but will use them in the
future.

A few integration bits are missing with respect to Baloo before I can do a
release.

Hi all,

clazy is a clang plugin which allows clang to understand Qt semantics.
You get more than 50 Qt related compiler warnings, ranging from
unneeded memory allocations to misusage of API, including fix-its for
automatic refactoring.

It's being used by many people, it's stable, has 4000 lines of
unit-tests, also works on macOS, Windows nowadays and is tested in
many distros (via docker) regularly.

The proposed location is extragear/sdk (seems that's where other
development utils are)

Happy reviewing!

Regards,
Sergio Martins

Git commit 8464153d3e7b76c37a3114a9c639c17fc07f6e8e by Ben Cooksley.
Committed on 10/06/2017 at 03:36.
Pushed by bcooksley into branch 'master'.

Move QtCurve to KDE Review at request of it's maintainer
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
Fixes T6306

R +0 -0 projects/kdereview/qtcurve/i18n.json [from: projects/playground/base/qtcurve/i18n.json - 100% similarity]
R +0 -0 projects/kdereview/qtcurve/metadata.yaml [from: projects/playground/base/qtcurve/metadata.yaml - 100% similarity]

<a href="https://commits.kde.org/sysadmin/repo-metadata/8464153d3e7b76c37a3114a9c639c17fc07f6e8e" title="https://commits.kde.org/sysadmin/repo-metadata/8464153d3e7b76c37a3114a9c639c17fc07f6e8e">https://commits.kde.org/sysadmin/repo-metadata/8464153d3e7b76c37a3114a9c...</a>

diff --git a/

Hello,

OK, this time it's the right one. :-)

Zanshin is now in kdereview and aiming for extragear/pim. Please review away!

Thanks in advance.

Regards.

Hey all,

We'd like to add project plasma-browser-integration into KDE[0].

The goal is to make chrome and firefox integrate better into a Plasma
desktop environment through browser extensions.

How?:
Firefox and chrome (and potentially others) allow plugins to talk to a
native binary host [1]. This binary host is launched by the the browser and
has a socket to a conventional browser extension.

Hello,

Zanshin has been around for a while and I should have requested it to move to
Extragear a long time ago but somehow forgot. The discussion regarding the
next gen CI reminded me of that.

I hereby request Zanshin to be moved out of playground and into kdereview so
that it gets the usual review period. The aim is to have in in extragear/pim
in the end.

Regards.

Good morning everyone,
For you that don't know me, I'm Lays Rodrigues, and I work with 3 more
guys(Patrick, Chris, Tomaz) on Atelier.
Atelier is a software for 3DPrinting that we are building inside KDE.

Hi,

I'm a bit confused as to how the current KF5 CMake support works. I
have a small fragment that looks like this:

find_package(KF5KIO REQUIRED)
message(STATUS "KF5KIO includes = ${KF5KIO_INCLUDE_DIRS}")

The printed output shows that the variable KF5KIO_INCLUDE_DIRS is not
set.

Following up from Ben's email where we won't have master of frameworks in
buidling master of Plasma.

plasma-desktop will need master of:
- pl

Hi,

please review ksmtp, which is now in kdereview.

KSMTP is a small simple library with a KJob-based API similar to KIMAP or KDAV
to send mime messages via SMTP. It was initially written in 2011 by Gregory
Schlomoff but since then it's been lying around in playground without any
interest or use.

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/78/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/78/">https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 08 May 2017 10:54:07 +0000
Build duration: 30 min

CHANGE SET
Revision 92273b7d8cf039b80c310971a4216c8736dae48f by Albert Astals Cid: (Prepare for 4.14.32)
change: edit CMakeLists.txt
change: edit cmake/modules/KDE4Defaults.cmake
change: edit README

JUNIT RESULTS

Name: (root) Failed: 30 test(s), Passed: 133 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kde3support-kcommandtestFaile

Hello,

specifically in this case, how should ksmserver properly launch autostart
apps, when they are specified by their .desktop files?

When the autostart launching code was moved from klauncher to ksmserver by
[1], it replaced the launching by simply using QProcess, which caused a
number of problems such as not parsing the Exec line properly (fixed by [2]),
ksmserver discarded all stderr of launched apps instead of them going to
~/.xsession-errors, and launched apps getting killed by SIGPIPE under
specific circumstances.

Git commit c52788ab01cf08b359842a44a3213239533d810a by Ben Cooksley.
Committed on 28/04/2017 at 19:15.
Pushed by bcooksley into branch 'master'.

Move plymouth-kcm from KDE Review to Plasma Workspace in the virtual hierarchy after it cleared review last year.
Fixes T5967
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
CCMAIL: <a href="mailto:plasma- ... at kde dot org">plasma- ... at kde dot org</a>
CCMAIL: <a href="mailto:release- ... at kde dot org">release- ... at kde dot org</a>

R +0 -0 projects/kde/workspace/plymouth-kcm/i18n.json [from: projects/kdereview/plymouth-kcm/i18n.json - 100% similarity]
R +1 -1 projects/kde/workspace/plymouth-kcm/metadata.yaml [from: projects/kdereview/plymouth-kcm/metad

Git commit aa20ad09ba818607b9fe173b5bf97ba8f10c310c by Ben Cooksley.
Committed on 24/04/2017 at 20:19.
Pushed by bcooksley into branch 'master'.

Rename imagewriter to usbimagewriter, and move it to Extragear/Utils as requested.
Fixes T5945
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>

R +0 -0 projects/extragear/utils/usbimagewriter/i18n.json [from: projects/kdereview/imagewriter/i18n.json - 100% similarity]
R +2 -2 projects/extragear/utils/usbimagewriter/metadata.yaml [from: projects/kdereview/imagewriter/metadata.yaml - 081% similarity]

<a href="https://commits.kde.org/sysadmin/repo-metadata/aa20ad0" title="https://commits.kde.org/sysadmin/repo-metadata/aa20ad0">https://commits.kde.org/sysadmin/repo-metadata/aa20ad0</a>

Hello,

legal checks in openSUSE have found a licensing issue in Parley:

"statisticslegendwidget.cpp" is licensed GPLv3+, while the rest of the
software is GPLv2+ licensed.

That makes parley GPLv3+, however the COPYING file still lists GPLv2 as the
license. The best solution would be to relicense the file to GPLv2+.

Would you (who are listed in the copyright headers: Inge Wallin and Andreas
Xavier) allow for this relicensing?

Thanks.

Hi,

I would like to request review of xdg-desktop-portal-kde [1]. We would like to
make it part of Plasma releases, see [2].

What is xdg-desktop-portal-kde:
It's a KDE implementation of Flatpak portals backend [3], currently with
support of AppChooser, FileChooser, Notification and Print portals.

One mentioned issue on plasma-devel mailing list was usage of Qt's private
print API. This will most likely go away if I find out it's useless, otherwise
I'll have to keep it as it's used to set CUPS properties which are not
available to the outside world.

I'm sure you're working on some amazing things you want to let the community
know about, so head to
<a href="https://akademy.kde.org/2017/cfp" title="https://akademy.kde.org/2017/cfp">https://akademy.kde.org/2017/cfp</a>

And submit your proposal!

Cheers,
Albert

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="https://github.com/appimage-packages/imagewriter/issues/1" title="https://github.com/appimage-packages/imagewriter/issues/1">https://github.com/appimage-packages/imagewriter/issues/1</a>

Jonathan

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/74/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/74/">https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 27 Mar 2017 12:20:43 +0000
Build duration: 28 min

CHANGE SET
Revision ff6a9a25c6fb7358460d4ae2164313a4e58a514b by rakuco: (khtml: Delete pointer _before_ returning.)
change: edit khtml/ecma/kjs_html.cpp

JUNIT RESULTS

Name: (root) Failed: 3 test(s), Passed: 160 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kdecore-kservicetestFailed: TestSuite.kdecore-ksycocathreadtestFailed: TestSuite

I need help with a shell and child process issue.

To show a progressbar with kdialog, the usage is like this:

dbusRef=`kdialog --progressbar "Initialising" 6`
qdbus $dbusRef Set org.kde.kdialog.ProgressDialog value 1
etc.

i.e.

Hi everyone,

Just repeating my last email on this subject as it seems some folks
have missed the previous memo.

All issues with Phabricator should be logged at
<a href="https://phabricator.kde.org/tag/phabricator/" title="https://phabricator.kde.org/tag/phabricator/">https://phabricator.kde.org/tag/phabricator/</a> - not with upstream.

This is being done to avoid duplicate tasks, and to allow us to
communicate on a whole of project basis the things we consider
important. This helps simplify things for upstream.

Thanks,
Ben Cooksley
KDE Sysadmin

Hi all,

Sysadmin have now completed the migration of our file distribution
systems, download.kde.org and files.kde.org, to a new server.

Hi all,

Over the weekend we've updated our Phabricator instance to the latest
stable version. This has brought in a few changes which you may wish
to check out - including the ability to customise the global home menu
and setup a favourites menu for yourself to access frequently used
functions.

As the global items setup by Sysadmin cannot be overridden by users,
i've only setup a very basic set of items for everyone to use.

For those who use Arcanist, now would be a good time for you to ensure
you are running the latest stable version as well.

Hi all,

To help simplify things for Phabricator upstream, they've asked that
only a couple of people bring things to their attention (including
filing tasks). This helps them with figuring out our priorities as a
project in regards to usage of Phabricator.

Please therefore file all issues / etc you hit regarding Phabricator
on our own instance, tagging them with the project "Phabricator".

At the moment i'm the one liasing with them primarily, although i'll
be looking to bring one or two others on board soonish.

Thanks,
Ben

11th February 2017. KDE today announces the release of KDE Frameworks 5.32.0.

KDE Frameworks are 70 addon libraries to Qt which provide a wide variety of·
commonly needed functionality in mature, peer reviewed and well tested·
libraries with friendly licensing terms.

Hi devs,

this month, a heated exchange on kde-core-devel about a dep
change breaking CI has moved us to draft a new policy to better
handle situations like this in the future.

While not "law", the policy _strongly_ suggests some guidelines
forming a quid-pro-pro protocol between developers and sysadmin
when it comes to making software dependency changes that impact
provisioning of the CI system.

I've just finished preparing the new Ideas page for 2017:
<a href="https://community.kde.org/GSoC/2017/Ideas" title="https://community.kde.org/GSoC/2017/Ideas">https://community.kde.org/GSoC/2017/Ideas</a>

It is basically the same as every other year, and has no previous
ideas on it. If you or your project plan to present a former idea
again, click on the 2016 Ideas link, and copy/paste it into the 2017
page as soon as possible.

Of course, new ideas are welcome as well, as long as there are mentors
available. We'll remove ideas with no mentor listed. Please ensure
that there is contact information for each mentor.

*Please* do no maintain a separate Ideas page which you present to
students.