Re: Move Koko to KDEReview

+1, I've been using Koko and find it quite pleasant. Nate On 6/9/20 5:30 AM, Carl Schwan wrote: Hi, I would like to move Koko, a convergent image viewer, to KDEReview. Koko is already shipped in the base Plasma mobile image and I was surprised that it was still in playground. The current

Re: Bridging #kde-devel on Freenode to Telegram

Yes, in general, user friendliness is a benefit that's rather important, especially when you're trying to encourage a platform to be used by more people. Nate On 6/10/20 5:14 PM, Jacky Alcine wrote: The only "benefit" here seems to be user friendliness (HTTP is ancient and C++ is but both

Re: Bridging #kde-devel on Freenode to Telegram

El mié., 10 de jun. de 2020 a la(s) 20:06, Carson Black (uhh...@gmail.com) escribió: > > Currently, #kde-devel is not set up with an IRC bridge to Telegram, > meaning users cannot access it from Telegram. > > Plugging it into our current bridge infrastructure would have the > following benefits: >

D29207: [Indexers] Ignore name-based mimetype for initial indexing decisions

bruns closed this revision. REPOSITORY R293 Baloo REVISION DETAIL https://phabricator.kde.org/D29207 To: bruns, #baloo, ngraham Cc: kde-frameworks-devel, hurikhan77, lots0logs, LeGast00n, cblack, fbampaloukas, domson, ashaposhnikov, michaelh, astippich, spoorun, ngraham, bruns, abrahams

Re: Bridging #kde-devel on Freenode to Telegram

The only "benefit" here seems to be user friendliness (HTTP is ancient and C++ is but both are still used) On Wed, Jun 10, 2020, at 16:07, Nate Graham wrote: > +1 if even only for the new contributor friendliness angle. Many other > channels are bridged to Telegram; probably this one should be

Re: Bridging #kde-devel on Freenode to Telegram

+1 if even only for the new contributor friendliness angle. Many other channels are bridged to Telegram; probably this one should be as well. Nate On 6/10/20 5:05 PM, Carson Black wrote: Currently, #kde-devel is not set up with an IRC bridge to Telegram, meaning users cannot access it from

Bridging #kde-devel on Freenode to Telegram

Currently, #kde-devel is not set up with an IRC bridge to Telegram, meaning users cannot access it from Telegram. Plugging it into our current bridge infrastructure would have the following benefits: - Telegram-only users (yes, those exist because neither IRC nor Matrix are suitable for their

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.14 - Build # 11 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.14/11/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 22:16:56 + Build duration: 32 min and counting JUnit Tests Name:

D28745: Skip caching thumbnails on encrypted filesystems

bruns added a comment. In D28745#674863 , @meven wrote: > In D28745#674827 , @bruns wrote: > > > In D28745#674711 , @meven wrote: > > > > > > > > >

D29207: [Indexers] Ignore name-based mimetype for initial indexing decisions

ngraham accepted this revision. ngraham added a comment. This revision is now accepted and ready to land. Shipit! REPOSITORY R293 Baloo BRANCH submit REVISION DETAIL https://phabricator.kde.org/D29207 To: bruns, #baloo, ngraham Cc: kde-frameworks-devel, hurikhan77, lots0logs,

Re: Opening files by mimetype instead of by file extension

El dimecres, 10 de juny de 2020, a les 11:52:03 CEST, David Faure va escriure: > On mercredi 10 juin 2020 00:52:16 CEST Albert Astals Cid wrote: > > As far as I can see QFileDialog only supports listing by file extension. > > > > On the other hand it seems in GTK+ land you can get an open file

Re: Who merges Merge Requests, and when?

El dimecres, 10 de juny de 2020, a les 18:19:36 CEST, Glen Ditchfield va escriure: > In the Phabricator work flow, I would submit a patch, someone knowledgeable > would accept it, and I would `arc land` it. Clear and simple. > > GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.14 - Build # 10 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.14/10/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 21:44:55 + Build duration: 31 min and counting JUnit Tests Name:

D29207: [Indexers] Ignore name-based mimetype for initial indexing decisions

bruns edited the summary of this revision. REPOSITORY R293 Baloo REVISION DETAIL https://phabricator.kde.org/D29207 To: bruns, #baloo, ngraham Cc: kde-frameworks-devel, hurikhan77, lots0logs, LeGast00n, cblack, fbampaloukas, domson, ashaposhnikov, michaelh, astippich, spoorun, ngraham,

Re: Who merges Merge Requests, and when?

On Wednesday, June 10, 2020 12:19:36 PM EDT Glen Ditchfield wrote: > In the Phabricator work flow, I would submit a patch, someone knowledgeable > would accept it, and I would `arc land` it. Clear and simple. > > GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's Infrastructure/ >

Who merges Merge Requests, and when?

In the Phabricator work flow, I would submit a patch, someone knowledgeable would accept it, and I would `arc land` it. Clear and simple. GitLab doesn't have that "accept" step AFAIK. The KDE Wiki's Infrastructure/ GitLab page says "Once the Merge Request is accepted, KDE Developers will

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.14 - Build # 9 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.14/9/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 15:17:13 + Build duration: 31 min and counting JUnit Tests Name:

KDE CI: Frameworks » kdeclarative » kf5-qt5 FreeBSDQt5.14 - Build # 22 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdeclarative/job/kf5-qt5%20FreeBSDQt5.14/22/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 15:31:23 + Build duration: 7 min 55 sec and counting JUnit Tests Name:

KDE CI: Frameworks » krunner » kf5-qt5 FreeBSDQt5.14 - Build # 27 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/krunner/job/kf5-qt5%20FreeBSDQt5.14/27/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 11:52:42 + Build duration: 1 min 0 sec and counting JUnit Tests Name:

KDE CI: Frameworks » kcrash » kf5-qt5 FreeBSDQt5.14 - Build # 19 - Still Failing!

BUILD FAILURE Build URL https://build.kde.org/job/Frameworks/job/kcrash/job/kf5-qt5%20FreeBSDQt5.14/19/ Project: kf5-qt5 FreeBSDQt5.14 Date of build: Wed, 10 Jun 2020 09:54:41 + Build duration: 1 min 18 sec and counting CONSOLE OUTPUT

Re: Opening files by mimetype instead of by file extension

On mercredi 10 juin 2020 00:52:16 CEST Albert Astals Cid wrote: > As far as I can see QFileDialog only supports listing by file extension. > > On the other hand it seems in GTK+ land you can get an open file dialog > listing by mimetype, so I've got one bug about "you're worse than XXX > because

D29810: Don't use the setenv function after fork

bcooksley added a comment. NOTICE OF INTENTION TO REVERT Due to this commit introducing a FBTFS on FreeBSD, this commit will be automatically reverted in 24 hours unless https://invent.kde.org/frameworks/kcrash/-/merge_requests/3 has been merged and the FTBFS condition corrected.

Re: Re: Add loop device interface to Solid framework

Hi, Thank you for your reply. I will definitely test your library as it seems to have everything ones need to interface with udisks. Best regards, Kwon-Young Choi > Message: 1 > Date: Tue, 9 Jun 2020 12:08:18 -0300 > From: Daniel Nicoletti > To: kde-devel@kde.org > Subject: Re: Add loop

Move Koko to KDEReview

Hi, I would like to move Koko, a convergent image viewer, to KDEReview. Koko is already shipped in the base Plasma mobile image and I was surprised that it was still in playground. The current devs are mostly Nicolas, Marco and me. Koko is following the KDE HIG and is build using QtQuick and the