Re: Dropping Qt5 CI Support at the End of September 2025

On Mon, Jun 23, 2025 at 10:31 AM Albert Astals Cid wrote: > Hi everyone, > > While this has been discussed in various forums, it has not yet been the > main > focus of any conversation. > > We are planning to drop support for Qt5 CI on invent.kde.org at the end > of > September 2025. > > If you a

Re: KDE Gear projects with failing CI (master) (17 June 2025)

On Thu, Jun 19, 2025 at 3:12 PM Justin Zobel wrote: > On 18/06/2025 18:13, Ben Cooksley wrote: > > On Wed, Jun 18, 2025 at 7:01 PM Justin Zobel wrote: > >> On 18/06/2025 07:31, Albert Astals Cid wrote: >> >> Please work on fixing them, otherwise i will remove the failing CI jobs on >> their 4th

Re: KDE Gear projects with failing CI (master) (17 June 2025)

On 18/06/2025 18:13, Ben Cooksley wrote: On Wed, Jun 18, 2025 at 7:01 PM Justin Zobel wrote: On 18/06/2025 07:31, Albert Astals Cid wrote: Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for

Re: KDE Gear projects with failing CI (master) (17 June 2025)

El dimecres, 18 de juny del 2025, a les 0:01:49 (Hora d’estiu d’Europa central), Albert Astals Cid va escriure: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Good news: 1 r

Re: KDE Gear projects with failing CI (master) (17 June 2025)

On Wed, Jun 18, 2025 at 7:01 PM Justin Zobel wrote: > On 18/06/2025 07:31, Albert Astals Cid wrote: > > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Good news: 1 repo fixed

Re: KDE Gear projects with failing CI (master) (17 June 2025)

On 18/06/2025 07:31, Albert Astals Cid wrote: Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Good news: 1 repo fixed Bad news: 1 repo still failing, 1 new repo failing cantor - 3rd

Re: Upcoming CI changes - transition to VM based CI

On Thu, Jun 12, 2025 at 12:22 AM Luigi Toscano wrote: > Ben Cooksley ha scritto: > > On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid > > wrote: > > > > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > > central), Ben Cooksley va escriure: >

Re: Upcoming CI changes - transition to VM based CI

Ben Cooksley ha scritto: > On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid > wrote: > > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > > > My concern is that if we keep pushing out terminating sup

Re: Upcoming CI changes - transition to VM based CI

On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid wrote: > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > > > My concern is that if we keep pushing out terminating support those > > > > projects will just keep deferring their portin

Re: Upcoming CI changes - transition to VM based CI

El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > > > My concern is that if we keep pushing out terminating support those > > > projects will just keep deferring their porting. > > > Note that Frameworks 6 released in Feb 2024, so they've h

Re: Building API documentation for frameworks

Am 06.06.25 um 17:31 schrieb Aurélien COUDERC: Hi Le 6 juin 2025 16:51:48 GMT+02:00, Nicolas Fella a écrit  : Hi, The end result is still qch files, but the build process changes a bit. It now works as followed: 1. Download https://invent.kde.org/sdk/kde-qdoc-common With my Debian packager h

Re: kio-fuse and Qt6/KF6 - Was: Re: Upcoming CI changes - transition to VM based CI

On Dienstag, 10. Juni 2025 09:28:45 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > On Mon, Jun 9, 2025 at 8:55 PM Stefan Brüns > > wrote: > > On Dienstag, 3. Juni 2025 17:38:54 Mitteleuropäische Sommerzeit Volker > > Krause > > > > wrote: > > > On Montag, 2. Juni 2025 16:42:01 Mitteleuropäi

Re: Upcoming CI changes - transition to VM based CI

