Hi everyone,

I'm happy to announce that our transition from our old mail system
(Postbox) to our new mail system (Letterbox) has been made
successfully.

The transition was made with minimal impact on service as far as we
can tell, aside from a slight delay in mail delivery as the DNS change
propagated. At this time all major providers appear to have picked up
this change and are now delivering to Letterbox successfully.

As part of this changeover, we started from scratch with our Bayesian
database.

Hi all,
in the kirigami framework repo, there is a little gallery application which
outgrew the point of being a small example.
It's now becoming a tutorial app: on each page an example and documentation on
how to use a particular component and when with links on the relevant source
code and HIG page about such component (if available) becoming a developing
aide while writing a Kirigami application.

Also, since it's planned to add more graphics and heavy media files, makes it
not particularly ideal to still use the framework repository.
If no objections, it will be moved as a standalone

I'm sending this again because I've been having issues with this mail ing
list I haven't received any response so I don't know if it went through.

How does one use kde's ci system? Is there a way to test a projects setup
before going live with it?

Hi!

A co-developer recently pointed out that EU General Data Protection
Regulation (GDPR) is going to come into effect, soon (May 25th). To my
_very_ limited understanding, this will require privacy notices on all
websites.

I have developed a new open source software as a result of a scientific
research and I want to share my study with scientists and/or software
developers.

ThreadStack is an innovative software which produces a class library for
C++ multi-thread programming and the outcome of the ThreadStack acts as an
autonomous management system for the thread synchronization tasks.
ThreadStack has a nice and useful graphical user interface and includes a
short tutorial and code examples.

Hi all,

Due to a regression of unknown origin which results in meinproc being
unusable, all Windows builds which are dependent on kdoctools are
currently KO on Windows.

This breakage was introduced sometime shortly after the new builders
became operational (but was working at that time).

Until someone has the time to investigate this, they'll remain broken
i'm afraid.

Regards,
Ben

Hi all,

Some of you may have noticed that the delivery of Phabricator mail has
been disrupted over the past few hours. This is due to Spamcop
blacklisting the relays used by Mailgun to send our Phabricator email.

List moderators, i'm afraid you will need to approve any mail which
has been automatically held for your approval.

I have now resolved this issue by terminating our use of Spamcop.

Hi all,

It has been brought to my attention that some find that they are
receiving too much mail or other notifications from Phabricator.

Hi,
I'd like to request review for Falkon.

It's been actually in kdereview for some time already, but I never got
to properly request review, sorry about that.

There is a project set up in bugzilla, CI build and code should be in
accordance with guidelines too.
There are also some autotests, although they are rather unstable on
FreeBSD build. It looks like crash in QtWebEngine, but the backtrace
from CI is without symbols, so it is unfortunately useless.

Target is Extragear for now, and later possibly moving to KDE Applications.

Thanks,
David

Git commit dbf563df2979361e9b97088e757f95315296ea19 by Ben Cooksley.
Committed on 26/02/2018 at 07:19.
Pushed by bcooksley into branch 'master'.

Move Elisa from KDE Review to Extragear - Multimedia as requested.
Ref T8080

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>

R +0 -0 projects/extragear/multimedia/elisa/i18n.json [from: projects/kdereview/elisa/i18n.json - 100% similarity]
R +1 -1 projects/extragear/multimedia/elisa/metadata.yaml [from: projects/kdereview/elisa/metadata.yaml - 082% similarity]

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

12th February 2018. KDE today announces the release of KDE Frameworks 5.43.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.

Hello,

Elisa is now in kdereview and aiming for extragear/multimedia. We may (in agreement with the module maintainer) move later to the Multimedia KDE Applications module.

It is a music player written with qml and a few KDE frameworks. It is primarily intended to integrate with baloo but can also index music on its own and open arbitrary files from command line or a file browser.

We have worked on a vision to help clarify the what our intentions are:

Elisa is a music player developed by the KDE community that strives to be simple and nice to use.

Git commit 9146d557b5d0c00ef400241736d1bfe564576c81 by Ben Cooksley.
Committed on 05/02/2018 at 08:36.
Pushed by bcooksley into branch 'master'.

Move KBackup to it's new home in KDE Utils.
This application was in KDE Review per the mailing list announcements, it just hadn't been moved in the structure to kdereview/ hence the direct jump here.

Fixes T7881

CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... 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/kdeutils/kbackup/i18n.json [from: projects/playground/base/kbackup/i18n.json - 100% similarity]
R +1 -1 projects/kde/kdeutils/kbackup/metadata.y

Hi!

From the following ticket <a href="https://phabricator.kde.org/T7642" title="https://phabricator.kde.org/T7642">https://phabricator.kde.org/T7642</a> I was
suggested to open discussion on kde-core-devel list. Sending this email
also to kopete-devel as it is relevant for Kopete development.

Currently in Kopete git repository <a href="https://cgit.kde.org/kopete.git/" title="https://cgit.kde.org/kopete.git/">https://cgit.kde.org/kopete.git/</a> is a
branch kf5 which contains port of Kopete to KF5. That branch was created
3 years ago as part of GSoC was used as "staging area". Some patches
there are incomplete and later were "fixed & cherry-picked" into master
branch.

Hi!

I'm starting a review thread for project:

<a href="https://phabricator.kde.org/source/plasma-redshift-control/" title="https://phabricator.kde.org/source/plasma-redshift-control/">https://phabricator.kde.org/source/plasma-redshift-control/</a>

