Re: LibKF6Breeze Icons and KIconLoader

[Jonathan Riddell]

I neon me and David R tracked it down to some optimization probably
with the dh_dwz tool from Debian packaging tools, this is the "DWARF
optimization and duplicate removal tool" part of the toolchain.

And with the discussion here Christoph has yesterday replaced the use
of qt_add_big_resources() with qt_add_resources() which also makes the
problem go away.
https://invent.kde.org/frameworks/breeze-icons/-/commit/fa44b11bc2b36d5c3cfc5c3403ea75b2fff57253

So beware use of qt_add_big_resources() it seems to be fragile to optimising.

Jonathan

Re: LibKF6Breeze Icons and KIconLoader

[Jonathan Riddell]

> have no such issues, but does for you the current code in KIconThemes
> and
> KBreezeIcons work? (e.g. if one doesn't revert but uses the master
> state)

No master is equally broken when made into a .deb and equally works
when compiled manually.

Jonathan

LibKF6Breeze Icons and KIconLoader

[Jonathan Riddell]

Has anyone had issues with Breeze loading using Frameworks 6.2 or
master building the libKF6BreezeIcons.so.6 library in breeze-icons.
In neon we found that the icons did not load in Plasma and System
Settings and other QML apps.  The Breeze theme was not available for
selection in System Settings but Breeze Dark was available for
selection.

This only happened in the packaged build.  A manual build was fine.
Building the package and copying the library in manually from the
build was fine.  But building the package and copying the library in
manually from the final package broke it.  So there's something about
the way the .deb packaging gets made that seems to break a path or
some other aspect of the library.

The error on output from apps when using the broken library is
"kf.config.core: Created a KConfigGroup on an inaccessible config
location :/icons/breeze/index.theme Icon Theme"

For now I've done a workaround of reverting to KIconLoader 6.1.

Bug used was https://bugs.kde.org/show_bug.cgi?id=487374

Jonathan

Frameworks 6.1 Released

[Jonathan Riddell]

KDE Frameworks 6.1 is released for distros and packagers

https://kde.org/announcements/frameworks/6/6.1.0/

Re: Frameworks 6.1 tars available

[Jonathan Riddell]

extra-cmake-modules 6.1.0 tar has been updated ahead of release on Friday

extra-cmake-modules;master;7e68938f075a0423e3744358be9c4e77c6922104;extra-cmake-modules-6.1.0.tar.xz;76c9edf00807e6cf8d4ae35f5195b4bc3fe94648d976fef532bf7f97d86388bd

   http://download.kde.org/stable/plasma/6.1.0/extra-cmake-modules-6.1.0.tar.xz;>extra-cmake-modules-6.1.0
   333kB
-   
a51fb26baea9f6828884bfe6671d1cda840bd7f8c8bba904b7abb2160c2fedd2
+   
76c9edf00807e6cf8d4ae35f5195b4bc3fe94648d976fef532bf7f97d86388bd

http://embra.edinburghlinux.co.uk/~jr/tmp/frameworks-6.1.0-release-data
http://embra.edinburghlinux.co.uk/~jr/tmp/extra-cmake-modules-6.1.0-changes_report.html

On Mon, 8 Apr 2024 at 12:09, Antonio Rojas  wrote:
>
> El viernes, 5 de abril de 2024 13:31:32 (CEST), Jonathan Riddell escribió:
>
> > Tars for KDE Frameworks 6.1 are available for pre-release packaging,
>
> > release is due next Friday 12 April
>
>
> Hello,
>
>  Please consider a respin of extra-cmake-modules to include 
> 7e68938f075a0423e3744358be9c4e77c6922104
>
>
>  It fixes the default CMAKE_INSTALL_PREFIX value with cmake>=3.29.1.
>
>
>
>

Frameworks 6.1 tars available

[Jonathan Riddell]

Tars for KDE Frameworks 6.1 are available for pre-release packaging,
release is due next Friday 12 April

http://embra.edinburghlinux.co.uk/~jr/tmp/frameworks-6.1.0-release-data

Jonathan

Kile release status

[Jonathan Riddell]

Following the release of Qt 6 based libraries and apps users of Kile are
reporting that it no longer runs for them.  There does not seem to have
been a stable release of Kile in many years and even the unstable beta is 2
years old but the app does seem to get development and have Qt 6 code ready
to go (although when I tried to compile it against Frameworks 6.0 it had
various include errors).

What are the chances of getting a Kile release in the near future?

Jonathan

Frameworks 6.0.0 is out!

[Jonathan Riddell]

Frameworks 6.0.0 is out!  Congrats everyone.

At the meeting yesterday we decided to keep with the 1 monthly schedule.
I'll try to nudge people into creating a release team so it's not all
dependent on 1 person.

David Faure: we talked about having KF5 releases on a less frequent
release, maybe every 2 or 3 months.  Do you have an opinion here?

We spoke about making a bugfix release of 6.0 in two or three weeks time
which would mean making Git Frameworks/6.0 branches so bugfixes can go
there.  I've not done this yet but do let me know if I should.

Jonathan

Re: KDE Frameworks 6.0.0 tars

[Jonathan Riddell]

Updated frameworks 6.0 tars tonight are
baloo-6.0.0
ea21e88d1fe252d2dc95e0b7ae8891594822ccdd898e7aa56d46ed9ecd626a41
http://embra.edinburghlinux.co.uk/~jr/tmp/baloo-6.0.0-changes_report.html

kfilemetadata-6.0.0
cf130dc1b32a31a19213f3e1ac67f2180cb7931240e5c755211686e93792f393
http://embra.edinburghlinux.co.uk/~jr/tmp/kfilemetadata-6.0.0-changes_report.html

knewstuff-6.0.0
0299dba980590bd7c74870a74c6bb6ca732af478ab2c9ba414943f62ea0be0fa
http://embra.edinburghlinux.co.uk/~jr/tmp/knewstuff-6.0.0-changes_report.html

Jonathan

Re: KDE Frameworks 6.0.0 tars

[Jonathan Riddell]

kstatusnotifieritem respin up
http://embra.edinburghlinux.co.uk/~jr/tmp/kstatusnotifieritem-6.0.0-changes_report.html

   http://download.kde.org/stable/frameworks/6.0/kstatusnotifieritem-6.0.0.tar.xz
">kstatusnotifieritem-6.0.0
   46kB
-
f64d46c340f455fb3354d41ed73c23766e0256943de3a316fbc56c3b51020095
+
b426176d2cbc6fe80c758b6c476a47341d89a92cbb3355c2be37428a41772907

Re: KDE Frameworks 6.0.0 tars

[Jonathan Riddell]

KAuth respin now up

http://embra.edinburghlinux.co.uk/~jr/tmp/kauth-6.0.0-changes_report.html#SGMLDocuments

   http://download.kde.org/stable/frameworks/6.0/kauth-6.0.0.tar.xz;>kauth-6.0.0

   2.1MB
-
  
fef974fb82f1564b520636c98dd537c2367a964ffc0fadfe34d3a42ed4ef991c
+
  
66046698d2584692d5397a6ec808b2c9f8b7882a0f85233be9cd69283d03c768



On Thu, 22 Feb 2024 at 09:33, Jonathan Riddell  wrote:

>   http://download.kde.org/stable/plasma/6.0.0/ktexteditor-6.0.0.tar.xz;>ktexteditor-6.0.0
>
>2.6MB
> -
>   
> 086c502231cd95861e47bcdad9e79bcbf200fd4c508b239af9ca6e78223f60b8
> +
>   
> 620266c1d288d09f7aee4d2bc8b141c73555d5f033c452bcd2e2db2064b8fd42
>
>
> http://embra.edinburghlinux.co.uk/~jr/tmp/ktexteditor-6.0.0-changes_report.html
>
> On Wed, 21 Feb 2024 at 11:44, Jonathan Riddell  wrote:
>
>> Tars for KDE Frameworks 6.0.0 are now available for packagers, release
>> due next Wednesday
>>
>> http://embra.edinburghlinux.co.uk/~jr/tmp/6.0.0-release-data
>>
>>
>>

Re: KDE Frameworks 6.0.0 tars

[Jonathan Riddell]

   http://download.kde.org/stable/plasma/6.0.0/ktexteditor-6.0.0.tar.xz;>ktexteditor-6.0.0

   2.6MB
-
  
086c502231cd95861e47bcdad9e79bcbf200fd4c508b239af9ca6e78223f60b8
+
  
620266c1d288d09f7aee4d2bc8b141c73555d5f033c452bcd2e2db2064b8fd42

http://embra.edinburghlinux.co.uk/~jr/tmp/ktexteditor-6.0.0-changes_report.html

On Wed, 21 Feb 2024 at 11:44, Jonathan Riddell  wrote:

> Tars for KDE Frameworks 6.0.0 are now available for packagers, release due
> next Wednesday
>
> http://embra.edinburghlinux.co.uk/~jr/tmp/6.0.0-release-data
>
>
>

Fwd: KDE Frameworks 6.0.0 tars

[Jonathan Riddell]

Tars for KDE Frameworks 6.0.0 are now available for packagers, release due
next Wednesday

http://embra.edinburghlinux.co.uk/~jr/tmp/6.0.0-release-data

Re: What can we expect from our developers

[Jonathan Riddell]

My opinion is that KDE project maintainers should aspire to get the
projects into the hands of users in a way which makes it a useful tool for
the user.  That means ensuring the projects are packaged and distributed
and updated.  That's a big ask of course especially from volunteers but it
would be the same of self hosted open source projects on Github or
commercial proprietary projects, the difference is we have a community
process where if you aren't sure how to achieve something there is probably
other people who can help out.  When I first took over Umbrello 20 years
ago I was surprised that as well as learning C++ and Qt I'd also need to
know some artwork and how to make it translatable and follow UI design.
Actually making it available to users through app stores is another ask for
sure but it's why I'd like that integrated into processes like the KDE Gear
release service so projects can offload some of the work.  There seems to
be minimal interest in this though which I worry keeps KDE projects back.

Jonathan

KDE's 6th Megarelease RC 2

[Jonathan Riddell]

The tars for the final pre-release of the megarelease bundle are now
available for packaging
https://kde.org/announcements/megarelease/6/rc2/

Re: Ready-to-use Docker images for KF6-based development ?

[Jonathan Riddell]

*Sure, the Neon unstable one should be ready to go*
*invent-registry.kde.org/neon/docker-images/plasma:unstable
*

*You can try Distrobox to give it a go in a more managed way *
https://community.kde.org/Neon/Containers

Or manually something like
docker run -ti --volume="$HOME/.Xauthority:/root/.Xauthority:rw"
--network=host -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=:0
--security-opt seccomp=unconfined
invent-registry.kde.org/neon/docker-images/plasma:unstable bash



On Mon, 29 Jan 2024 at 21:18, Alexander Neundorf  wrote:

> Hi,
>
> I'm still running a Qt5/KF5-based setup on my machine.
> Is there a ready-to-use docker image/Dockerfile which I could use to work
> on a
> KF6-based application, maybe something from KDE neon ?
>
> Sorry for the maybe stupid question
> Alex
>
>
>
>

Re: KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

[Jonathan Riddell]

On Sat, 27 Jan 2024 at 17:26, Friedrich W. H. Kossebau 
wrote:

> [ ] App packages in Flatpak, Snap, AppImages and Windows etc as appropriate
>
> Not involved with any of those packages/platforms, but I assume that
> checkbox
> is rather some kind of "nice to have", not blocking the process actually?
>

This sort of comment  makes me really sad. The All About the Apps goal,
which in principle is still ongoing, was an attempt to get KDE developers
to realise it was important not just to write apps but to actually make
them available to users, I find it astonishing how we still don't have a
culture where making our apps available to users is part of our
responsibility.  There's teams in KDE to help with all these formats.
Sorry to complain here as the issue is larger than just this one app but
it's so sad that nobody within KDE wants to help get users using our
software directly.

Jonathan

KDE's 6th Megarelease RC 1

[Jonathan Riddell]

Release Candidate 1 for KDE's 6th Megarelease is now available for
packaging and testing
https://kde.org/announcements/megarelease/6/rc1/

It contains the release candidate for KDE Frameworks 6, Plasma 6 and all
the apps in KDE Gear.

Please review the release notes before packaging and testing
https://community.kde.org/Frameworks/6.0_Release_notes
https://community.kde.org/Plasma/Plasma_6.0_Release_notes
https://community.kde.org/KDE_Gear/24.02_Release_notes

KDE's 6th Megarelease RC 1

[Jonathan Riddell]

Release Candidate 1 for KDE's 6th Megarelease is now available for
packaging and testing
https://kde.org/announcements/megarelease/6/rc1/

It contains the release candidate for KDE Frameworks 6, Plasma 6 and all
the apps in KDE Gear.

Please review the release notes before packaging and testing
https://community.kde.org/Frameworks/6.0_Release_notes
https://community.kde.org/Plasma/Plasma_6.0_Release_notes
https://community.kde.org/KDE_Gear/24.02_Release_notes

KDE's 6th MegaRelease Beta 2

[Jonathan Riddell]

