DevHeads.net

Core

KUserFeedback in/on its way to KDE Review

Hi,

I've asked for KUserFeedback to be moved to KDE Review, aiming for extragear/
libs initially, with a possible future option to continue on to frameworks.

KUserFeedback is a framework for gathering user feedback using application
telemetry and targeted surveys while providing decent transparency and control
to the user.

For more details see the previous announcement on this list here: https://
marc.info/?l=kde-core-devel&m=149294623025111&w=2 Since then we also got a QML
API and a few more data sources, and KUserFeedback has been shipped with the
recent GammaRay 2.8 release.

Please

AtCore on KDE Review

Yay, now we are on track again.

projects/kdereview: Move Atelier and AtCore to KDE Review proper.

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

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="https://phabricator.kde.org/D6318" title="https://phabricator.kde.org/D6318">https://phabricator.kde.org/D6318</a>

Jonathan

Elisa is in kdereview

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.

kdereview - qtcurve

QtCurve is now in kdereview with the intention of being in extragear/base

clazy is in kdereview

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

KDE Frameworks 5.35.0 released

10th June 2017. KDE today announces the release of KDE Frameworks 5.35.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. For an introduction see the·
Frameworks 5.0 release announcement.

Attica

Improve error notification

BluezQt

Pass an explicit list of arguments.

projects/kdereview/qtcurve: Move QtCurve to KDE Review at request of it's maintainer

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/

Notice of significant adjustment to KWin

Hi all,

At the request of the KWin maintainer the KWin repository master
branch has been forcibly rewound to c5861b99 (per T6301)

A log of the changes which have been thrown away is attached.

Developers may need to reinstate these changes (assuming they have
been properly reviewed) to ensure no fixes are lost.

Apologies for the inconvenience.

Regards,
Ben Cooksley
KDE Sysadmin

Zanshin is in kdereview

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.

projects/kdereview/zanshin: Move Zanshin to KDE Review.

Git commit 866a38766e5c33ef81e9f2434f6d8995bd5f1aea by Ben Cooksley.
Committed on 08/06/2017 at 06:29.
Pushed by bcooksley into branch 'master'.

Move Zanshin to KDE Review.
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
Fixes T6277

R +0 -0 projects/kdereview/zanshin/i18n.json [from: projects/playground/pim/zanshin/i18n.json - 100% similarity]
R +1 -1 projects/kdereview/zanshin/metadata.yaml [from: projects/playground/pim/zanshin/metadata.yaml - 089% similarity]

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

diff --git a/projects/playground/pim/zanshin

Plasma Browser Integration is in kdereview

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.

Kirigami in Frameworks

Hi all,
The Kirigami component set always was targeted to be eventually released as a
framework, ideally tier 1.

zanshin for kdereview

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.

Moving AtCore to Extragear

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.

Moving AtCore to Extragear

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.

kdereview: qqc2-desktop-style

Hi all,
I'm anouncing the QtQuickControls2 desktop style in kdereview, repo name is
qqc2-desktop-style