..based on responses from Albert, Ingo and Ben from thread "2 New Plasmoids in Kdereview" here on kde-core-devel. Thanks for the fast responses!

Best Regards,
Martin

Hello GSoC mentors, and teams supporting mentors,

TL;DR: Fill out <a href="https://community.kde.org/GSoC/2018/Ideas;" title="https://community.kde.org/GSoC/2018/Ideas;">https://community.kde.org/GSoC/2018/Ideas;</a> read
<a href="https://community.kde.org/GSoC" title="https://community.kde.org/GSoC">https://community.kde.org/GSoC</a>. Now.

Every year, we've asked for more time to get ramped up for GSoC, and so now
is the time for organizations to apply[1]. We have begun to write our
application, and that means that our Ideas page needs to be filled NOW,
because that is the prime consideration for the GSoC team once the Org
Applications deadline has passed.

The quality of our ideas and the guidance they give our students are the
most important part of our application.

Hi everyone,

it just happened to me again, that I want to commit/push a change of
someone else (first-time contributor) with the correct --author="x y
<mail...>" data.

But Phabricator hides the email address, so I either have to ask via
phabricator messages for the email address, which is time consuming,
or I simply give up and commit in my own name, claiming work done by
others.

Is there a simple way to find out the email address (identity.kde.org
does not work, since phab user accounts seem to be separate).

Help is very much appreciated.

Hello all,

I happen to be one of those poor souls who still rip CDs from time to time.
I'm using Dolphin for that right now, but I miss the convenience of using
KAudioCreator a while back.

It looks like it's not released at all anymore. After a quick glance at the
repository, it seems to be in a somewhat good shape (at least it builds and
starts, I didn't push further yet).

Then, I'd like to revive it and have it part of KDE Applications. Anyone with
an objection about that?

Hi all,

This is a request email for the review process of the mycroft plasmoid, the plasma-mycroft project has been moved to kdereview

The repository url: <a href="https://cgit.kde.org/plasma-mycroft.git/" title="https://cgit.kde.org/plasma-mycroft.git/">https://cgit.kde.org/plasma-mycroft.git/</a>

Mycroft plasmoid is a desktop frontend that interacts with the Mycroft Core. It is an open source community committed technology that ties natural language processing, text-to-speech, speech-to-text, and powerful APIs together to create a powerful experience allowing users to manipulate their devices through voice control.

Hello,

thanks to the KDE Sysadmins krename was moved to kdereview today.

It's a batch renamer started outside of KDE and its infrastructure but
it was kind of abandoned and I got the ok the from the original author
to move it to git.kde.org.

The code can be found at kde:krename.

The intended target should be
extragear-or-whatever-that-thing-missing-a-proper-name-is/utils

Considering KDELibs4 reached the end of its life-cycle, I'd like to
release a beta version soon after krename passes review.

Questions? Comments?

Best regards,
Heiko

Hi all,

I just realised that the Python binding effort is not setting the default
visibility for symbols using the -fvisibility=xxx option when processing
the header files [1]. Of course I can see the export macros set by the
likes of attica_exports.h, but I don't see where the compiler default is
set. Can somebody kindly point that out?

Thanks, Shaheed

[1] I'm also a bit mystified by the fact that I am deliberately querying
CMake for the COMPILE_FLAGS to use, but I have not seen -fvisibility
anywhere...

Hi all,

As some of you will know, we're currently unable to build our Fedora
image on the CI system, and have effectively been unable to do so for
some time.

Hi all,

I'd like to announce an application I've implemented over the last few weeks - liquidshell

liquidshell is a replacement for plasmashell

It does not use QtQuick but instead relies on QtWidgets,
therefore no hardware graphics acceleration is needed.

Main Features:
- Wallpaper per virtual desktop
- No animations, no CPU hogging, low Memory footprint
- Instant startup
- No use of activities (I never used nor needed them)
- QtWidgets based, therefore follows widget style from systemsettings
- Icons are used from your globally defined icon theme from systemsettings
- Colors are used from

Hi,

I'd like to submit the "Simple Menu" widget for Plasma to kdereview.

Sysadmin kindly moved the repo in position for me:

<a href="https://cgit.kde.org/plasma-simplemenu.git/" title="https://cgit.kde.org/plasma-simplemenu.git/">https://cgit.kde.org/plasma-simplemenu.git/</a>

A shiny website is found here:

<a href="https://store.kde.org/p/1169537/" title="https://store.kde.org/p/1169537/">https://store.kde.org/p/1169537/</a>

And here is an old announcement blog:

<a href="https://blogs.kde.org/2017/01/30/simple-menu-launcher-kde-store" title="https://blogs.kde.org/2017/01/30/simple-menu-launcher-kde-store">https://blogs.kde.org/2017/01/30/simple-menu-launcher-kde-store</a>

The Simple Menu codebase is QML-only, relying on C++ backends shipped
with Plasma Desktop.

It's had multiple tagged releases and is shipped as the default menu
in several distros.

Cheers,
Eike

As promised, here is an interim update on the investigation into the
use of cppyy-based bindings for KF5 (and more...) instead of SIP-based
bindings.

The first thing is that the underlying technology of cppyy,
cling/ROOT, has been under development at CERN for quite a while. It
directly reads regular C++ files (there is no intermediate format like
SIP).

The bindings it generates from Python to C++ seem far more complete
and automatic than SIP.

09th September 2017. KDE today announces the release of KDE Frameworks 5.38.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.