A second beta of Plasma 6, Frameworks 6 and KDE Gear 24.04 is out for
packaging and testing

https://kde.org/announcements/megarelease/6/beta2/

Re: Remove/ Archive Obsolete or Disabled Bugzilla Product/Components

[Jonathan Riddell]

These look good to remove from my knowledge as Plasma release manager and
distro packager

Jonathan

Ark Qt Version

[Jonathan Riddell]

I'm e-mailing everyone who has committed to Ark in the last year.

It's not on our list of KDE Gear apps which have been ported to Qt 6.  But
many distros are building it for Qt 6 and reporting it works fine.  If it's
not built for Qt 6 then people miss plugins in Dolphin and elsewhere.

Should we add it to the list of apps we recommend distros build with Qt 6?
This is for the currently in beta KDE Gear 24.02 version.

Jonathan

Re: Collection of packaging notes

[Jonathan Riddell]

On Fri, 10 Nov 2023 at 10:55, Christophe Marin  wrote:

> 3 different issues appeared with plasma 6 alpha:
>
>
- The CMake config names are identical for certain core libraries:
> KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt,
> LibKWorkspace,
>  LibTaskManager (and Breeze but it's slightly less problematic)
>
> - The CMake config files for DBus interface are not versioned:
> KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface,
> ScreenSaverDBusInterface
>

As discussed on Matrix our assumption is that Plasma 5 and 6 aren't
packaged together, a single version of Plasma should be packaged only with
the same version.


> - The libksysguard  libraries soversion weren't bumped. It's not only a
> problem for
> building plasma 5 and plasma 6. KSysguard is also an optional dependency
> for kdevelop.
>

I've bumped the soversions in libksysguard now. (I'll look at doing the
KFification for kuserfeedback too.)

I've also release noted that ksysguard the app is dead and should be
removed from distros, it hasn't been released for over 2 years and hasn't
been ported.

Jonathan

Frameworks 6 Alpha modules list

[Jonathan Riddell]

It's been agreed I'll make the release tomorrow, I'm updating version
numbers now. Here's the diff compared to KF5

+++ git-repositories-for-release-frameworks 2023-11-07
15:53:32.674589130 +
-kactivities
-kactivities-stats
+kcolorscheme
-kdelibs4support
-kdesignerplugin
-kdewebkit
-kemoticons
-khtml
-kinit
-kjs
-kjsembed
-kmediaplayer
-kross
+kstatusnotifieritem
+ksvg
+ktexttemplate
+kuserfeedback
-kwayland
-kxmlrpcclient
-oxygen-icons5
-plasma-framework

and complete one

attica
baloo
bluez-qt
breeze-icons
extra-cmake-modules
frameworkintegration
kapidox
karchive
kauth
kbookmarks
kcalendarcore
kcmutils
kcodecs
kcolorscheme
kcompletion
kconfig
kconfigwidgets
kcontacts
kcoreaddons
kcrash
kdav
kdbusaddons
kdeclarative
kded
kdesu
kdnssd
kdoctools
kfilemetadata
kglobalaccel
kguiaddons
kholidays
ki18n
kiconthemes
kidletime
kimageformats
kio
kirigami
kitemmodels
kitemviews
kjobwidgets
knewstuff
knotifications
knotifyconfig
kpackage
kparts
kpeople
kplotting
kpty
kquickcharts
krunner
kservice
kstatusnotifieritem
ksvg
ktexteditor
ktexttemplate
ktextwidgets
kunitconversion
kuserfeedback
kwallet
kwidgetsaddons
kwindowsystem
kxmlgui
modemmanager-qt
networkmanager-qt
prison
purpose
qqc2-desktop-style
solid
sonnet
syndication
syntax-highlighting
threadweave

Frameworks 6 release scripts

[Jonathan Riddell]

I've started the process of adapting the Plasma release scripts to
Frameworks (and other stuff generally hopefully).

https://invent.kde.org/sdk/releaseme/  work/frameworks branch

I've updated the scripts to get a list of repos and to make the tars.
Still to be done are stuff like updating the version numbers and Qt
versions, making web pages, changelogs and well everything else.

Here's the tars I got it to make, can someone check one or more of them to
see if they look correct and if the list of tars looks correct?
http://embra.edinburghlinux.co.uk/~jr/tmp/frameworks-5.245.0/

oxygen-icons5 needs renamed to oxygen-icons but that's done in gitlab I've
asked sysadmin to do that.

I know I'm probably not going to get anywhere but I'd advocate again
dropping oxygen-icons (and oxygen from Plasma) and do standalone releases,
it's the majority of disk space and creation time for these tars

This includes kuserfeedback which probably needs more framework-ification

> ncdu
  229.4 MiB [##]  oxygen-icons5-5.245.0.tar.xz
  15.1 MiB [  ]  kimageformats-5.245.0.tar.xz
   4.1 MiB [  ]  kwidgetsaddons-5.245.0.tar.xz
   3.3 MiB [  ]  syntax-highlighting-5.245.0.tar.xz
   3.3 MiB [  ]  kio-5.245.0.tar.xz
   3.0 MiB [  ]  knewstuff-5.245.0.tar.xz

Is this useful?  Should we use it for the release next Wednesday?  In which
case I'll continue with the rest of the work

Jonathan

Re: Collection of packaging notes

[Jonathan Riddell]

>
> If not, then why not fix any misnaming while we change names anyway.
>

Go for it :)

Jonathan

Re: Collection of packaging notes

[Jonathan Riddell]

Thanks for your e-mail.  It covers more than Frameworks so I'm including
release-team@ too.

One quick question, is naming non-frameworks libKF6foo really a problem we
need to fix?  Given all the other issues...

Jonathan


On Wed, 1 Nov 2023 at 10:55, Christophe Marin  wrote:

> Hello,
>
> With various alpha coming out soon, here are the notes added to my
> packages
> when I started packaging snapshots and still present.
>
> I'm well aware that some of these modules won't be present in the first
> releases.
>
> First, the most annoying issue:
> Plasma still didn't bump all their libraries soname. That's a major
> annoyance
> for packagers.
>
> - Conflicting files (not mentioned in the other thread)
> kcm_trash.desktop is installed by both kio (kf5) and kio-extras (kf6)
>
> - Conflicting translation catalog names:
> plasma-integration (plasmaintegration5)
> kuserfeedback
>
> - Misnamed libraries:
> kmail-account-wizard (liblibaccountwizard.so)
> ktextaddons (liblibvoskspeechtotext.so)
>
> - Non frameworks modules installing libKF*.so
> ktextaddons (various libraries)
> konqueror (libKF6Konq.so)
> libksane (libKF5Sane5.so)
> kweathercore (libKF6KWeatherCore.so)
> libktorrent (libKF5Torrent.so)
> libkexiv2 (libKF6KExiv2.so)
> libkdcraw (libKF6KDcraw.so)
> baloo-widgets (libKF6BalooWidgets.so)
> kmoretools (libKF6MoreTools.so)
> libkscreen (libKF6Screen.so, libKF6ScreenDpms.so)
>
> - Wrong install location for knewstuff files:
> khangman
> kturtle
>
> - Wrong install location for CMake files:
> qqc2-breeze-style (still uses KF5QQC2BreezeStyle)
>
> - old install location:
> kalgebra (/usr/share/katepart5. Note: syntax-highlighting won't ignore the
> file, but it's not the default location)
> ksystemlog (/usr/share/kxmlgui5/ksystemlog)
>
> - Modules still using QQC1:
> kdeplasma-addons (applets/fifteenPuzzle)
>
> - build dependency issues:
> plasma5support (links and requires QtGui but doesn't search for it at
> build
> time)
> kinfocenter (requires kpackage at build time but doesn't seem to need it)
>
>
> Christophe
>
>
>
>

Re: KUserFeedback as framework for KF6

[Jonathan Riddell]

I'm bumping this thread because this needs done pronto.  There's no
objections but also frameworks has quite exacting needs so it would be nice
to have a confirmation it would be good to include from someone who knows
about ABI needs etc.  But I'll include it when I get these release scripts
looked into.

Jonathan


On Sat, 15 Jul 2023 at 21:39,  wrote:

> Hi,
>
> several of our projects use it, like Plasma and Kate.
>
> Can we make it a framework for KF6?
>
> Then we have finally regular releases that include bug fixes.
>
> Is there some opposition to do that?
> I asked in the past but there was just no reaction.
>
> Greetings
> Christoph
>

Frameworks 6 alpha

[Jonathan Riddell]

We chatted about the alpha release due next Wednesday in the Frameworks
meeting today.

>From my notes:

- Frameworks would like do be part of this release

- Nico F, Alex S, David E are release spods

- There's not been any work on doing the tooling.  There's a desire to move
to releaseme for tooling.  Jonathan uses this plus a load of supporting
scripts for Plasma and will look at adapting that for Frameworks and come
up with a proposal

- Plasma would like to take over release of plasma-framework, kwayland and
kactivities and that presumably means also kactivities-stats.  There was
discussion on the problem of moving the gitlab entries for this while 5
releases are still ongoing so it's probably best to just leave that for now.

- oxygen-icons5 tar should be renamed oxygen-icons (again probably leave
gitlab repo renaming until later)
- We didn't discuss it but kirigami2 tar should also be renamed to kirigami

Does that seem right?

Anything else?

Jonathan

Re: KLook: are GPLv3 libraries acceptable for KDE?

[Jonathan Riddell]

https://community.kde.org/Policies/Licensing_Policy

LGPL compatible licence is needed for Frameworks etc, to quote from
above "*Source
files* that are part of a library with a public API which is part of the
KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks)".

But if it's a standalone library that's fine to be GPL, it's up to the apps
to make sure they're happy with that restriction/protection and most will
be.

Jonathan

Re: KF6 overlapping files

[Jonathan Riddell]

Here's a current list

'/usr/share/dbus-1/system.d/org.kde.kf5auth.conf' → libkf5auth-data
'/etc/xdg/ui/ui_standards.rc' → libkf5xmlgui-data
'/etc/xdg/accept-languages.codes' → kio
'/etc/xdg/kshorturifilterrc' → kio
'/usr/bin/kcookiejar5' → kio
'/usr/share/dbus-1/services/org.kde.kcookiejar5.service' → kio
'/usr/share/dbus-1/services/org.kde.kiod5.service' → kio
'/usr/share/dbus-1/services/org.kde.kioexecd.service' → kio
'/usr/share/dbus-1/services/org.kde.kpasswdserver.service' → kio
'/usr/share/dbus-1/services/org.kde.kssld5.service' → kio
'/usr/share/kconf_update/filepicker.upd' → kio
'/etc/xdg/autostart/baloo_file.desktop' → baloo-kf5
'/usr/lib/systemd/user/kde-baloo.service' → baloo-kf5
'/usr/share/plasma/desktoptheme/breeze-dark/colors' → plasma-framework
'/usr/share/plasma/desktoptheme/breeze-dark/metadata.json' →
plasma-framework
'/usr/share/plasma/desktoptheme/breeze-dark/plasmarc' → plasma-framework
'/usr/share/plasma/desktoptheme/breeze-light/colors' → plasma-framework
'/usr/share/plasma/desktoptheme/breeze-light/metadata.json' →
plasma-framework
'/usr/share/plasma/desktoptheme/breeze-light/plasmarc' → plasma-framework
'/usr/share/plasma/desktoptheme/default/dialogs/background.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/akonadi.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/akregator.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/amarok.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/applications.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/apport.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/audio.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/battery.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/bookmarks.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/cantata.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/computer.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/configure.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/device.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/disk.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/distribute.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/document.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/drive.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/edit.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/fcitx.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/go.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/ime.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/input.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kalarm.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kdeconnect.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/keyboard.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kget.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kgpg.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kleopatra.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/klipper.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kmail.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/konv_message.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/konversation.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kopete.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/korgac.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kpackagekit.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kruler.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kteatime.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/ktorrent.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/kup.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/list.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/mail.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/media.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/mobile.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/network.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/notification.svgz' →
plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/osd.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/phone.svgz' → plasma-framework
'/usr/share/plasma/desktoptheme/default/icons/plasmavault.svgz' →
plasma-framework

Re: Suggestion to drop kopete from KDE Gear

[Jonathan Riddell]

I'd agree on this having taken a quick look at it, I can't see a useful
function for this app any more.

Jonathan


On Fri, 28 Jul 2023 at 22:15, Heiko Becker  wrote:

> Hello,
>
> I wanted to keep kopete at least buildable against recent version of its
> dependencies by removing some obsolete parts. But it occured to me that if
> I were to continue with that, there wouldn't be much left. It suffers from
> the same problems with dead or (at least dying) protocols I wrote down for
> ktp [1], so I'll just add some relevant things affecting kopete:
>
> - Contrary to ktp it doesn't use pidgin for ICQ/AIM, but a custom
> implementation, the result is the same. AIM ceased to exist and ICQ
> changed
> its protocol (and thus kopete silently fails to with the latter).
> - XMPP/Jabber allows to connect, but joining a room crashes kopete, which
> matches a bug report from 2019 [2]
> - winpopup was apparently discontinued after Windows XP
> - qq: I'm hesistant to give them my phone number to manually register an
> account (the link behind the register button times out). Pidgin removed
> support for this in 2011, which is roughly the same time a non-porting
> commit touched the code and there is a bug report that it indeed doesn't
> work [3]
>
> I didn't have/find an instance to test Bonjour and my distro doesn't
> provide a package for libmeanwhile, so no testing of these.
>
> In addition, it has a very long list of (partly very old) bugs [4] (no
> idea
> how many, bugzilla stops after 500), and my impression from testing a few
> is that many of them are easily reproduceably today.
>
> As much as I used kopete for chatting back in the day, I seriously think
> it's broken enough to stop shipping it with Gear, if nobody surprisingly
> steps up and does at least some basic maintenance.
>
> If you know anybody who's still around and cares for kopete, please feel
> free to bring this mail to their attention.
>
> Regards,
> Heiko
>
> [1] https://mail.kde.org/pipermail/release-team/2023-June/013080.html
> [2] https://bugs.kde.org/show_bug.cgi?id=412228
> [3] https://bugs.kde.org/show_bug.cgi?id=460744
> [4]
>
> https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=ASSIGNED_status=REOPENED_id=2429758=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id=kopete_format=advanced
>

Re: Phonon Backends

[Jonathan Riddell]

Indeed, we seem to have the capitalised headers but lower-case "phonon"
includes back with the changes Harald has recently made, phonon-vlc and
dolphin etc now compile again.  Qt 5 and Qt 6 now seem to need separate
compiles.

Jonathan


On Fri, 21 Jul 2023 at 10:20, Volker Krause  wrote:

> On Wednesday, 19 July 2023 16:46:55 CEST Jonathan Riddell wrote:
> > Hola, I see Volker has stopped installing the capitalised headers for
> > Phonon.
> >
> > This breaks the build of phonon-vlc.  Are there any plans to update it?
>
> phonon-vlc uses lower-case namespace includes, so I rather suspect this is
> unintended fallout from https://invent.kde.org/libraries/phonon/-/
> merge_requests/14
> <https://invent.kde.org/libraries/phonon/-/merge_requests/14> which
> should have been fixed meanwhile.
>
> Adding a Qt6 CI job for phonon-vlc would also help I guess.
>
> Regards,
> Volker

Phonon Backends

[Jonathan Riddell]

Hola, I see Volker has stopped installing the capitalised headers for
Phonon.

This breaks the build of phonon-vlc.  Are there any plans to update it?

(I'm not sure if this is the right place to discuss Phonon.)

Jonathan

KF6 overlapping files

[Jonathan Riddell]

I thought I'd give an update on current overlapping files since our
automated setup isn't running just now..

 kf6-kxmlgui (0.0+p22.04+tunstable+git20230708.0126-0) over
(0.0+p22.04+tunstable+git20230701.0107-0) ...
'/etc/xdg/ui/ui_standards.rc' libkf5xmlgui-data

 kf6-kio (0.0+p22.04+tunstable+git20230711.0449-0) over
(0.0+p22.04+tunstable+git20230703.0257-0) ...
'/etc/xdg/accept-languages.codes' kio
'/etc/xdg/kshorturifilterrc' kio
'/usr/bin/kcookiejar5' kio
'/usr/share/dbus-1/services/org.kde.kcookiejar5.service' kio
'/usr/share/dbus-1/services/org.kde.kiod5.service' kio
'/usr/share/dbus-1/services/org.kde.kioexecd.service' kio
'/usr/share/dbus-1/services/org.kde.kpasswdserver.service' kio
'/usr/share/dbus-1/services/org.kde.kssld5.service' kio
'/usr/share/kconf_update/filepicker.upd' kio

 kf6-baloo (0.0+p22.04+tunstable+git20230711.0216-0) over
(0.0+p22.04+tunstable+git20230701.0101-0) ...
'/etc/xdg/autostart/baloo_file.desktop' baloo-kf5
'/usr/lib/systemd/user/kde-baloo.service' baloo-kf5

 kf6-kglobalaccel-dev (0.0+p22.04+tunstable+git20230705.0803-0) over
(0.0+p22.04+tunstable+git20230701.0128-0) ...
'/usr/share/dbus-1/interfaces/kf5_org.kde.KGlobalAccel.xml'
libkf5globalaccel-dev
'/usr/share/dbus-1/interfaces/kf5_org.kde.kglobalaccel.Component.xml'
libkf5globalaccel-dev

 kf6-kwallet (0.0+p22.04+tunstable+git20230708.0144-0) over
(0.0+p22.04+tunstable+git20230703.0249-0) ...
'/usr/bin/kwallet-query' libkf5wallet-bin
'/usr/bin/kwalletd5' libkf5wallet-bin
'/usr/share/applications/org.kde.kwalletd5.desktop' libkf5wallet-bin
'/usr/share/dbus-1/services/org.kde.kwalletd5.service' libkf5wallet-bin
'/usr/share/man/man1/kwallet-query.1.gz' libkf5wallet-bin


 kf6-knotifications-dev (0.0+p22.04+tunstable+git20230708.0123-0) over
(0.0+p22.04+tunstable+git20230703.0121-0) ...
'/usr/share/dbus-1/interfaces/kf5_org.kde.StatusNotifierItem.xml'
libkf5notifications-dev
'/usr/share/dbus-1/interfaces/kf5_org.kde.StatusNotifierWatcher.xml'
libkf5notifications-dev

 kf6-kguiaddons (0.0+p22.04+tunstable+git20230711.0102-0) over
(0.0+p22.04+tunstable+git20230701.0112-0) ...
'/usr/bin/kde-geo-uri-handler' libkf5guiaddons-bin
'/usr/share/applications/google-maps-geo-handler.desktop'
libkf5guiaddons-data
'/usr/share/applications/openstreetmap-geo-handler.desktop'
libkf5guiaddons-data
'/usr/share/applications/qwant-maps-geo-handler.desktop'
libkf5guiaddons-data
'/usr/share/applications/wheelmap-geo-handler.desktop' libkf5guiaddons-data

 kf6-kauth (0.0+p22.04+tunstable+git20230705.0759-0) over
(0.0+p22.04+tunstable+git20230630.0252-0) ...
'/usr/share/dbus-1/system.d/org.kde.kf5auth.conf' libkf5auth-data

Re: PokiPoki in KDEReview

[Jonathan Riddell]

Do you have any intention to follow up on this Carson?

Jonathan


On Tue, 4 Jul 2023 at 13:52, Jonathan Riddell  wrote:

> I created an issue for this in line with the new kdereview process
>
> https://invent.kde.org/libraries/pokipoki/-/issues/1
>
> Jonathan
>
>
> On Wed, 26 Aug 2020 at 20:28, Carson Black  wrote:
>
>> Hi y'all!
>>
>> I'd like to see PokiPoki go through KDEReview and eventually end up
>> releasing as an extragear library.
>>
>> PokiPoki is a framework that aims to make persistent objects as
>> trivial to use as possible and provides other sugar functionality on
>> top of simply persisting objects, such as an undo/redo stack.
>>
>> From a code overview, PokiPoki is split into two main parts:
>> libpokipoki and pokic. libpokipoki is a small helper library that
>> provides types used by pokic while pokic is a code generator that
>> consumes .pokipoki files to generate a header-only library that can be
>> included in a project.
>>
>> libpokipoki is authored in C++ for obvious reasons, while pokic is
>> authored in Go due to the extensive text templating system used for
>> code generation and the lexer in the stdlib used for reading pokipoki
>> files.
>>
>> poki-compiler/parser/output.go will probably be the file that needs
>> most looking at, as it's responsible for the code generation.
>>
>> Cheers,
>> -- Carson Black
>>
>

Re: RKWard is in kdereview - again

[Jonathan Riddell]

I've created an issue for the kdereview process

https://invent.kde.org/education/rkward/-/issues/23

Jonathan


On Sat, 26 Mar 2022 at 20:34, Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net> wrote:

> Hi!
>
> KDE.org has been our home for a 7.5(!) years, now (after over a
> decade on sourceforge), but we still haven't left playground... After a
> lot of procrastination on that matter, a previous review failed due to
> lack of time on my part. Sorry! Now, finally, I'd like to ask you to
> start reviewing RKWard for inclusion into exragear / education, once
> more.
>
> RKWard is an easy to use and easily extensible IDE/GUI for R (a
> powerful language and environment for statistical computing, if you
> did not know it, yet). It aims to combine the power of the
> R-language with the ease of use of commercial statistics tools.
>
> RKWard is used productively on Linux/BSD, Mac, and Windows.
>
>
>
> Here's a summary of the critical comments we got in the previous round
> of review (https://marc.info/?l=kde-core-devel=153883367600690=2):
>
> Albert Astals Cid remarked
> (https://marc.info/?l=kde-core-devel=153912336114603=2):
>
> > the i18n folder seems like from the past and something you should not
> > need if in kde infrastructure. Could you delete it?
>
> We cannot easily get rid of this, entirely, as we are shipping
> (non-compiled) plugins that keep their message catalogs in relative
> paths, and thus we have to install .mo files to custom locations. Pino
> Toscano has helped to bring this more in line with standard KDE.org
> processes (https://invent.kde.org/education/rkward/-/merge_requests/2).
>
> > Also I'd suggest you compile enabling
> > -DECM_ENABLE_SANITIZERS="address;undefined"
>
> Thanks for the hint, did not know that switch. One effect of this is a
> lot of false positive "runtime errors", when casting a half-destroyed
> QObject* to its original (derived) type, in order to remove it from
> containers (e.g. a QHash of KActionCollection()s). Is there an elegant
> way around this?
>
> > There's a few memory leaks (reported at exit) that you may want to
> > have a look.
>
> I fixed a lot of that, but didn't work out all of them.
>
> > And there's also a few undefined behaviour warnings on exit, you've
> > them marked as "known" things but it'd be good if you could find a way
> > to fix them.
>
> Not quite sure what you were referring to, esp. what I may have marked
> as known behavior. I did fix several quirks at exit since this comment
> (and I keep introducing new ones, all the time).
>
> > Your help menu is for some reason missing the Change Language option,
> > i tried to do it a quick fix but could not, i would appreciate if you
> > could find a way to only define the extra actions and not all of them
> > (like we do for example in okular).
>
> I've added the switch application language option (in Settings rather
> than Help). Our help menu is perhaps more customized than meets the eye
> on first glance. For instance, we have an app-integrated help system
> instead of external handbook (at least as the primary documentation),
> and our bug report dialog is beefed up to include a lot of extra
> information by default (mostly importantly: version of R). I guess it
> would be possible to hack KHelpMenu this way, but at least at some
> point in the past it seemed cleaner to implement "from scratch" (but
> using the default actions, where applicable).
>
>
>
> Comments by Jonathan Riddel
> (https://marc.info/?l=kde-core-devel=153916691226377=2):
>
> > It installs two desktop files which creates duplicate menu entries
> > /usr/share/applications/org.kde.rkward-open.desktop
> > /usr/share/applications/org.kde.rkward.desktop
>
> Completed following suggestions by Thomas Baumgart and Meik Michalke:
> https://marc.info/?l=kde-core-devel=153942961310071=2
>
> > The .desktop files call it a "GUI for R" which is not a great
> > description, everything in the menu is a GUI.  I recommend "R
> > Statistical Programming" or "IDE for R" maybe.
>
> Renamed to Statistics with R, following Meik's suggestion
> (https://marc.info/?l=kde-core-devel=153942595709279=2).
>
> > I tidied up the files with the icon licence as they could easily be
> > lost.
>
> Done by Jonathan.
>
> > It depends on WebKit which is not supported, could this be ported to
> > WebEngine?
>
> Meanwhile, RKWard can be compiled to use QtWebEngine (and this is the
> default), but support for webkit has not been dropped, because MinGW is
> an important platform for us.
>
> > It's uncommon having debian/ packaging directly in the source and
> > there's also debian-official/ which could get confusing and
> > out-of-sync and messy.  I recommend moving them to another archive.
> > Storing the packaging in KDE neon Git would be cool as we already
> > have packaging for all the rest of KDE software.
>
> Meanwhile packaging has been taken over by the debian-qt-kde team
> (thank you so much!). Jonathan himself added RKWard to neon. We still
> 

Re: PokiPoki in KDEReview

[Jonathan Riddell]

I created an issue for this in line with the new kdereview process

https://invent.kde.org/libraries/pokipoki/-/issues/1

Jonathan


On Wed, 26 Aug 2020 at 20:28, Carson Black  wrote:

> Hi y'all!
>
> I'd like to see PokiPoki go through KDEReview and eventually end up
> releasing as an extragear library.
>
> PokiPoki is a framework that aims to make persistent objects as
> trivial to use as possible and provides other sugar functionality on
> top of simply persisting objects, such as an undo/redo stack.
>
> From a code overview, PokiPoki is split into two main parts:
> libpokipoki and pokic. libpokipoki is a small helper library that
> provides types used by pokic while pokic is a code generator that
> consumes .pokipoki files to generate a header-only library that can be
> included in a project.
>
> libpokipoki is authored in C++ for obvious reasons, while pokic is
> authored in Go due to the extensive text templating system used for
> code generation and the lexer in the stdlib used for reading pokipoki
> files.
>
> poki-compiler/parser/output.go will probably be the file that needs
> most looking at, as it's responsible for the code generation.
>
> Cheers,
> -- Carson Black
>

Re: KCGroups in KDEreview

[Jonathan Riddell]

I opened an issue in line with the new kdereview process

https://invent.kde.org/libraries/kcgroups/-/issues/1

Jonathan


On Sat, 21 Nov 2020 at 00:38, Albert Astals Cid  wrote:

> El divendres, 20 de novembre de 2020, a les 14:55:16 CET, Henri Chain va
> escriure:
> > Hello everyone,
> >
> > KCgroups has been moved to KDEReview !
> > What is that, you ask ? It's a library that wraps the systemd dbus API
> to
> > expose a higher-level concept of desktop application and allow control
> of its
> > system resource usage (CPU, RAM, IO, etc).
> >
> > It relies on the recent ability of plasma to launch applications in
> their own
> > systemd scopes, with correspond to cgroups and provides a more robust
> > definition for an application (more details at
> https://lwn.net/Articles/834329/
> > ) .
> >
> > The main use of the library is to expose related resource control
> settings for
> > those applications, at a user space level that other KDE applications
> and
> > frameworks can use, including consumption straight from QML as
> demonstrated in
> > the test application.
> >
> > KCgroups is intended to become a (Tier 1) framework. A first user of
> this
> > library might be the foreground window CPU booster daemon that is
> available
> > here:
> https://invent.kde.org/libraries/kcgroups/-/tree/work/foreground-booster
> >
> > Packages are already available for both Neon and Arch Linux.
> >
> > Looking forward to your feedback and ideas for using this,
>
> I'm a bit scared about your optional class being there all in the main
> namespace. I'd suggest putting in some "namespace kcgroups{}" or name it
> kcgoptional or something.
>
> you have a few properties without NOTIFY, ideally you should either add it
> if they can change or mark them as CONSTANT if they can't.
>
> Cheers,
>   Albert
>
>
> > Henri
> >
> >
> >
>
>
>
>
>

Re: KCGroups in KDEreview

[Jonathan Riddell]

I opened an issue in line with the new kdereview process

https://invent.kde.org/libraries/kcgroups/-/issues/1

Jonathan


On Sat, 21 Nov 2020 at 00:38, Albert Astals Cid  wrote:

> El divendres, 20 de novembre de 2020, a les 14:55:16 CET, Henri Chain va
> escriure:
> > Hello everyone,
> >
> > KCgroups has been moved to KDEReview !
> > What is that, you ask ? It's a library that wraps the systemd dbus API
> to
> > expose a higher-level concept of desktop application and allow control
> of its
> > system resource usage (CPU, RAM, IO, etc).
> >
> > It relies on the recent ability of plasma to launch applications in
> their own
> > systemd scopes, with correspond to cgroups and provides a more robust
> > definition for an application (more details at
> https://lwn.net/Articles/834329/
> > ) .
> >
> > The main use of the library is to expose related resource control
> settings for
> > those applications, at a user space level that other KDE applications
> and
> > frameworks can use, including consumption straight from QML as
> demonstrated in
> > the test application.
> >
> > KCgroups is intended to become a (Tier 1) framework. A first user of
> this
> > library might be the foreground window CPU booster daemon that is
> available
> > here:
> https://invent.kde.org/libraries/kcgroups/-/tree/work/foreground-booster
> >
> > Packages are already available for both Neon and Arch Linux.
> >
> > Looking forward to your feedback and ideas for using this,
>
> I'm a bit scared about your optional class being there all in the main
> namespace. I'd suggest putting in some "namespace kcgroups{}" or name it
> kcgoptional or something.
>
> you have a few properties without NOTIFY, ideally you should either add it
> if they can change or mark them as CONSTANT if they can't.
>
> Cheers,
>   Albert
>
>
> > Henri
> >
> >
> >
>
>
>
>
>

Re: KQuickChatComponents in kdereview

[Jonathan Riddell]

I opened an issue in line with the new kdereview process
https://invent.kde.org/libraries/kquickchatcomponents/-/issues/1

Jonathan


On Fri, 31 Dec 2021 at 11:35, Janet Blackquill  wrote:

> Hi,
>
> KQuickChatComponents
> (https://invent.kde.org/libraries/kquickchatcomponents) is in
> kdereview now.
>
> It is a very small (as of now) library mostly containing a base bubble
> component offering a consistent bubble design, with a few variants
> built on top of the bubble offering common patterns of chat things
> with bubble backgrounds and layouts. Besides the timestamp component,
> that's pretty much it, since chat apps need to diverge heavily to
> accomodate their protocols. This library's purpose is mostly for
> getting KDE's plethora of QtQuick chat apps to converge on one (1)
> bubble design instead of a different look per app, as well as other
> details like the selection of shortcuts used for common chat app
> actions (see MR !2)
>
> -- Janet
>

Re: kpeoplevcard in kdereview

[Jonathan Riddell]

I opened an issue in line with the new kdereview process

https://invent.kde.org/pim/kpeoplevcard/-/issues/1

Jonathan


On Sat, 12 Jun 2021 at 14:56, Nicolas Fella  wrote:

> Hi,
>
> https://invent.kde.org/pim/kpeoplevcard is now in kdereview.
>
> kpeoplevcard is a data source plugin for KPeople that provides contacts
> based on VCard files on the disk. The 0.1 release has been in use in
> plasma-phonebook and kdeconnect-sms for a while, but I just realized it
> was never properly reviewed.
>
> I did some cleanup work to bring the repo up to standards, but in
> general the thing is rather "finished". There is a pending MR adding
> full REUSE compliance waiting for approval from the copyright holders.
>
> Cheers
>
> Nico
>
>

Re: Eloquens now on KDEREVIEW

[Jonathan Riddell]

I opened an issue in line with the new process
https://invent.kde.org/sdk/eloquens/-/issues/1

Jonathan


On Mon, 20 Jun 2022 at 21:30, Felipe Kinoshita  wrote:

> For those who don't know, Eloquens is a simple application targeted at
> developers/designers, it generates the lorem ipsum text and allows you to
> customize it a little bit like adding heading, bullet lists, etc...
>
> I would also like to ask if it would be possible for it to be released
> along with KDE Gear.
>
> Thanks,
> Felipe
>

Re: KSvg in kdereview

[Jonathan Riddell]

I opened an issue in line with the new process

https://invent.kde.org/frameworks/ksvg/-/issues/2

Jonathan


On Thu, 20 Apr 2023 at 09:26, Marco Martin  wrote:

> Hi all,
> A part of plasma-framewrok, which is the one to do SVG-based themes,
> has now been splitted in a standalone library which is intended to be
> a new framework in KF6 (all usages of the plasma-framework version
> will be ported once this officially lands, and then those classes will
> be removed)
> The repo for now lives in
> https://invent.kde.org/libraries/plasmasvg
>
> In the end it will be renamed in ksvg
>
> Comments? reviews?
>
>
> --
> Marco Martin
>

Re: XWayland Video Bridge in kdereview

[Jonathan Riddell]

I opened an issue in line with the new process

https://invent.kde.org/system/xwaylandvideobridge/-/issues/2



On Fri, 16 Jun 2023 at 17:44, Aleix Pol  wrote:

> Hi Everyone,
> As discussed by david in his blog post [1], we worked on the component
> in question to solve the problem of X11 applications that want to use
> the screencasting services on Wayland.
>
> https://invent.kde.org/system/xwaylandvideobridge
>
> While there's some corners to polish here and there, it's ready to be
> used by everyone who needs it. In fact, people are using it from the
> flatpak and distros want to ship it so we should probably make it
> easier and regulated through a proper release.
>
> First it should go through kdereview, then I'd suggest starting to
> release it with Plasma 5.27 in one of the minor releases. I don't
> think it's something we have done before but it doesn't add new
> dependencies and it has an impact in our product offering which is,
> incidentally, frozen due to the switch to *6.
>
> I would appreciate the review of the module, I guess the "how to
> release it" is something we can discuss in a couple of weeks once this
> is sorted.
>
> Thanks everyone!
> Aleix
>
> [1] https://blog.davidedmundson.co.uk/blog/xwaylandvideobridge/
>

Re: Move Licentia to KDEREVIEW

[Jonathan Riddell]

I opened an Issue in line with the new practice
https://invent.kde.org/sdk/licentia/-/issues/2


On Tue, 8 Nov 2022 at 02:14, Felipe Kinoshita  wrote:

> Yes, I'm still interested in working on them, just lost motivation because
> it was taking too long for someone to review it.
>
> On Thu, Nov 3, 2022, 09:44 Jonathan Riddell  wrote:
>
>> Same question on this one Felipe, are you still interested in working on
>> the app?  It seems stuck in kdereview with no recent development.
>>
>> Jonathan
>>
>>
>> On Fri, 8 Jul 2022 at 06:37, Felipe Kinoshita  wrote:
>>
>>> Hey, I'd like to move Licentia <https://invent.kde.org/sdk/licentia> to
>>> KDEREVIEW.
>>>
>>> Licentia is a simple app targeted at developers/creators who need to
>>> decide which license is suited to their projects, Licentia helps with that
>>> by listing a bunch of licenses, which with it's permissions, conditions and
>>> limitations, instructions about how to add a license to your project and a
>>> list of known projects that use said license.
>>>
>>> Thanks,
>>> Felipe.
>>>
>>

Re: Proposal for using gitlab for kdereview process

[Jonathan Riddell]

I've gone ahead an updated the Sanity checklist and updated the kde review
policy to ask people to make an Issue on gitlab labelled "KDE Review
Request"

https://community.kde.org/Policies/Application_Lifecycle#kdereview

So you can now find kdereview requests at
https://invent.kde.org/dashboard/issues?sort=created_date=opened_name[]=KDE+Review+Request

Which is linked from
https://community.kde.org/Policies/Application_Lifecycle#kdereview

I'll open Issues for outstanding kdereview projects.

Jonathan



On Mon, 19 Jun 2023 at 19:55, Jonathan Riddell  wrote:

> Seems using issues is more intuitive so I'll ask for a global group label
> for issues and update the process docs for kdereview and incubator.
>
> Incubator suggestion is here
> https://discuss.kde.org/t/proposal-kde-invent-based-incubator-process/
>
> Jonathan
>
>
> On Wed, 1 Mar 2023 at 08:27, David Redondo  wrote:
>
>> So there are two new kdereview requests using gitlab issues now instead
>> of my
>> more complicated idea of merge requests. I imagined a MR to have
>> advantages
>> for codereview but an issue seems to be less complicated (no need to have
>> an
>> empty orphan branch, etc..), so maybe we should go with that.
>>
>> David
>>
>>
>>

Re: [ANNOUNCE] GammaRay 2.11.0

[Jonathan Riddell]

Hi Allan, I'm getting queries about having Gammaray support Qt 6 and KF6
for our KDE neon packages.  Do you have plans for any new release?

Jonathan


On Fri, 5 Jul 2019 at 19:10, Allen Winter  wrote:

> Announcing GammaRay 2.11.0
>
> Highlights of this Release:
> =
>  * Drop support for Qt 4 and Qt <= 5.4.
>  * Drop support for MSVC 2010 and MSVC 2012, as well as GCC < 4.8.
>  * Add support for more QtNetwork properties.
>  * Add new network operations monitoring tool.
>  * Fix inspection of QJson types.
>  * Add thread affinity check to the problem reporter.
>  * Add new event monitoring tool.
>  * Initial forward compatibility with Qt6 build system.
>  * Improved performance of the Qt Quick 2 inspector and the signal monitor.
>
> The source code can be found on GitHub at:
> https://github.com/KDAB/GammaRay
> Tarballs and zipballs for v2.11.0 are available from:
> https://github.com/KDAB/GammaRay/releases
>
> For Linux users:
>  * we provide pre-built packages for some popular distributions at:
> https://software.opensuse.org/package/gammaray
>
> For OSX users:
>  * we provide a homebrew recipe, see:
> https://github.com/KDAB/homebrew-tap
>
> For Windows users:
>  * you'll need to build from source
>
> GammaRay is a tool to poke around in a Qt-application and also to
> manipulate
> the application to some extent. GammaRay uses various DLL injection
> techniques to hook into an application at runtime and provide access to a
> lot of interesting information.
>
> For more information about GammaRay, please see:
>  * the KDAB GammaRay home page at http://www.kdab.com/gammaray
>  * the GammaRay wiki at https://github.com/KDAB/GammaRay/wiki
>  * the GammaRay User Manual at
> https://docs.kdab.com/gammaray-manual/latest/
>  * the GammaRay API doc at https://docs.kdab.com/gammaray/latest/
>
> --
> Allen Winter | allen.win...@kdab.com | Senior Software Engineer
> KDAB (USA) LLC, a KDAB Group company
> Tel. USA +1-866-777-KDAB(5322) ext3
> KDAB - The Qt, C++ and OpenGL Experts
>

Re: version numbers towards kf6

[Jonathan Riddell]

Use whatever you like for your distro but for neon we have the not very
elegant

5.92.0+p22.04+tunstable+git20230613.2104-0 for git master frameworks build

frameworks version, ubuntu version, neon edition, date.time, build number.

Of course the frameworks version is meaningless there, it's just where I
took the first packaging from, I'll update that once the frameworks get
releases.

Jonathan

Re: XWayland Video Bridge in kdereview

[Jonathan Riddell]

I got this compiling on neon unstable.  Our kpipewire is qt6 so I'm not
sure how that affects it.  I don't have a way to test it quickly though.
https://build.neon.kde.org/job/jammy_unstable_neon-packaging_xwaylandvideobridge/

How come it's in the system group on invent if you want it to be part of
Plasma?

Jonathan



On Fri, 16 Jun 2023 at 17:44, Aleix Pol  wrote:

> Hi Everyone,
> As discussed by david in his blog post [1], we worked on the component
> in question to solve the problem of X11 applications that want to use
> the screencasting services on Wayland.
>
> https://invent.kde.org/system/xwaylandvideobridge
>
> While there's some corners to polish here and there, it's ready to be
> used by everyone who needs it. In fact, people are using it from the
> flatpak and distros want to ship it so we should probably make it
> easier and regulated through a proper release.
>
> First it should go through kdereview, then I'd suggest starting to
> release it with Plasma 5.27 in one of the minor releases. I don't
> think it's something we have done before but it doesn't add new
> dependencies and it has an impact in our product offering which is,
> incidentally, frozen due to the switch to *6.
>
> I would appreciate the review of the module, I guess the "how to
> release it" is something we can discuss in a couple of weeks once this
> is sorted.
>
> Thanks everyone!
> Aleix
>
> [1] https://blog.davidedmundson.co.uk/blog/xwaylandvideobridge/
>

Re: Proposal for using gitlab for kdereview process

[Jonathan Riddell]

Seems using issues is more intuitive so I'll ask for a global group label
for issues and update the process docs for kdereview and incubator.

Incubator suggestion is here
https://discuss.kde.org/t/proposal-kde-invent-based-incubator-process/

Jonathan


On Wed, 1 Mar 2023 at 08:27, David Redondo  wrote:

> So there are two new kdereview requests using gitlab issues now instead of
> my
> more complicated idea of merge requests. I imagined a MR to have
> advantages
> for codereview but an issue seems to be less complicated (no need to have
> an
> empty orphan branch, etc..), so maybe we should go with that.
>
> David
>
>
>

Re: XWayland Video Bridge in kdereview

[Jonathan Riddell]

I don't want to add it to the Plasma release for a bugfix version.  But
I'll happily release it alongside it.

Jonathan


On Mon, 19 Jun 2023 at 09:48, Sandro Knauß  wrote:

> Hey,
>
> > First it should go through kdereview, then I'd suggest starting to
> > release it with Plasma 5.27 in one of the minor releases. I don't
> > think it's something we have done before but it doesn't add new
> > dependencies and it has an impact in our product offering which is,
> > incidentally, frozen due to the switch to *6.
>
> With my Debian hat on: Please make sure nothing depend on this new
> application
> for 5.27.
> Background: We successfully could convinced the Debian release team, that
> it
> is safe to ship new minor Plasma releases to Debian stable with the result
> shipping 5.27.5 in bookworm (released some days ago). The main reason was
> that
> the minor releases are only bugfix releases and no new features are added.
> If you do not break this rule, that we can ship the minor releases to
> bookworm
> (without XWayland Video Bridge, as no new applications are allowed).
>
> Regards,
>
> hefee
>
>
>

Re: kf6 deconflictor progress

[Jonathan Riddell]

I've updated the deconflictor now

https://build.neon.kde.org/job/test_kf6_deconflictor/lastSuccessfulBuild/artifact/conflict-report.json/*view*/

On Tue, 2 May 2023 at 09:35, David Edmundson 
wrote:

> On Fri, Apr 28, 2023 at 5:59 PM Jonathan Riddell  wrote:
> >
> > The deconflictor job we run in neon still has a bunch of files
> overlapping between kf5 and kf6
> >
> > https://build.neon.kde.org/job/test_kf6_deconflictor/
> >
> >
> https://build.neon.kde.org/job/test_kf6_deconflictor/9/artifact/conflict-report.json/*view*/
> >
> > Is there any progress being made in fixing this?
>
> Any, yes.
> Obviously it's not done yet.
>
> I'm not sure this report is up to date:
>
> "/usr/kf6/bin/kglobalaccel5",
> "/usr/bin/kglobalaccel5"
>
> I can't see us installing that.
>
> > We'd like to move the neon packages into /usr which would break our
> deconflicting report job.
>
> You know how to make progress faster :)
>
> > Jonathan
> >
>

kf6 deconflictor progress

[Jonathan Riddell]

The deconflictor job we run in neon still has a bunch of files overlapping
between kf5 and kf6

https://build.neon.kde.org/job/test_kf6_deconflictor/

https://build.neon.kde.org/job/test_kf6_deconflictor/9/artifact/conflict-report.json/*view*/

Is there any progress being made in fixing this?

We'd like to move the neon packages into /usr which would break our
deconflicting report job.

Jonathan

Proposal to deprecate KFloppy

[Jonathan Riddell]

KFloppy is an old tool to format your floppy diskettes.  We packaged
KFloppy for the Snap store but it doesn't work, neither does it work for
the apt packages.  The code depends on features of Linux that do not seem
to exist any more, expecting /dev/fd0 and other nodes in /dev.  It also
depends on having tools like fdformat around which are not packages for
Ubuntu any more.  I tested it with an external USB floppy drive.  The most
recent maintainer seems to be Wolfgang Bauer.  Can we agree to archive it
and stop releases?

Jonathan

Re: kf6 vs. kf5 conflict report

[Jonathan Riddell]

Also from kxmlgui is a clash
/etc/xdg/ui/ui_standards.rc

Jonathan

Re: KDE Review: Arianna

[Jonathan Riddell]

The epub.js is not in preferred modifiable form.  It's cleartext but it's
not the source as anyone would want to edit it.  The comment at the end
says it comes from a mapping called sourceMappingURL=epub.js.map so the
full source of this should be included.

Jonathan


On Sat, 25 Feb 2023 at 13:59, Carl Schwan  wrote:
>
> Hi folks,
>
> I want to move Arianna to KDE review. Arianna is an ebook reader
> currently only supporting epubs. This is based on top of epub.js
> and QtWebEngine for the actualy rendering of ebooks as doing that
> from scratch in Qt would be too much work.
>
> The repo can be found here: https://invent.kde.org/graphics/arianna/
>
> I create a gitlab issue to track the progress of this:
> https://invent.kde.org/graphics/arianna/-/issues/1 Please free to add
> your comments as recently suggested in this mailing list.
>
> Cheers,
> Carl

Re: Re : New repo in kdereview: PlasmaTube

[Jonathan Riddell]

Oh yes now I remember it needs a new version of the fork yt-dlp, give that
it works fine.

So might be worth adding a compile time and/or runtime check for the right
version there.

Jonathan


On Mon, 27 Feb 2023 at 13:14, Jonathan Riddell  wrote:

> When I compile this and play a video I get an error suggesting youtube-dl
> isn't happy.  I'm using youtube-dl from Ubuntu which is versioned
> 2021.12.17-1 and looking at the
> https://ytdl-org.github.io/youtube-dl/download.html site that is the
> latest version
>
>
> Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
> kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
> qrc:/videoplayer/VideoControls.qml:243:5: QML Dialog: Binding loop
> detected for property "implicitHeight"
> qrc:/videoplayer/VideoControls.qml:243:5: QML Dialog: Binding loop
> detected for property "implicitHeight"
> qrc:/components/Sidebar.qml:9:1: QML Sidebar: Binding loop detected for
> property "contentHeight"
> qrc:/videoplayer/VideoControls.qml:122: ReferenceError: UserPlaylistModel
> is not defined
> qrc:/videoplayer/VideoControls.qml:193: ReferenceError: UserPlaylistModel
> is not defined
> file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
> QML MouseArea: Binding loop detected for property "implicitHeight"
> file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
> QML MouseArea: Binding loop detected for property "implicitHeight"
> file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9:
> QML ListView: Binding loop detected for property "topMargin"
> Cannot load libcuda.so.1
> qrc:/videoplayer/VideoPlayer.qml:172:25: QML Image: Error decoding:
> https://inv.riverside.rocks/feed/popular: Unsupported image format
> qrc:/videoplayer/VideoControls.qml:193: ReferenceError: UserPlaylistModel
> is not defined
> qrc:/videoplayer/VideoControls.qml:122: ReferenceError: UserPlaylistModel
> is not defined
> file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
> QML MouseArea: Binding loop detected for property "implicitHeight"
> file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
> QML MouseArea: Binding loop detected for property "implicitHeight"
> [ytdl_hook] ERROR: [youtube] Y0H1l3XnEr8: Unable to extract uploader id;
> please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= ,
> filling out the appropriate issue template. Confirm you are on the latest
> version using
> yt-dlp -U
> [ytdl_hook] youtube-dl failed: unexpected error occurred
> No protocol handler found to open URL ytdl://Y0H1l3XnEr8
> The protocol is either unsupported, or was disabled at compile-time.
> [ytdl_hook] ERROR: [youtube] Y0H1l3XnEr8: Unable to extract uploader id;
> please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= ,
> filling out the appropriate issue template. Confirm you are on the latest
> version using
> yt-dlp -U
> [ytdl_hook] youtube-dl failed: unexpected error occurred
>
>
>
> On Fri, 24 Feb 2023 at 15:05, Carl Schwan  wrote:
>
>> Le samedi 4 février 2023 à 7:14 PM, Devin  a écrit :
>>
>> > Hi everyone,
>> >
>> > I would like to put PlasmaTube through kdereview:
>> >
>> > https://invent.kde.org/multimedia/plasmatube
>> >
>> > PlasmaTube is a YouTube client for both mobile and desktop.
>>
>> It has already been almost 3 weeks since Devin put plasmatube in
>> kdereview.
>> Does anyone have more feedback for Plasmatube? Any last objections before
>> moving it out of kde review? :p
>>
>> Cheers,
>> Carl
>> >
>> > Thanks,
>> > Devin
>>
>

Re: Re : New repo in kdereview: PlasmaTube

[Jonathan Riddell]

When I compile this and play a video I get an error suggesting youtube-dl
isn't happy.  I'm using youtube-dl from Ubuntu which is versioned
2021.12.17-1 and looking at the
https://ytdl-org.github.io/youtube-dl/download.html site that is the latest
version


Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
qrc:/videoplayer/VideoControls.qml:243:5: QML Dialog: Binding loop detected
for property "implicitHeight"
qrc:/videoplayer/VideoControls.qml:243:5: QML Dialog: Binding loop detected
for property "implicitHeight"
qrc:/components/Sidebar.qml:9:1: QML Sidebar: Binding loop detected for
property "contentHeight"
qrc:/videoplayer/VideoControls.qml:122: ReferenceError: UserPlaylistModel
is not defined
qrc:/videoplayer/VideoControls.qml:193: ReferenceError: UserPlaylistModel
is not defined
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9:
QML ListView: Binding loop detected for property "topMargin"
Cannot load libcuda.so.1
qrc:/videoplayer/VideoPlayer.qml:172:25: QML Image: Error decoding:
https://inv.riverside.rocks/feed/popular: Unsupported image format
qrc:/videoplayer/VideoControls.qml:193: ReferenceError: UserPlaylistModel
is not defined
qrc:/videoplayer/VideoControls.qml:122: ReferenceError: UserPlaylistModel
is not defined
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "implicitHeight"
[ytdl_hook] ERROR: [youtube] Y0H1l3XnEr8: Unable to extract uploader id;
please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= ,
filling out the appropriate issue template. Confirm you are on the latest
version using
yt-dlp -U
[ytdl_hook] youtube-dl failed: unexpected error occurred
No protocol handler found to open URL ytdl://Y0H1l3XnEr8
The protocol is either unsupported, or was disabled at compile-time.
[ytdl_hook] ERROR: [youtube] Y0H1l3XnEr8: Unable to extract uploader id;
please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= ,
filling out the appropriate issue template. Confirm you are on the latest
version using
yt-dlp -U
[ytdl_hook] youtube-dl failed: unexpected error occurred



On Fri, 24 Feb 2023 at 15:05, Carl Schwan  wrote:

> Le samedi 4 février 2023 à 7:14 PM, Devin  a écrit :
>
> > Hi everyone,
> >
> > I would like to put PlasmaTube through kdereview:
> >
> > https://invent.kde.org/multimedia/plasmatube
> >
> > PlasmaTube is a YouTube client for both mobile and desktop.
>
> It has already been almost 3 weeks since Devin put plasmatube in kdereview.
> Does anyone have more feedback for Plasmatube? Any last objections before
> moving it out of kde review? :p
>
> Cheers,
> Carl
> >
> > Thanks,
> > Devin
>

kirigami2 and oxygen-icons5 in kf6

[Jonathan Riddell]

A while ago it was agreed that tars and git repos should have the same
names, which does many everyone's life easier.

https://markmail.org/message/jr4za6d7c2n7bw73#query:+page:1+mid:z67hzcbjmx5brqiv+state:results

There's one outlier which is kirigami where the tar is named kirigami2
https://invent.kde.org/frameworks/kirigami

That was to make it co-installable with kirigami 1 but nothing uses that
now so it can be dropped.  Can I suggest renaming "kirigami2" tar to be
"kirigami" again?

Another place where version numbers are used in the git/tar name is
oxygen-icons
https://invent.kde.org/frameworks/oxygen-icons5
I can't even remember why that has the 5 in it but now that Qt5 support is
dropped it seems obsolete, can I suggest renaming this to "oxygen-icons"?

Jonathan

Re: portings aids in kf6?

[Jonathan Riddell]

On Thu, 26 Jan 2023 at 17:02, Volker Krause  wrote:

>
> And add KEmoticons to that list, that's also deprecated (but not marked as
> a
> porting aid).


[:'-(

portings aids in kf6?

[Jonathan Riddell]

Can the team say which, if any, porting aids will continue in kf6?

KDELibs4Support
KDesignerPlugin
KDEWebKit
KHtml
KJS
KJsEmbed
KMediaPlayer
Kross
KXmlRpcClient

kquickcharts

[Jonathan Riddell]

*What might need doing for me to compile kquickcharts master branch?*




*https://build.neon.kde.org/job/jammy_unstable_kf6_kquickcharts_bin_amd64/25/console
15:51:32*
[ 29%] Building CXX object
src/CMakeFiles/QuickChartsStatic.dir/datasource/ModelHistorySource.cpp.o*15:51:35*
In file included from
/usr/include/c++/11/bits/stl_algobase.h:71,*15:51:35*
from /usr/include/c++/11/array:40,*15:51:35*  from
/usr/include/c++/11/tuple:39,*15:51:35*  from
/usr/include/x86_64-linux-gnu/qt6/QtCore/qtypeinfo.h:9,*15:51:35*
from
/usr/include/x86_64-linux-gnu/qt6/QtCore/qglobal.h:1397,*15:51:35*
 from
/usr/include/x86_64-linux-gnu/qt6/QtCore/qcontainertools_impl.h:14,*15:51:35*
 from
/usr/include/x86_64-linux-gnu/qt6/QtCore/qhash.h:8,*15:51:35*
from 
/usr/include/x86_64-linux-gnu/qt6/QtCore/qabstractitemmodel.h:8,*15:51:35*
 from
/usr/include/x86_64-linux-gnu/qt6/QtCore/QAbstractItemModel:1,*15:51:35*
 from
/workspace/build/src/datasource/ModelSource.h:11,*15:51:35*
  from /workspace/build/src/datasource/ModelHistorySource.h:11,*15:51:35*
 from
/workspace/build/src/datasource/ModelHistorySource.cpp:8:*15:51:35*
/usr/include/c++/11/bits/predefined_ops.h: In instantiation of
‘constexpr bool
__gnu_cxx::__ops::_Iter_less_iter::operator()(_Iterator1, _Iterator2)
const [with _Iterator1 = QList::const_iterator; _Iterator2 =
QList::const_iterator]’:*15:51:35*
/usr/include/c++/11/bits/stl_algo.h:5624:12:   required from
‘constexpr _ForwardIterator std::__min_element(_ForwardIterator,
_ForwardIterator, _Compare) [with _ForwardIterator =
QList::const_iterator; _Compare =
__gnu_cxx::__ops::_Iter_less_iter]’*15:51:35*
/usr/include/c++/11/bits/stl_algo.h:5648:43:   required from
‘constexpr _FIter std::min_element(_FIter, _FIter) [with _FIter =
QList::const_iterator]’*15:51:35*
/workspace/build/src/datasource/ModelHistorySource.cpp:53:29:
required from here*15:51:35*
/usr/include/c++/11/bits/predefined_ops.h:45:23: error: no match for
‘operator<’ (operand types are ‘const QVariant’ and ‘const
QVariant’)*15:51:35*45 |   { return *__it1 < *__it2;
}*15:51:35*   |~~~^~~~

kitemmodels kf6 build failure

[Jonathan Riddell]

Building kitemmodels I get this failure, where might it have gone?

*15:27:15* [ 86%] Building CXX object
src/qml/CMakeFiles/itemmodelsplugin.dir/plugin.cpp.o*15:27:15* In file
included from /workspace/build/src/qml/plugin.cpp:17:*15:27:15*
/workspace/build/src/qml/kconcatenaterowsproxymodel_qml.h:11:10: fatal
error: KConcatenateRowsProxyModel: No such file or directory*15:27:15*
   11 | #include *15:27:15*   |
  ^~~~

Re: Move Licentia to KDEREVIEW

[Jonathan Riddell]

Same question on this one Felipe, are you still interested in working on
the app?  It seems stuck in kdereview with no recent development.

Jonathan


On Fri, 8 Jul 2022 at 06:37, Felipe Kinoshita  wrote:

> Hey, I'd like to move Licentia  to
> KDEREVIEW.
>
> Licentia is a simple app targeted at developers/creators who need to
> decide which license is suited to their projects, Licentia helps with that
> by listing a bunch of licenses, which with it's permissions, conditions and
> limitations, instructions about how to add a license to your project and a
> list of known projects that use said license.
>
> Thanks,
> Felipe.
>

Re: Eloquens now on KDEREVIEW)

[Jonathan Riddell]

Hi Felipe, there doesn't seem to have been any movement on this for some
months, are you still interested in working on it?  If it's a useful app it
can be added to KDE gear to get releases done for example.

Jonathan


On Sat, 3 Sept 2022 at 10:40, Tomaz Canabrava  wrote:

> Hello All,
>
> All discussion was resolved by Felipe in the past few weeks,
> I Assume this is done, and should be moved out of KDE Review?
>
> Best.
>
>
> On Tue, Jun 28, 2022 at 4:54 PM Felipe Kinoshita 
> wrote:
>
>> friendly ping! :)
>>
>> On Wed, Jun 22, 2022 at 5:44 PM Felipe Kinoshita 
>> wrote:
>> >
>> > > Ah! I would suggest moving the conversion into the Controller then. As
>> > > far as kcfg, your Config object and your Settings.qml are concerned
>> > > they can be proper bools, it's only in the Controller that you have
>> > > the presentation requirement that bools must be 0/1. This saves you
>> > > the two-way conversion, in the Controller you only need to convert
>> > > bool=>int and the rest of the app can treat them as proper bools.
>> >
>> > Indeed, this makes much more sense.
>> >
>> > Fixed it now!
>> >
>> > Thanks,
>> > Felipe
>> >
>> > On Wed, Jun 22, 2022 at 10:10 AM Harald Sitter  wrote:
>> > >
>> > > On Wed, Jun 22, 2022 at 12:07 AM Felipe Kinoshita 
>> wrote:
>> > > >
>> > > > > Could you elaborate why your config.kcfg uses Ints for everything
>> when
>> > > > > you clearly want booleans (e.g. `Config.code == 1 ? true : false`)
>> > > >
>> > > > The API expects ones and zeros for its params, I chose to convert
>> them to
>> > > > booleans to make the API call easier to write and change.
>> > >
>> > > Ah! I would suggest moving the conversion into the Controller then. As
>> > > far as kcfg, your Config object and your Settings.qml are concerned
>> > > they can be proper bools, it's only in the Controller that you have
>> > > the presentation requirement that bools must be 0/1. This saves you
>> > > the two-way conversion, in the Controller you only need to convert
>> > > bool=>int and the rest of the app can treat them as proper bools.
>> > >
>> > > HS
>>
>

beware KF5 5.100 version checks

[Jonathan Riddell]

This week I got most confused by files moving around again in our
packages.  It turns out several apps have checks on ECM version for new
KDEInstallDirs that were added around ECM 5.57.  If the app uses

if(${ECM_VERSION} STRGREATER "5.57.0")

It will break with KF5 5.100

Instead it should use

if(${ECM_VERSION} VERSION_GREATER "5.57.0")

Or just depend on a newer ECM version, a few apps we've found had these
broken version checks but depended on a newer ECM version anyway so the
test can be removed.

Examples:
https://invent.kde.org/office/tellico/-/merge_requests/6/diffs
https://invent.kde.org/graphics/okular/-/merge_requests/666/diffs

Jonathan

beware KF5 5.100 version checks

[Jonathan Riddell]

This week I got most confused by files moving around again in our
packages.  It turns out several apps have checks on ECM version for new
KDEInstallDirs that were added around ECM 5.57.  If the app uses

if(${ECM_VERSION} STRGREATER "5.57.0")

It will break with KF5 5.100

Instead it should use

if(${ECM_VERSION} VERSION_GREATER "5.57.0")

Or just depend on a newer ECM version, a few apps we've found had these
broken version checks but depended on a newer ECM version anyway so the
test can be removed.

Examples:
https://invent.kde.org/office/tellico/-/merge_requests/6/diffs
https://invent.kde.org/graphics/okular/-/merge_requests/666/diffs

Jonathan

kbibtex release

[Jonathan Riddell]

KBibTex had unstable releases until 2021.  The maintainer Thomas seems to
have disappeared.  It seems stable to me on a casual use.  I wonder if
anyone is familiar enough with it to know if it can get a stable release?
The current stable release has bitrotted and distros have started shipping
the unstable release.

Jonathan

Re: Aura Browser in KDE Review

[Jonathan Riddell]

This is missing an Appstream file and the licencing isn't clear, it should
get SPDX licences.

Jonathan


On Fri, 26 Aug 2022 at 11:27, Aditya Mehra  wrote:

> Hi,
>
> Aura Browser is in KDE Review and would like to release it along with
> Plasma Bigscreen
>
> Aura browser is a web browser specifically designed to work with remote
> controls and key navigation for Plasma Bigscreen, it supports a virtual
> mouse cursor and multiple tabs it also includes a third party AdBlock from
> brave browser based on easy list.
>
> You can find the repository here:
> https://invent.kde.org/plasma-bigscreen/aura-browser
>
> Request to please review Aura Browser.
>
> Regards,
> Aditya
>

Re: New releases for bugfixes

[Jonathan Riddell]

As a distro packaging it's much easier and more reliable to just let the
new version get added automatically to our builds.  As a release manager it
shouldn't be any harder to automate making a new bugfix release.  I do this
already for Plasma when requested.  It should be the default method.

Jonathan


On Thu, 25 Aug 2022 at 17:55, Nate Graham  wrote:

> Hello everyone,
> Right now when we fix a significant bug in our software that may take a
> while to reach users to to the release schedule of its repo, we contact
> distros and ask them to backport it. This puts the burden on distros to
> react to us. I'm wondering how people feel about KDE instead making
> immediate point releases ourselves. Thus we would take responsibility
> for releasing fixes for our own regressions, and distros that monitor
> KDE infrastructure for new tarballs could be notified automatically.
>
> Thoughts?
>
> Nate
>

Re: libmediawiki release

[Jonathan Riddell]

Kipi plugins uses it, which we do still release.

Jonathan


On Thu, 25 Aug 2022 at 20:54, Albert Astals Cid  wrote:

> El dijous, 25 d’agost de 2022, a les 14:11:31 (CEST), Jonathan Riddell va
> escriure:
> > libmediawiki release no longer compiles but there's fixes in git that
> make
> > it compile.  Scarlett did the last release in 2017.  Can I make a new
> > stable release from git?
>
> Does anything use libmediawiki ? Maybe it's better to just archive it?
>
> Cheers,
>   Albert
>
> >
> > Jonathan
>
>
>
>
>

libmediawiki release

[Jonathan Riddell]

libmediawiki release no longer compiles but there's fixes in git that make
it compile.  Scarlett did the last release in 2017.  Can I make a new
stable release from git?

Jonathan

Re: Request to bump QT_MIN_VERSION to 5.15.2 for whole Plasma

[Jonathan Riddell]

I've now bumped all of Plasma to depend on Qt 5.15.2 as we had agreed that
some time ago but I seem not to have made the change.

It's not clear from your post that you really did mean Plasma though,
Plasma is only our desktop, other apps are separate and have their own
dependencies.

Jonathan


On Sun, 26 Jun 2022 at 12:53, Ömer Fadıl USTA  wrote:

> Hello everyone,
>
> Right now plasma projects' minimum depends on KF >5.90 and after KF5.86 its
> REQUIRED_QT_VERSION is 5.15.2
> thus keeping QT_MIN_VERSION as 5.15.0 is meaningless and it also causes
> problems such as in this merge :
> https://invent.kde.org/utilities/konsole/-/merge_requests/689
>
> So I am suggesting to bump all plasma project's QT_MIN_VERSION to 5.15.2
> I will be glad to get some replies and want to hear what are your opinions
> about this
>
> Thank you
> Ömer Fadıl Usta
> PGP key : 0xfd11561976b1690b
> about.me/omerusta
>

QtWebengine version

[Jonathan Riddell]

I'm building Qt 5 from the KDE branches with the new 5.15.4 rebase and
QtWebengine is up to 5.15.10, I understand this is because there are tags
in Qt Git for it.

However building, for example, messagelib I get complains about QtQuick not
being the right version

"""

*12:27:47* CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/Qt5WebEngineCore/Qt5WebEngineCoreConfig.cmake:111
(find_package):*12:27:47*   Could not find a configuration file for
package "Qt5Quick" that is*12:27:47*   compatible with requested
version "5.15.10".*12:27:47* *12:27:47*   The following configuration
files were considered but not accepted:*12:27:47* *12:27:47*
/usr/lib/x86_64-linux-gnu/cmake/Qt5Quick/Qt5QuickConfig.cmake,
version: 5.15.4*12:27:47* *12:27:47* Call Stack (most recent call
first):*12:27:47*
/usr/lib/x86_64-linux-gnu/cmake/Qt5WebEngineWidgets/Qt5WebEngineWidgetsConfig.cmake:111
(find_package)*12:27:47*
/usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake:28
(find_package)*12:27:47*   CMakeLists.txt:66 (find_package)*12:27:47*
"""

I can patch the version number in QtWebEngine to match but that feels
wrong.  What's the right solution?
https://invent.kde.org/neon/qt/qtwebengine/-/blob/Neon/release/debian/patches/0001-lower-version-to-.3-to-align-with-the-rest-of-the-pa.patch

Jonathan

Re: KDE Incubator: Telly Skout Sponsor

[Jonathan Riddell]

I've added in Plasma Mobile Gear into
https://community.kde.org/Policies/Application_Lifecycle#Releasing

Once the app has passed incubator you can ask the Plasma Mobile team to add
it into their Plasma Mobile Gear releases.

It also needs to pass kdereview which is just allowing people to review the
code and check it complies with our normal practices.  Having said that
Plasma Mobile Gear release several apps which have ignored this requirement
so it's not strongly policed.

Jonathan

Re: KDE Incubator: Telly Skout Sponsor

[Jonathan Riddell]

On Fri, 6 May 2022 at 14:41, Albert Astals Cid  wrote:

> El divendres, 6 de maig de 2022, a les 13:53:06 (CEST), Jonathan Riddell
> va escriure:
> > Hi, this app looks great.  I don't think there's a need for any formal
> > Incubation process, that's for when an app has already been part of
> another
> > development community and infrastructure and that all needs moved over.
> if
> > you've just developed this in KDE then great, stay within KDE.
>
> I think you may have not looked at the URL enough.
>
> This does needs incubation, he's just developing it in a private
> repository, but he doesn't have a KDE Developer account. Without a KDE
> Developer account we can't move this out of https://invent.kde.org/plata/
> to something like https://invent.kde.org/plasma-mobile/ or whatever would
> make sense since he'd lose commit access when the move happened.
>

Ah yes well spotted.  Plata give me a ping on Matrix any time and we'll
make an incubation page.

Jonathan

Re: KDE Incubator: Telly Skout Sponsor

[Jonathan Riddell]

Hi, this app looks great.  I don't think there's a need for any formal
Incubation process, that's for when an app has already been part of another
development community and infrastructure and that all needs moved over.  if
you've just developed this in KDE then great, stay within KDE.

I'd echo Carl's comment that I don't know what EPG means, better to spell
that out.

I had a seg fault when I ran the app for the first time after selecting
some favourite channels.

This app is heavily dependent on external data sources.  But the data
source seems to be hard coded into src/tvspielfilmfetcher.cpp and I'm not
clear what format is needed to add other sources.  It would be good to have
that well documented and some non-code format for data sources (such as
json or .desktop files etc) so anyone can propose to add one easily.  It
probably also needs some testing code to check over the data sources to
make sure they are still active, these sorts of things tend to go inactive
without warning.

When you feel the code is getting ready for release you can ask for a
review, see kdereview section here
https://community.kde.org/Policies/Application_Lifecycle

Then use releaseme to make a release and get it packaged up.  Let me know
if you need any help with that.

Jonathan




On Thu, 5 May 2022 at 11:36, Carl Schwan  wrote:

> Hi,
> An EPG is a TV guide application.
> https://en.m.wikipedia.org/wiki/Electronic_program_guide
> I agree that using 'TV guide' instead of EPG is a bit clearer :)
>
> Cheers,
> Carl
>
>
>  Original Message 
> On May 5, 2022, 00:53, Aleix Pol < aleix...@kde.org> wrote:
>
> >
> >
> > Hi Plata,
> > Would you be able to explain a bit what a "Convergent EPG" is?
> >
> > Aleix
> >
> > On Wed, Apr 27, 2022 at 11:53 PM Albert Astals Cid 
> wrote:
> > >
> > > El dilluns, 25 d’abril de 2022, a les 18:09:42 (CEST), Plata va
> escriure:
> > > > Hello,
> > >
> > > Hi.
> > >
> > > > I'm developing Telly Skout, a convergent Kirigami based EPG (
> https://invent.kde.org/plata/telly-skout).
> > > > I started developing this because I was missing an EPG to daily
> drive Plasma Mobile (coming from Android).
> > > > Currently, I'm the only committer but I hope that this might change
> now after moving to KDE Invent from GitHub.
> > > > I would love to see Telly Skout becoming part of Plasma (Mobile)
> Gear. Therefore, I'm looking for a sponsor.
> > >
> > > That's great :) We can always use more developers in KDE. Welcome!
> > > I'm not super experienced myself on Plasma Mobile, so I'd suggest you
> to drop in their Matrix channel (or mailing list) and ask there
> https://plasma-mobile.org/join/
> > > If you don't have any luck I will help you, after all the incubating
> part is relatively generic for most of the KDE parts.
> > >
> > > Cheers,
> > > Albert
> > >
> > > > Best regards
> > > > Plata
>
>

Re: Croutons in kdereview

[Jonathan Riddell]

Looks good, I've now packaged this for KDE neon unstable edition

https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/focal_unstable_neon-packaging_croutons/

Jonathan


On Sun, 29 Aug 2021 at 10:25, Janet Blackquill  wrote:

> Hello,
>
> https://invent.kde.org/libraries/croutons is in kdereview now
>
> Croutons is a library containing assorted functionality for dealing
> with asynchronous code in Qt, most notably a future type that can be
> passed into QML as a JavaScript Thennable (similarly to Qt IVI's
> PendingReply) and headers for C++20 coroutine integration for the
> Croutons Future types + some Qt types that make sense to co_await.
>
> The library is largely headers-only, sans the FutureBase, which has
> one (1) associated source file needing to be compiled into a binary.
>
> -- Janet
>

Re: kalendar desktop-mime-but-no-exec-code

[Jonathan Riddell]

Great thanks, I've packaged this now for neon's unstable edition
https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/focal_unstable_neon-packaging_kalendar/

Jonathan


On Wed, 27 Oct 2021 at 13:28, Claudio Cambra 
wrote:

> Hi Jonathan,
>
> We are now fully vendoring the required Kirigami Addons components, so
> this dependency is now eliminated.
>
> I have also pushed a commit that should fix the
> desktop-mime-but-no-exec-code error. Please let me know if you encounter
> any other issues.
>
> Thanks!
> Clau
>
> On Wed, Oct 27, 2021 at 1:51 PM Jonathan Riddell  wrote:
>
>> Packaging kalendar for neon I found an error
>>
>> desktop-mime-but-no-exec-code
>>
>> which means the .desktop file gives a mimetype but no way to launch it
>>
>> Also it depends on kirigami-addons which has not yet been released,
>> discussed at
>> https://mail.kde.org/pipermail/kde-core-devel/2021-October/091485.html
>>
>> Jonathan
>>
>

kalendar desktop-mime-but-no-exec-code

[Jonathan Riddell]

Packaging kalendar for neon I found an error

desktop-mime-but-no-exec-code

which means the .desktop file gives a mimetype but no way to launch it

Also it depends on kirigami-addons which has not yet been released,
discussed at
https://mail.kde.org/pipermail/kde-core-devel/2021-October/091485.html

Jonathan

Re: New repo in kdereview: kclock

[Jonathan Riddell]

I still don't see any attempt to get kirigami-addons through kdereview and
make a stable release (making a tag in invent isn't the same as making a
stable release).  Does anyone feel able to take enough ownership of it to
do that?  Else kclock and others will be forever stuck.

Jonathan


On Fri, 5 Mar 2021 at 02:04, hanyoung  wrote:

> Hello everyone!
> I want to move kclock to kdereview.
>
> https://invent.kde.org/plasma-mobile/kclock
>
> KClock is the alarm/clock app for Plasma Mobile. It consists of two parts,
> daemon and the client. The daemon communicates with powerdevil to register
> alarms, and provide DBus interface to interact with the client.
>
> Besides the daemon and the client, some plasmoids also included in the
> repo, although only one is enabled so far.
>
> Regards,
> Han
>

Plasma 5.24 Kickoff meeting in 4 hours

[Jonathan Riddell]

Plasma kickoff meeting at 14:00UTC/15:00BST/16:00CEST today.  I've set up
the meet room at https://meet.kde.org/b/jon-qyr-v3g

Jonathan

Frameworks 5 releases for 2022

[Jonathan Riddell]

I've created a schedule of releases for KF5 for 2022 using the
second-saturday as previously.

https://community.kde.org/Schedules/Frameworks

(I did this because it's needed for Plasma releases.)  I've added it to
phab and my google calendar.

https://calendar.google.com/calendar/u/0?cid=MDMxZ2tncWcxaGpmOGxjbWowZW0xZDJzajhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
https://phabricator.kde.org/calendar/query/KhNLCxe1xjoI/2021/11/

This is presumably all subject to changes if and when KF6 development means
it's no longer worth releasing KF5.

Jonathan

Re: New repo in kdereview: kclock

[Jonathan Riddell]

Although KClock now has a release published under stable (
https://download.kde.org/stable/plasma-mobile/21.05/) there is no stable
release of kirigami-addons and no kdereview submission.  That should be
fixed first.

Jonathan


On Thu, 13 May 2021 at 09:57, hanyoung  wrote:

> Kirigami Add-ons (a runtime dependency of kclock) now have a proper
> release. https://invent.kde.org/libraries/kirigami-addons
>
> regards,
> Han
>

Introducing Haruna

[Jonathan Riddell]

Just passed the Incubator process is Haruna, a video player.  It uses a
bunch of KDE libraries so is a natural fit to move into KDE.

https://invent.kde.org/multimedia/haruna

The project is run by George Florea Bănuș.

Jonathan

Re: [neon-notifications] Changes in repo-metadata

[Jonathan Riddell]

I noticed the below change from Laurent about ruqola describing it as a
"KDE client".  It would be much better not to pidgeon hole apps as being
"for KDE", users don't care what widget toolkit they're written in or what
desktop the app author uses, apps should work equally well on any desktop.
Even "client for" is confusing tech-speak.  I'd rather a description like
"Talk to colleagues and friends over the Rocket Chat network".

Jonathan

On Wed, 3 Mar 2021 at 18:46, Neon CI  wrote:

> commit c70e514d608c330b9871b37fb7e3369b0cea2a0d
> Author: Laurent Montel 
> Date:   Wed Mar 3 13:29:59 2021 +0100
>
> It's not a qml program now
>
> diff --git a/projects-invent/network/ruqola/metadata.yaml
> b/projects-invent/network/ruqola/metadata.yaml
> index 102acbd2..76ef5ee9 100644
> --- a/projects-invent/network/ruqola/metadata.yaml
> +++ b/projects-invent/network/ruqola/metadata.yaml
> @@ -1,4 +1,4 @@
> -description: Qt/QML client for Rocket Chat
> +description: KDE client for Rocket Chat
>  hasrepo: true
>  identifier: ruqola
>  name: Ruqola
>
>

Re: panoview Sponsor Request

[Jonathan Riddell]

Hi Samual, this looks like a fun project there.  It's not clear what you're
asking for in this e-mail.

"It's a requirement for this to be hosted using Free Software tools" it's
not clear where this requirement you say is from or why you've come to us.

While it would be possible for KDE to incubate and host the project we do
require projects to use similar technologies, so it would need to use Qt
and cmake for example.  We don't tend to host primarily command line apps
unless they are supporting our graphical tools, but I can see the panoramic
viewing might be nice additions for some of our photography and image apps
such as gwenview or digikam.

Jonathan

Re: Exiv2 project submission to the KDE community

[Jonathan Riddell]

This looks exciting, welcome along.  If you want to get the process started
we'd make an incubation page.  I can help out if you like, give me a ping
on KDE Development room on Matrix (webchat.kde.org)

https://community.kde.org/Incubator

Jonathan


On Tue, 2 Mar 2021 at 20:59, alexander.essel...@googlemail.com <
alexander.essel...@gmail.com> wrote:

> Ladies and Gentlemen:
>
> I am writing to you on behalf of the Exiv2 project https://exiv2.org.
>
> Exiv2 is a C++ library and a command-line utility to read, write, delete
> and modify Exif, IPTC, XMP and ICC image metadata. It is widely used in the
> Linux ecosystem and part of many applications such as digiKam, Gimp,
> darktable and many more.
>
> The Exiv2 project is hosted at the moment on GitHub (
> https://github.com/Exiv2/exiv2). We would like to evaluate the
> possibility of onboarding the Exiv2 project into the KDE community.
>
> The project is in good shape and the next release is scheduled to ship May
> 2021. There is a small group of people who frequently contribute to the
> project.  However the current maintainer, Robin Mills, is retiring at the
> age of 70 after 13 years of service to the project.  Robin has written a
> book about the project and discusses every aspect of both the Exiv2
> Architecture and Image Metadata Standards.
> https://clanmills.com/exiv2/book/
>
> Last Saturday (2021-02-27) there was a meeting concerning the future of
> the Exiv2 and we tried to find a new maintainer.  Regrettably because of
> the time demand imposed on the maintainer, no one volunteered.  By joining
> the KDE community we hope to address this issue and keep this important
> project alive. The meeting notes can be found on the GitHub issue (
> https://github.com/Exiv2/exiv2/issues/1466).
>
> In addition to finding a new maintainer, being part of KDE would bring
> Exiv2 into the Open Invention Network.  We are very interested in this
> aspect of KDE as it mitigates risks involved in patent discussions.
>
> Yours,
>
> Alex Esseling and Robin Mills
>

Re: Requesting my project named "media-downloader" to become part of KDE

[Jonathan Riddell]

Hi, thanks for your interest in joining KDE with your project.  We have a
process called Incubator to help being in projects created outside KDE.
https://community.kde.org/Incubator  It's just a checklist to make sure the
project uses technologies we are familiar with and communication tools we
use such as Matrix and bugzilla.

Looking at your project it would benefit from using ki18n and there's some
obvious QA issues such as what running it when youtube-dl is not installed
(the app just freezes for me).

There's no legal issues I'm aware of for youtube-dl and certainly none for
an app which happens to run as an external command.  Background info at
https://github.blog/2020-11-16-standing-up-for-developers-youtube-dl-is-back/
https://lwn.net/Articles/836830/

Do give me a ping on Matrix (jriddell) if you want to get the process
started.

Jonathan


On Fri, 5 Feb 2021 at 08:03, .. ink ..  wrote:

> Greetings from Tanzania,
>
> I have a project named "media-downloader"[1] and i would like to have
> it as part of KDE. The project is a simple GUI front end to youtube-dl
> and it can be used to download any media from any website that is
> supported by youtube-dl.
>
> Thank you.
>
> [1] https://github.com/mhogomchungu/media-downloader
>

Re: qqc2-breeze-stlye in KDE Review

[Jonathan Riddell]

No complaints so I've moved it to Plasma.  It has been included in the
Plasma 5.21 beta.

Jonathan


On Thu, 7 Jan 2021 at 09:29, Noah Davis  wrote:

> https://invent.kde.org/plasma/qqc2-breeze-style/
>
> qqc2-breeze-style is a Qt Quick Controls 2 style made with Qt Quick
> and Kirigami. It has a visual style that is meant to match the Visual
> Design Group's vision for Breeze.
>
> My motivations for making this include the following reasons.
>
> - Creating, iterating on and maintaining a Qt Quick/Kirigami based
> QQC2 style is relatively easy.
>
> - Plasma Mobile needs an efficient QQC2 style.
> - qqc2-breeze-style has better graphical performance than Plasma
> style/PC3 and qqc2-desktop-style. It doesn't depend on the speed of
> the Qt SVG renderer when rendering elements for the 1st time and most
> graphical elements are drawn with the GPU.
> - It has much better RAM usage than PC3, slightly better RAM usage
> than qqc2-desktop-style and about the same RAM usage as Material.
> After opening all pages of Kirigami Gallery, PC3 used 254MB,
> qqc2-desktop-style used 185MB, qqc2-breeze-style used 182MB and
> Material used 180MB. Take those numbers with a grain of salt since the
> absolute amount of RAM used can vary based on how much free RAM there
> is.
> - Its loading times are much better than PC3. I don't remember the
> exact number, but I'm pretty sure it took half as long to load Index
> (Maui file manager) on a PinePhone compared to PC3.
>
> - We occasionally have QQC2 style compatibility issues with 3rd party
> apps that don't force a specific QQC2 style and have been designed
> using other QQC2 styles. qqc2-breeze-style is much more compatible
> with the Default (Basic in Qt 6), Fusion and Material QQC2 styles than
> Plasma style/PC3 and qqc2-desktop-style, so 3rd party apps should be
> less likely to have issues with it. The Fusion QQC2 style will become
> the default QQC2 style on Linux in Qt 6, so I'd expect to see more
> apps designed for it in the future. Unless GNOME starts shipping an
> Adwaita QQC2 style, Fusion will probably be the QQC2 style that 3rd
> party desktop environment users see by default.
>
> - I'd like 3rd party app developers to be able to adopt the look of
> KDE apps even if they aren't part of KDE. As far as I know, there
> aren't that many open source QQC2 styles out there. The visuals of the
> Qt QQC2 styles are not terrible, but not very impressive either and
> the Material QQC2 style is not up to date with Material Design.
> qqc2-breeze-style could gain some popularity outside of KDE if it's
> easy for developers to use and proven on low power platforms like
> Plasma Mobile on the PinePhone.
>
> - Plasma style/PC3 is unfortunately limited by needing to be
> compatible with PC2 in order to not break existing Plasma themes. This
> makes it a fairly poor choice for anything but Plasmoids and anything
> else that doesn't need to be cross-platform or compatible with
> multiple QQC2 styles. Using SVGs for UI graphics has its advantages
> when you want to make something that isn't easy to make with just
> Rectangle/ShadowedRectangle. However, it seriously gets in the way for
> anything that can easily be made with just rectangles, which is most
> UI graphics in the style of Breeze. Plus, manually editing SVGs in a
> text editor to get the element IDs and CSS classes right is never fun.
>
> - qqc2-desktop-style is unfortunately limited by the fact that it gets
> most of its visuals from the system QStyle. This means there's no way
> for it to do things that would be basic in Qt Quick, such as
> animations and drawing shadows/glows/focus rings outside the bounds of
> buttons. Changing the visuals at all is harder in general due to the
> facts that the Breeze QStyle is massive and it's very easy to create
> serious issues in many apps that are hard to fix. See the struggles
> that went into making the new header area of the Breeze QStyle. In
> QML, this would have been easy.
>

Re: TotalReqall

[Jonathan Riddell]

Here is a project where the author wants to be part of our community and
has made effort to fit in with our manifesto.  We should be welcoming him
not making up arbitrary new rules that don't exist.

Jonathan

Re: Synchronized release schedule for Plasma

[Jonathan Riddell]

We discussed this in the Plasma meeting on Monday and I'm afraid there's
little appetite in moving to a 6 monthly release or a 3 monthly release.
We did used to have a 3 monthly schedule but that is too tight given the
length of beta and freezes we want to have now.  But also 6 monthly feels
too long, for distros that miss the release that become a long time that we
have users on an older release.

Having said that if there's occasions where we can shift a release a bit to
help distros we're happy to do that.

Jonathan

Re: Would distributions have an issue if KF 5.77+ would require Qt >= 5.14 (instead of >= 5.13 as of now)?

[Jonathan Riddell]

Not from KDE neon of course, we're on 5.15.  And not from the KDE snaps
build either.  But I suppose there's more than just Linux distros to
consider as we ship apps using KDE frameworks on Flatpak, Android, Windows,
even Mac to ponder too.

Jonathan


On Tue, 1 Dec 2020 at 12:14, Friedrich W. H. Kossebau 
wrote:

> Hi,
>
> last week KDE Frameworks master saw a bump in the required/expected
> minimal Qt
> version to Qt 5.13, following rules once agreed and noted here:
> https://community.kde.org/Frameworks/Policies#Frameworks_Qt_requirements
>
> I would like to challenge that former decision though and propose to
> instead
> go straight to Qt 5.14 as minimum requirement now.
>
>
> QUESTION:
> Would any of the distributions have an issue with requiring Qt 5.14
> instead of
> Qt 5.13?
>
>
> From some quick checks using https://repology.org/ it seems that any
> distribution versions which currently use Qt 5.13 have also settled on
> some
> older KF version, so will not update to just KF 5.77 and thus be screwed.
>
> Motivation:
> * KDE CI not setup ATM to cover builds with Qt 5.13 (no build, no unit
> tests)
> * Qt 5.14 added some new API, chance to miss out when using that in new
> code
> * C++: no need to write #if QT_VERSION < QT_VERSION_CHECK(5, 14, 0)
> variants
> * QML: no need to do hard-to-read generation tricks to support < Qt 5.14
> * Qt 5.13 went out-of-support in June
> * App bundle builders would rather use some recent Qt 5.14/5.15
>
> So by restraining to Qt 5.13 as minimum version IMHO we would make/keep
> life
> complicated for KF contributors without adding any value for anyone.
>
> With most of KDE Frameworks in my local checkout:
> grep "QT_VERSION_CHECK(5, 14, 0)"  frameworks/*/src -r 2>/dev/null | \
> grep "QT_VERSION " | wc -l
> gives me "92", so there are quite some code variants which need support in
> current code.
>
> From the emails at least in
> https://mail.kde.org/pipermail/kde-frameworks-devel/2020-July/112712.html
> I could not see a discussion whether Qt 5.13 makes
> sense at all now, seems mainly the algorithm was applied. I propose to
> match
> the result to known real world needs now. Or teach me what I have missed
> here
> :)
>
> Cheers
> Friedrich
>
>
>

20.12 releases

[Jonathan Riddell]

If you have an app which will be released as part of the 20.12 bundle from
the release service please list new feature on this wiki page so we can
write them up in the announcement

https://invent.kde.org/websites/kde-org/-/wikis/20.12-Releases

Tagging is due on Dec 3rd for release on Thu Dec 10th.  I'll be wanting to
write up the announce by Thu Dec 3rd.

Jonathan

Re: New to KDE OS Organisation

[Jonathan Riddell]

Welcome along!  There's no shortage of bugs that need filed and fixed and
lesser known projects that need extra help.  junior jobs will list plenty.
There's a #kde-welcome channel on matrix to say hi on too as well as the
relevant dev channels when you're working on something.  Once you get into
it it's hard to leave :)

Jonathan


On Tue, 3 Nov 2020 at 11:11, Prateek Pardeshi  wrote:

> Hello everyone,
>
> I am Prateek Pardeshi, a Junior(3rd yr) Student from SRM IST, Chennai,
> India.
>
>
> My Prev Open Source Experience:
>
> 1. *GirlScript Summer of Code 2020*- contributed to Ovuli Project.
> 2. Mentor @ *StudentCodein* (3-month open source program)
> 3. Completed *RISE Summer Program 2020* with team3 as EM (
> https://www.risesummer2020.org/team3)
>
>
> My Github: http://pp0.xyz/git
>
>
> I am looking forward to contributing and becoming a long-term contributor
> to this Organisation.
>
> Regards
> Prateek Pardeshi
>
>

Frameworks releases in 2021

[Jonathan Riddell]

The future is nearly here so I've updated the Frameworks release schedule
for 2021 based on the same first + second saturday of the month formula.

https://community.kde.org/Schedules/Frameworks
https://phabricator.kde.org/calendar/
https://calendar.google.com/calendar?cid=MDMxZ2tncWcxaGpmOGxjbWowZW0xZDJzajhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

Jonathan

Re: Supported C++ standard (aka compiler version) Overview Table for various distros?

[Jonathan Riddell]

On Wed, 14 Oct 2020 at 10:33, Milian Wolff  wrote:

> I would like to push for C++17 usage in KDevelop to make it more fun to
> develop there. This is an extragear app, so I believe we can take this
> decision separately from the surrounding KDE ecosystem.
>
> Does anyone know if there's an overview page similar to [1], but for Linux
> distributions?
>
> [1]: https://en.cppreference.com/w/cpp/compiler_support
>
> I.e. I would like to know which distro versions we would potentially lose
> by
> moving KDevelop master to C++17. I seem to recall that there existed such
> an
> overview page somewhere, but I cannot find it anymore.
>
>
I don't know of any overview.  In neon and Ubuntu LTS we seem to be using
GCC 9.3 which supports C++17 going by the reference above.

Jonathan

Releases 20.08 announce notes

[Jonathan Riddell]

If you're added new features to an app which the release service will
include in 20.08 or made a standalone release this month please add the new
feature here

https://share.kde.org/s/rSWjXQc5wPXbwtc

or go directly into the announce at
https://invent.kde.org/websites/kde-org-announcements-releases/-/blob/master/content/2020-08-apps-update/_index.md

Jonathan

xml_mimetypes5 and kcoreaddons

[Jonathan Riddell]

We're playing with translations in neon packages and looking at kcoreaddons
the tars have
xml_mimetypes5
But we can't see anything in the code which uses this.  Do these
translations get used?

Jonathan