It is intended to be a small style written in QML for QtQuickControls2 that is
intended to be used by default in QQC2-based apps when used in the Plasma
desktop (it shouldn't have any user-visible message, anywhere), its final
intended location is kde/workspace to be released together with Plasma 5.11

KF5 CMake usage question

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.

KDE Frameworks 5.34.0 released

13th May 2017. KDE today announces the release of KDE Frameworks 5.34.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.

RE: Next Gen CI - frameworks requirements for plasma

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

Jenkins-kde-ci: kdelibs KDE-4.14 latest-qt4 » Linux,gcc - Build # 79 - Unstable!

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/79/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/79/">https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 12 May 2017 00:39:57 +0000
Build duration: 48 min

CHANGE SET
Revision 2c2892f07cc052a9f3d52b73b4b03d4637142a31 by scripty: (SVN_SILENT made messages (.desktop file))
change: edit knotify/tests/knotifytest.notifyrc
change: edit kio/misc/kmailservice.desktop
change: edit kdecore/network/kssld/kssld.desktop
change: edit kparts/tests/notepad.desktop
change: edit plasma/tests/testcontainmentactionsplugin

kdereview: ksmtp

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.

Jenkins-kde-ci: kdelibs KDE-4.14 latest-qt4 » Linux,gcc - Build # 77 - Unstable!

GENERAL INFO

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

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

JUNIT RESULTS

Name: (root) Failed: 2 test(s), Passed: 161 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kdecore-ksycocathreadtestFaile

Jenkins-kde-ci: kdelibs KDE-4.14 stable-qt4 » Linux,gcc - Build # 78 - Unstable!

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

Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

Hi everyone,

This is going to be quite a long email, my apologies in advance for that.
If you use the CI system regularly as part of your development flow it
is important you read this email in it's entirety as your action will
probably be required. If you are aware of a list I have missed in the
above, please feel free to forward it there.

As some will have been aware of for some time we currently have a
problem where changing the system base is an incredibly disruptive
activity.

How to launch .desktop files properly?

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.

kde-open5 bug help needed

Hi all,

I hit a bug[1][2] in kde-open5 when using
QDesktopServices::openUrl(myUrl) to open the system browser.

The issue is that, since myUrl redirects to another page, kde-open5
(used under the hood by QDesktopServices because
XDG_CURRENT_DESKTOP=KDE is set) "fetches" the redirection url and then
open the browser at the redirected url; for my workflow this is bad
because myUrl generate a cookie and then you have no such cookie when
the browser starts.

I debugged the flow and I understood that since
redirectionHandlingEnabled is enabled by default, this[3] statement in
transferjob.cpp handl

projects/kde/workspace/plymouth-kcm: Move plymouth-kcm from KDE Review to Plasma Workspace in the virtual hierarchy after it cleared review last year.

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

projects/kde/pim/kdepim-runtime: Move kdepim-runtime to kde/pim/ in the virtual hierarchy.

Git commit 01bc4814fa11272f54e6f33f7a3f3e2ae883913c by Ben Cooksley.
Committed on 27/04/2017 at 09:59.
Pushed by bcooksley into branch 'master'.

Move kdepim-runtime to kde/pim/ in the virtual hierarchy.
WARNING: All projects which depend on kdepim-runtime on the CI system will be broken until kdepim-runtime has been rebuilt following this commit.

projects/extragear/utils/usbimagewriter: Rename imagewriter to usbimagewriter, and move it to Extragear/Utils as requested.

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>

Application usage statistics and targeted user surveys

Hi,

we have talked about the above topics a couple of times in the past, from what
I remember usually agreeing it would be nice to have some more statistical
information about our users, so we know what our applications are used for,
and to measure impact of changes. Similarly, it would be nice to be able to
actually ask our users questions without statistical bias by using out-of-band
channels like blogs or social media.

Licensing issues in Parley: GPLv2+ vs GPLv3+

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.

KDirWatch issue

Hi,

just wondering if I'm doing something wrong or there really is a bug in KDirWatch
(I'm on openSuse Leap 42.2, KF5 5.33.0)

From the docs I understand that when I call

KDirWatch::stopDirScan(dir);
... create files in the dir ...
KDirWatch::restartDirScan(dir)

it should not emit the dirty signal when I run this, right ?

Well, it does.
I've attached a small test.

When I modify the code and use stopScan() ... create ... startScan()
I still receive the dirty signal with the path to the file I created.

Only way it works without signal is
removeDir(dir) ... create ...

kdereview - xdg-desktop-portal-kde

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.

How to install icons for multiple themes

Hey all,

how is one supposed to install different versions of icons for different icon
themes? Say I have an icon for breeze, breeze-dark and oxygen. I went ahead
and plumbed it into CMake with ECM's ecm_install_icons specifying THEME
accordingly, but at runtime nothing is found...

Akademy 2017 Call for Papers deadline is this Monday!

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

KDE Frameworks 5.33.0 released

08th April 2017. KDE today announces the release of KDE Frameworks 5.33.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.

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="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

karchive and QSaveFile

I'm trying to make Krita use QSaveFile instead of the home-grown
mess of temporary files that get copied over the original file
after saving succeeded. The problem is that Krita, like Calligra,
uses KArchive.

Jenkins-kde-ci: kdelibs KDE-4.14 latest-qt4 » Linux,gcc - Build # 74 - Unstable!

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

Jenkins-kde-ci: kdelibs KDE-4.14 stable-qt4 » Linux,gcc - Build # 75 - Unstable!

GENERAL INFO

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

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

JUNIT RESULTS

Name: (root) Failed: 5 test(s), Passed: 158 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kfile-kdiroperatortestFailed: TestSuite.kio-clipboardupdatertestFailed: TestSuit

QProcess::startDetached and bash stdout capture

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.

KDE Frameworks 5.32.0 released

11th March 2017. KDE today announces the release of KDE Frameworks 5.32.0.
(this time for real -- last time it was in fact 5.31 with a bug in the version in the announcement email...)

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.

Communication with Phabricator upstream

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

projects/kde/workspace/plasma-vault: Move Plasma Vault to (Plasma) Workspace

Git commit b8559f750bfa648ebae4a26882b2a64f07ae3094 by Ben Cooksley.
Committed on 07/03/2017 at 06:24.
Pushed by bcooksley into branch 'master'.

Move Plasma Vault to (Plasma) Workspace
Fixes T5335
CCMAIL: <a href="mailto:release- ... at kde dot org">release- ... at kde dot org</a>
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>

R +0 -0 projects/kde/workspace/plasma-vault/i18n.json [from: projects/kdereview/plasma-vault/i18n.json - 100% similarity]
R +1 -1 projects/kde/workspace/plasma-vault/metadata.yaml [from: projects/kdereview/plasma-vault/metadata.yaml - 084% similarity]

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

Migration of Download Infrastructure: Please check your applications

Hi all,

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

Project Releases: Infrastructure Migration

Hi everyone,

To allow for Sysadmin to migrate the primary host for download.kde.org
and files.kde.org to another server (with significantly more disk
space) we'll need to make both of those read only for a period of time
this weekend.

During this period, it will not be possible to add/remove files to
those trees - which means projects will not be able to make releases.

To the knowledge of Sysadmin, this does not affect the release of any
project, however anyone who had plans should please contact us
immediately.

Regards,
Ben Cooksley
KDE Sysadmin

Phabricator updated

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.

Branching retrospective question re KDE frameworks 5.x work from 2011 onwards.

In 2011, something bubbled to SlashDot from this community.

<a href="https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-Development" title="https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-Development">https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-De...</a>

TL;DR: what branching strategy to adopt for the KDE 5.x work, given
a wish to:
1) stay abreast of 4.x fixes/releases,
and 2) not make the mistakes of the 3.x to 4.x effort (whatever they were).