On Mon, Jun 9, 2025 at 8:10 PM Albert Astals Cid wrote: > El dimecres, 4 de juny del 2025, a les 14:27:35 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > On Wed, Jun 4, 2025 at 8:17 AM Albert Astals Cid wrote: > > > El dimarts, 3 de juny del 2025, a les 11:42:08 (Hora d’estiu d’

Re: kio-fuse and Qt6/KF6 - Was: Re: Upcoming CI changes - transition to VM based CI

On Mon, Jun 9, 2025 at 8:55 PM Stefan Brüns wrote: > On Dienstag, 3. Juni 2025 17:38:54 Mitteleuropäische Sommerzeit Volker > Krause > wrote: > > On Montag, 2. Juni 2025 16:42:01 Mitteleuropäische Sommerzeit Christoph > > > > Cullmann wrote: > > > Have we some overview how many things on invent.k

kio-fuse and Qt6/KF6 - Was: Re: Upcoming CI changes - transition to VM based CI

On Dienstag, 3. Juni 2025 17:38:54 Mitteleuropäische Sommerzeit Volker Krause wrote: > On Montag, 2. Juni 2025 16:42:01 Mitteleuropäische Sommerzeit Christoph > > Cullmann wrote: > > Have we some overview how many things on invent.kde.org will loose the the > > CI as they are still Qt 5 only? >

Re: Upcoming CI changes - transition to VM based CI

El dimecres, 4 de juny del 2025, a les 14:27:35 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > On Wed, Jun 4, 2025 at 8:17 AM Albert Astals Cid wrote: > > El dimarts, 3 de juny del 2025, a les 11:42:08 (Hora d’estiu d’Europa > > > > central), Ben Cooksley va escriure: > > > On Tue,

Re: KDE Gear projects with failing CI (master) (4 June 2025)

On 08/06/25 11:48, Christophe Marin wrote: On dimanche 8 juin 2025 11:25:07 heure d’été d’Europe centrale Alexander Semke wrote: On 04/06/25 20:53, Albert Astals Cid wrote: [...] cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/963838 * testmaxima fails This is a

Re: KDE Gear projects with failing CI (master) (4 June 2025)

On Sun, Jun 8, 2025 at 9:48 PM Christophe Marin wrote: > On dimanche 8 juin 2025 11:25:07 heure d’été d’Europe centrale Alexander > Semke > wrote: > > On 04/06/25 20:53, Albert Astals Cid wrote: > > > [...] > > > > > > cantor - NEW > > > > > > * https://invent.kde.org/education/cantor/-/pipelin

Re: KDE Gear projects with failing CI (master) (4 June 2025)

On dimanche 8 juin 2025 11:25:07 heure d’été d’Europe centrale Alexander Semke wrote: > On 04/06/25 20:53, Albert Astals Cid wrote: > > [...] > > > > cantor - NEW > > > > * https://invent.kde.org/education/cantor/-/pipelines/963838 > > > >* testmaxima fails > > This is again a problem

Re: KDE Gear projects with failing CI (master) (4 June 2025)

On 04/06/25 20:53, Albert Astals Cid wrote: [...] cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/963838 * testmaxima fails This is again a problem with the Maxima package in Tumbleweed, we had it already a couple of weeks ago: |"Error: fatal error encountered in

Re: Building API documentation for frameworks

Hi Anna, you may want to only split out the index files into the -devel packages and you're good to go. I did that with fedora packages when adding the -doc packages, so those don't have to be added to the builds themselves, you just require the .index files like Nicolas wrote. Kind regards,

Re: Building API documentation for frameworks

Hi Le 6 juin 2025 16:51:48 GMT+02:00, Nicolas Fella a écrit  : >Hi, >The end result is still qch files, but the build process changes a bit. It now >works as followed: >1. Download https://invent.kde.org/sdk/kde-qdoc-common With my Debian packager hat on : we don't allow network access during

Re: Building API documentation for frameworks

On Jun 6, 2025, at 09:51, Nicolas Fella wrote: > > To make sure that cross-linking between modules works you want the .index > files of the module's dependencies available during the generate phase. This is quite inconvenient as -doc packages now become build-time dependencies in addition to -

Re: Building API documentation for frameworks

Hello, On vendredi 6 juin 2025 16:51:48 heure d’été d’Europe centrale Nicolas Fella wrote: > 4. Build the 'prepare_docs' Make target > > 5. Build the 'generate_docs' Make target > > 6. Build the 'install_html_docs' Make target to install the generated > HTML files > > 7. Build the 'generate_

Re: KDE Gear projects with failing CI (master) (4 June 2025)

On Mittwoch, 4. Juni 2025 20:53:57 Mitteleuropäische Sommerzeit Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Can some akonadi person have a look a

Re: KDE Gear projects with failing CI (master) (4 June 2025)

El dimecres, 4 de juny del 2025, a les 20:53:57 (Hora d’estiu d’Europa central), Albert Astals Cid va escriure: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Can some akona

Re: Upcoming CI changes - transition to VM based CI

On Wed, Jun 4, 2025 at 8:17 AM Albert Astals Cid wrote: > El dimarts, 3 de juny del 2025, a les 11:42:08 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > On Tue, Jun 3, 2025 at 9:03 AM Albert Astals Cid wrote: > > > El dilluns, 2 de juny del 2025, a les 13:39:21 (Hora d’estiu d’E

Re: Upcoming CI changes - transition to VM based CI

On Tuesday, 3 June 2025 11:42:08 CEST Ben Cooksley wrote: > For FreeBSD the story is much the same as SUSE - packages are being removed > as apps upgrade to Qt 6 and the Qt 5 version of libraries becomes surplus > to requirements. >From the FreeBSD packaging side, we have zero interest in Qt5 for

Re: Upcoming CI changes - transition to VM based CI

El dimarts, 3 de juny del 2025, a les 11:42:08 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > On Tue, Jun 3, 2025 at 9:03 AM Albert Astals Cid wrote: > > El dilluns, 2 de juny del 2025, a les 13:39:21 (Hora d’estiu d’Europa > > > > central), Ben Cooksley va escriure: > > > Hi all,

Re: Upcoming CI changes - transition to VM based CI

Am 03.06.25 um 11:42 schrieb Ben Cooksley: On Tue, Jun 3, 2025 at 9:03 AM Albert Astals Cid wrote: El dilluns, 2 de juny del 2025, a les 13:39:21 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > Hi all, > > For some time now we have had a variety of issues with o

Re: Upcoming CI changes - transition to VM based CI

On Montag, 2. Juni 2025 16:42:01 Mitteleuropäische Sommerzeit Christoph Cullmann wrote: > Have we some overview how many things on invent.kde.org will loose the the > CI as they are still Qt 5 only? Looking at things that still have Qt5 jobs in the CI, it's a pretty mixed bag: * Plugins needed to

Re: Upcoming CI changes - transition to VM based CI

On Dienstag, 3. Juni 2025 11:30:51 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > On Tue, Jun 3, 2025 at 11:04 AM Lukas Sommer wrote: > > I have a question. Currently we have a static Windows Qt5 build, but we > > don't have a static windows Qt6 build, right? So when removing Qt5, there > > w

Re: Upcoming CI changes - transition to VM based CI

On Tue, Jun 3, 2025 at 9:03 AM Albert Astals Cid wrote: > El dilluns, 2 de juny del 2025, a les 13:39:21 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > Hi all, > > > > For some time now we have had a variety of issues with our Docker/Podman > > based CI builds. These have includ

Re: Upcoming CI changes - transition to VM based CI

On Tue, Jun 3, 2025 at 11:04 AM Lukas Sommer wrote: > Hi. > Hi Lukas, > > I have a question. Currently we have a static Windows Qt5 build, but we > don't have a static windows Qt6 build, right? So when removing Qt5, there > won't be any static windows build at all anymore? > Unless someone do

Re: Upcoming CI changes - transition to VM based CI

Hi. I have a question. Currently we have a static Windows Qt5 build, but we don't have a static windows Qt6 build, right? So when removing Qt5, there won't be any static windows build at all anymore? Best regards Lukas Am 2. Juni 2025 11:39:21 GMT+00:00 schrieb Ben Cooksley : >Hi all, > >For

Re: Licensing Policy: other build files should follow cmake rule

El dilluns, 2 de juny del 2025, a les 12:39:49 (Hora d’estiu d’Europa central), Harald Sitter va escriure: > Ahoy ahoy > > I am proposing that we clarify the licensing policy a bit by adding a > > new point following cmake: > > #. Build-related files (build scripts, makefiles, build systems othe

Re: Upcoming CI changes - transition to VM based CI

El dilluns, 2 de juny del 2025, a les 16:42:01 (Hora d’estiu d’Europa central), Christoph Cullmann va escriure: > Hi, > > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > > Hi all, > > For some time now we have had a variety of issues with our Docker/Podman > > based CI builds. These ha

Re: Upcoming CI changes - transition to VM based CI

El dilluns, 2 de juny del 2025, a les 13:39:21 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > Hi all, > > For some time now we have had a variety of issues with our Docker/Podman > based CI builds. These have included the lack of GUI test support on > Windows, periodic crashes on Fr

Re: Upcoming CI changes - transition to VM based CI

Am Montag, 2. Juni 2025, 16:42:01 Mitteleuropäische Sommerzeit schrieb Christoph Cullmann: > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > > We will therefore have to remove Qt 5 support from the CI system with the > > transition to VM based CI. > > > > > > Please let me know if th

Re: Upcoming CI changes - transition to VM based CI

On Tue, Jun 3, 2025 at 3:54 AM Thomas Baumgart wrote: > On Montag, 2. Juni 2025 17:06:15 CEST Benson Muite wrote: > > > > > On Mon, Jun 2, 2025, at 5:42 PM, Christoph Cullmann wrote: > > > Hi, > > > > > > > > > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley > wrote: > > > > > >> Hi all, > > >>

invent.k.o/games (Re: Upcoming CI changes - transition to VM based CI)

Am Montag, 2. Juni 2025, 17:06:15 Mitteleuropäische Sommerzeit schrieb Benson Muite: > Can also help with some of the Games software. I can speed you (and others) up with looking at the games (at least those in invent.kde.org/games): There is one unreleased which needs related work: Kolorfill,

Re: Upcoming CI changes - transition to VM based CI

On Montag, 2. Juni 2025 17:06:15 CEST Benson Muite wrote: > > On Mon, Jun 2, 2025, at 5:42 PM, Christoph Cullmann wrote: > > Hi, > > > > > > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > > > >> Hi all, > >> For some time now we have had a variety of issues with our Docker/Podman > >

Re: Upcoming CI changes - transition to VM based CI

On Mon, Jun 2, 2025, at 5:42 PM, Christoph Cullmann wrote: > Hi, > > > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > >> Hi all, >> For some time now we have had a variety of issues with our Docker/Podman >> based CI builds. These have included the lack of GUI test support on >> Wi

Re: Upcoming CI changes - transition to VM based CI

Hi, On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > Hi all, > For some time now we have had a variety of issues with our Docker/Podman > based CI builds. These have included the lack of GUI test support on Windows, > periodic crashes on FreeBSD, poor IO performance of Windows builds

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

El diumenge, 1 de juny del 2025, a les 13:17:29 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > On Sun, Jun 1, 2025 at 4:42 PM Azhar Momin wrote: > > On 6/1/25 1:14 AM, Ben Cooksley wrote: > > > > On Sun, Jun 1, 2025 at 7:42 AM Albert Astals Cid wrote: > >> El divendres, 30 de maig

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Sun, Jun 1, 2025 at 4:42 PM Azhar Momin wrote: > > On 6/1/25 1:14 AM, Ben Cooksley wrote: > > On Sun, Jun 1, 2025 at 7:42 AM Albert Astals Cid wrote: > >> El divendres, 30 de maig del 2025, a les 13:42:29 (Hora d’estiu d’Europa >> central), Neal Gompa va escriure: >> > On Fri, May 30, 2025 at

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On 6/1/25 1:14 AM, Ben Cooksley wrote: On Sun, Jun 1, 2025 at 7:42 AM Albert Astals Cid wrote: El divendres, 30 de maig del 2025, a les 13:42:29 (Hora d’estiu d’Europa central), Neal Gompa va escriure: > On Fri, May 30, 2025 at 7:36 AM Albert Astals Cid wrote: > > El d

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Sun, Jun 1, 2025 at 7:42 AM Albert Astals Cid wrote: > El divendres, 30 de maig del 2025, a les 13:42:29 (Hora d’estiu d’Europa > central), Neal Gompa va escriure: > > On Fri, May 30, 2025 at 7:36 AM Albert Astals Cid wrote: > > > El divendres, 30 de maig del 2025, a les 13:02:48 (Hora d’esti

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

El divendres, 30 de maig del 2025, a les 13:42:29 (Hora d’estiu d’Europa central), Neal Gompa va escriure: > On Fri, May 30, 2025 at 7:36 AM Albert Astals Cid wrote: > > El divendres, 30 de maig del 2025, a les 13:02:48 (Hora d’estiu d’Europa > > > > central), Neal Gompa va escriure: > > > On Fr

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025 at 10:52 PM Neal Gompa wrote: > On Fri, May 30, 2025 at 5:54 AM Albert Astals Cid wrote: > > > > We are trying to move most of the oss-fuzz related files to our reops > instead > > of being in https://github.com/google/oss-fuzz/ > > > > This will allow us to not have to depe

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025 at 10:40 PM Carl Schwan wrote: > On Fri, May 30, 2025, at 11:53 AM, Albert Astals Cid wrote: > > We are trying to move most of the oss-fuzz related files to our reops > instead > > of being in https://github.com/google/oss-fuzz/ > > > > This will allow us to not have to depen

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025 at 6:59 AM Albert Astals Cid wrote: > > El divendres, 30 de maig del 2025, a les 12:51:08 (Hora d’estiu d’Europa > central), Neal Gompa va escriure: > > On Fri, May 30, 2025 at 5:54 AM Albert Astals Cid wrote: > > > We are trying to move most of the oss-fuzz related files to

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Freitag, 30. Mai 2025 13:42:29 Mitteleuropäische Sommerzeit Neal Gompa wrote: > The fuzzer code files basically force the project to be LGPLv3+ > licensed as distributed since the combined work of LGPL-2.1-or-later + > Apache-2.0 means LGPL-3.0-or-later. Huh? Which combined work? The KArchive

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025 at 5:54 AM Albert Astals Cid wrote: > > We are trying to move most of the oss-fuzz related files to our reops instead > of being in https://github.com/google/oss-fuzz/ > > This will allow us to not have to depend on other people to merge changes in > them which sometimes creat

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

El divendres, 30 de maig del 2025, a les 12:51:08 (Hora d’estiu d’Europa central), Neal Gompa va escriure: > On Fri, May 30, 2025 at 5:54 AM Albert Astals Cid wrote: > > We are trying to move most of the oss-fuzz related files to our reops > > instead of being in https://github.com/google/oss-fuz

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025 at 7:36 AM Albert Astals Cid wrote: > > El divendres, 30 de maig del 2025, a les 13:02:48 (Hora d’estiu d’Europa > central), Neal Gompa va escriure: > > On Fri, May 30, 2025 at 6:59 AM Albert Astals Cid wrote: > > > El divendres, 30 de maig del 2025, a les 12:51:08 (Hora d’es

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

El divendres, 30 de maig del 2025, a les 13:02:48 (Hora d’estiu d’Europa central), Neal Gompa va escriure: > On Fri, May 30, 2025 at 6:59 AM Albert Astals Cid wrote: > > El divendres, 30 de maig del 2025, a les 12:51:08 (Hora d’estiu d’Europa > > > > central), Neal Gompa va escriure: > > > On Fr

Re: Licensing Policy: Accepting Apache 2 for oss-fuzz related files

On Fri, May 30, 2025, at 11:53 AM, Albert Astals Cid wrote: > We are trying to move most of the oss-fuzz related files to our reops instead > of being in https://github.com/google/oss-fuzz/ > > This will allow us to not have to depend on other people to merge changes in > them which sometimes cre

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 16/05/25 02:22, Justin Zobel wrote: [...] Using a mobile phone cannot be compared to the power used by data centres to train AI in the slightest. Just straight off the top of my head, your phone and computer automatically go to sleep by default. Servers do not. It's also a matter of h

Re: Coding assistants for KDE

On 25/05/25 17:47, Christoph Cullmann wrote: [...] given I played already a bit longer with local running AI stuff via ollama, I tried to use the REST API https://github.com/ollama/ollama/blob/main/docs/api.md for a small Kate plugin skeleton: https://invent.kde.org/utilities/kate/-/merge_r

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 26/05/25 20:52, Christoph Cullmann wrote: Hi, https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/698 would still benefit from some input on how to proceed in this very concrete case. I see it pragmatically - it just another "tool" that helps you to generate/auto-comp

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

gt; > > > > > > > > > Greetings > > > > Christoph > > > > > > If the contributor cannot tell you the license(s) of the code that was > > > used to generate the code, then it's literally gambling that this code > &g

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

> used in a way that violates the license and opens up the KDE e.V. to > > litigation. > > > > This is an absolutely possible scenario if the author happens to look > > around for their code being re-used. KDE e.V. CAN NOT accept AI > > contributions because the s

Re: Disallow or discourage use of "AI" tools

On 12 May 2025 15.53.02 EEST, Akseli wrote: >Hi > >There's been a lot of "AI" slop spam to various KDE projects, bug reports, >forums, etc.. > >We should take a more public stance on disallowing all this slop. Lengthy >gitlab issues that are just full of nonsense generated by a bot just take tim

Re: Performance improvement

On Thursday, 22 May 2025 22:58:37 Central Daylight Time Igor Mironchik wrote: > PASS : Test::initTestCase() > PASS : Test::test_func() > RESULT : Test::test_func(): > 0.35 msecs per iteration (total: 75, iterations: 2097152) > PASS : Test::test_template() > RESULT : Test::test_templ

Re: Performance improvement

On Thursday, 22 May 2025 11:21:03 Central Daylight Time Igor Mironchik wrote: > inline long long int > skipSpaces(long long int i, const QString &line) > { > return skipIf(i, line, [](const QChar &ch){ return ch.isSpace(); }); > } > > Do you know a way to optimize it? In addition to what oth

Re: Coding assistants for KDE

Hi, On Monday, May 19th, 2025 at 02:37, Justin Zobel wrote: > On 19/05/2025 06:05, Ingo Klöcker wrote: > > > On Sonntag, 18. Mai 2025 21:32:20 Mitteleuropäische Sommerzeit Ingo Klöcker > > wrote: > > > > > Yes, there is the theoretical threat that an AI learned code that's under > > > a >

AW: Plasma Marble Globe wallpaper (was: Re: My first task)

. Best Regards, Torsten -Original-Nachricht- Betreff: Plasma Marble Globe wallpaper (was: Re: My first task) Datum: 2025-05-23T11:38:27+0200 Von: "Friedrich W. H. Kossebau" An: "Piotr Frankowski" Hi Piotr, Am Freitag, 23. Mai 2025, 10:02:54 Mitteleuropäische Sommerze

Re: My first task

Hello Carl, I'm not sure about visual effect of code which you mentioned. But it looks better in code organization. My additional work was to implement "follow the sun" functionality, i.e. rotate earth according to current sun position (it was present in KDE4 long time ago). When I will have oppor

Re: My first task

Hi, I'm not sure I follow exactly what you are trying to do but the following code works with Plasma 6: https://invent.kde.org/education/marble/-/blob/master/src/plasma/wallpapers/worldmap/contents/ui/main.qml?ref_type=heads Cheers, Carl On Fri, May 23, 2025, at 10:02 AM, Piotr Frankowski wrot

Plasma Marble Globe wallpaper (was: Re: My first task)

Hi Piotr, Am Freitag, 23. Mai 2025, 10:02:54 Mitteleuropäische Sommerzeit schrieb Piotr Frankowski: > Hello, > Long time has passed, I have found some free time, and with little help of > LLM I have managed to reproduce your work, modify the script(?), and it > works. I have enabled stars, but I

Re: Performance improvement

Igor Mironchik 于2025年5月23日周五 00:21写道： > > Hi. > > I'd like to ask you, guys, maybe I'm a dumb a little, and you know how > to optimize a following function. > > inline long long int > skipIf(long long int startPos, const QString &line, > const std::function &pred, > long long int e

Re: Performance improvement

On Thu, 2025-05-22 at 19:21 +0300, Igor Mironchik wrote: > Hi. > > I'd like to ask you, guys, maybe I'm a dumb a little, and you know > how > to optimize a following function. > > inline long long int > skipIf(long long int startPos, const QString &line, >     const std::function &pred, >   

Re: Performance improvement

On 2025-05-22, Igor Mironchik wrote: > Hi. > > I'd like to ask you, guys, maybe I'm a dumb a little, and you know how > to optimize a following function. I don't understand the requirements. Can you provide 10 sets of input/output ? /Sune

Re: KDE Gear projects with failing CI (release/25.04) (20 May 2025)

On Mittwoch, 21. Mai 2025 00:39:22 Mitteleuropäische Sommerzeit Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > VERY BAD NEWS: neochat suse_tumblewee

Re: KDE Gear projects with failing CI (master) (20 May 2025)

On Wed, May 21, 2025 at 8:13 AM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for > multiple > reasons. > > Bad news: 2 new repos failing > > Good news: 1 repo fixed > > krfb

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Sorry for swooping in this conversation as a regular contributor. >> From my understanding (what others have told me), AI generally does not >> produce good quality code though. So how is that a benefit to society? > > Well, in that case, those “others” are using them wrong or are just spreading

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 19:15, Ilya Bizyaev wrote: On Monday, May 19th, 2025 at 02:34, Justin Zobel wrote: On 18/05/2025 16:41, Albert Vaca Cintora wrote: On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: If the contributor cannot tell you the license(s) of the code that was used to generate t

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Montag, 19. Mai 2025 07:48:42 Mitteleuropäische Sommerzeit Justin Zobel wrote: > On 19/05/2025 15:01, Konstantin Kharlamov wrote: > > Another example is I had to rewrite some project from one language to > > another at work. This is tedious task, so I similarly used AI to > > create a scratch,

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Monday, May 19, 2025 02:51:37 AM Martin Steigerwald wrote: > Ingo's suggestions to train a model with KDE code might help. But of > course to train a model will need a huge lot of resources according to > what I know. From the peanut gallery: I know very little about training an AI, but, from

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Mon, May 19, 2025, at 11:45, Ilya Bizyaev wrote: > If you really care about the licensing aspect, focus on it instead of > diverting this thread into other topics with statements like this one. I strongly agree with this statement. "AI" as a term is a nothing-burger, it needs to be broken dow

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Monday, May 19th, 2025 at 02:34, Justin Zobel wrote: > On 18/05/2025 16:41, Albert Vaca Cintora wrote: > > > On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: > > > > > If the contributor cannot tell you the license(s) of the code that was > > > used to generate the code, then it's lite

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Akseli Lahtinen 于2025年5月19日周一 16:14写道： > My original point is to try to get rid of the low-hanging fruit, as in > people who spam bug reports with obviously "AI" generated things. I'm basically with you. That's why I began my first reply with "I assume this doesn't include...", i.e. just a casual

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 15:28, Jin Liu wrote: Justin Zobel 于2025年5月19日周一 13:52写道： I understand that it makes everything easier. That doesn't matter in the slightest when you cannot verify the original license of the code allows you to use said code or that the license is compatible with KDE. I don't th

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Monday 19 May 2025 10:26:19 Eastern European Summer Time Jin Liu wrote: > Martin Steigerwald 于2025年5月19日周一 14:56写道： > > > Everyone: I suggest to assume good intentions. > > My suggestion is to avoid making assessments on "people", and focus on > code or legal or other aspects. > > - Jin Liu

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Martin Steigerwald 于2025年5月19日周一 14:56写道： > Everyone: I suggest to assume good intentions. My suggestion is to avoid making assessments on "people", and focus on code or legal or other aspects. - Jin Liu

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Sunday, 18 May 2025 09:11:35 Central European Summer Time Albert Vaca Cintora wrote: > On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: > > If the contributor cannot tell you the license(s) of the code that was > > used to generate the code, then it's literally gambling that this code > > wasn'

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Hi. Jin Liu - 19.05.25, 07:58:50 CEST: > > It's clear a lot of people don't care about theft or the environment > > and are happy to use AI without thinking about the true impact. > > Insult taken. Is that KDE's official stance that because I use AI in > coding, so "I don't care about theft or the

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Mon, 2025-05-19 at 15:18 +0930, Justin Zobel wrote: > > > > > On 19/05/2025 15:01, Konstantin Kharlamov wrote: > > > > > On Mon, 2025-05-19 at 14:53 +0930, Justin Zobel wrote: > > > > > > > > > > > > > > On 19/05/2025 14:35, Konstantin Kharlamov wrote: > > > > > > > > > >

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Hi. Justin Zobel - 19.05.25, 07:52:05 CEST: > I understand that it makes everything easier. That doesn't matter in the > slightest when you cannot verify the original license of the code > allows you to use said code or that the license is compatible with KDE. > > What this all boils down to, is

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Justin Zobel 于2025年5月19日周一 13:52写道： > I understand that it makes everything easier. That doesn't matter in the > slightest when you cannot verify the original license of the code allows you > to use said code or that the license is compatible with KDE. I don't think a few (<10) lines of code ar

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 15:10, Jin Liu wrote: Justin Zobel 于2025年5月19日周一 08:34写道： From my understanding (what others have told me), AI generally does not produce good quality code though. So how is that a benefit to society? From my personal experience (what I, not others, have personally used Github

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 15:01, Konstantin Kharlamov wrote: On Mon, 2025-05-19 at 14:53 +0930, Justin Zobel wrote: On 19/05/2025 14:35, Konstantin Kharlamov wrote: On Mon, 2025-05-19 at 10:03 +0930, Justin Zobel wrote: On 18/05/2025 16:41, Albert Vaca Cintora wrote: On Sun, 18 May 2025, 08:59 Justi

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

Justin Zobel 于2025年5月19日周一 08:34写道： > From my understanding (what others have told me), AI generally does not > produce good quality code though. So how is that a benefit to society? >From my personal experience (what I, not others, have personally used Github Copilot for months), AI makes codin

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Mon, 2025-05-19 at 14:53 +0930, Justin Zobel wrote: > > On 19/05/2025 14:35, Konstantin Kharlamov wrote: > > > > > On Mon, 2025-05-19 at 10:03 +0930, Justin Zobel wrote: > > > > > > > > > > > > > > On 18/05/2025 16:41, Albert Vaca Cintora wrote: > > > > > > > > > > > > > > >

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 14:35, Konstantin Kharlamov wrote: On Mon, 2025-05-19 at 10:03 +0930, Justin Zobel wrote: On 18/05/2025 16:41, Albert Vaca Cintora wrote: On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: If the contributor cannot tell you the license(s) of the code that was used to generate the

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On Mon, 2025-05-19 at 10:03 +0930, Justin Zobel wrote: > > On 18/05/2025 16:41, Albert Vaca Cintora wrote: > > > > > > > > > > > On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: > > > > > > > > > > > If the contributor cannot tell you the license(s) of the code > > > that was used

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 19/05/2025 05:02, Ingo Klöcker wrote: On Sonntag, 18. Mai 2025 16:52:00 Mitteleuropäische Sommerzeit Christoph Cullmann wrote: On Sunday, May 18th, 2025 at 09:12, Albert Vaca Cintora wrote: On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: If the contributor cannot tell you the license(s) o

Re: Coding assistants for KDE

On 19/05/2025 06:05, Ingo Klöcker wrote: On Sonntag, 18. Mai 2025 21:32:20 Mitteleuropäische Sommerzeit Ingo Klöcker wrote: Yes, there is the theoretical threat that an AI learned code that's under a less liberal license like the GPL or even under one of the "new" not-OSI- approved licenses used

Re: Disallow or discourage use of "AI" tools (Christoph Cullmann)

On 18/05/2025 16:41, Albert Vaca Cintora wrote: On Sun, 18 May 2025, 08:59 Justin Zobel, wrote: If the contributor cannot tell you the license(s) of the code that was used to generate the code, then it's literally gambling that this code wasn't taken from another project by Gemini a

  1   2   3   4   5   6   7   8   9   10   >