May I ask what actually happened re branching, merging, cherry picks
(back and forth) and all that, and what veterans think about it all
looking back?

This is really a question for posterity.

Communication with Phabricator upstream

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

Plasma Vault is in kdereview

Hi all,

I'm announcing that Plasma Vault is in the review phase - you can get
it from kde:plasma-vault or with kdesrc-build plasma-vault.

Plasma Vault is a system for easy creation of encrypted data storage
(not for whole system encryption - we have distribution installers for
that).

It is consisted of:
- kded daemon that handles most of the logic
- Plasma applet to provide the UI

Features:
- Supports encfs and cryfs (more to come later)
- Vaults can be limited to certain activities (automatically closing
when you leave the activity it belongs to)

More info at [1] and [2]

Cheers,
Ivan

KDE Frameworks 5.32.0 released

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.

Longer holidays Feb-Aug

Hey,

just a short notice. From Feb to Aug. I won't be available very much at
computer, because I'll do a longer holiday in South France. I'll still will
answer mails, but not as fast as currently and I won't nearly do any
programming.

Best Regards,

sandro

Draft Policy: Dependency Changes and CI

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.

KDE Frameworks 5.30.0 released

14th January 2017. KDE today announces the release of KDE Frameworks 5.30.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.

As Google Code-in ends, time to plan for Google Summer of Code

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.

Syndicate content