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

2025-05-15 Thread Justin Zobel
On 16/05/2025 00:48, Konstantin Kharlamov wrote: On Fri, 2025-05-16 at 00:29 +0930, Justin Zobel wrote: On 15/05/2025 23:57, Konstantin Kharlamov wrote: On Thu, 2025-05-15 at 16:09 +0200, Felix Ernst wrote: Late reply, but I also wanted to mention that I am 100% in support of

Re: Proposal: Encourage squashing commits when merging

2025-05-15 Thread Soumyadeep Ghosh
This have been a problem for me also, like I have created multiple commits, and then when the MR is being merged, I would request the maintainer to specifically squash and merge to keep the consistancy. But they might forget, or that MR might be very insignificant to give it a 2nd thought. How e

Re: Proposal: Encourage squashing commits when merging

2025-05-15 Thread Ben Cooksley
On Fri, May 16, 2025 at 4:16 AM Volker Krause wrote: > On Donnerstag, 15. Mai 2025 16:55:01 Mitteleuropäische Sommerzeit Felix > Ernst > wrote: > > Gitlab allows squashing commits while merging. I suggest to have the > > checkbox for this ticked by default. Contributors would still be able to > >

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

2025-05-15 Thread Benson Muite
On Thu, May 15, 2025, at 9:28 PM, Alexander Potashev wrote: > Hi Benson, (everyone,) > >> Code contributions made using AI trained on unknown data is problematic. > > Is this purely a legal/intellectual property concern? > This is a concern. People have pointed out others. > > If we can gene

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

2025-05-15 Thread Alexander Potashev
Hi Benson, (everyone,) > Code contributions made using AI trained on unknown data is problematic. Is this purely a legal/intellectual property concern? If we can generalize this concern as "a contributor submits code incompatible with the project's license, thus breaching the license" , n

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

2025-05-15 Thread Volker Krause
On Dienstag, 13. Mai 2025 22:36:39 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. > > Bad news: 1 repo still failing > > G

Re: Proposal: Encourage squashing commits when merging

2025-05-15 Thread Volker Krause
On Donnerstag, 15. Mai 2025 16:55:01 Mitteleuropäische Sommerzeit Felix Ernst wrote: > Gitlab allows squashing commits while merging. I suggest to have the > checkbox for this ticked by default. Contributors would still be able to > untick it as they see fit. > > I think "encouraging squashing" i

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

2025-05-15 Thread Wodsfort
I think KDE developers shouldn`t use AI чт, 15 мая 2025 г. в 17:39, Benson Muite : > > Code contributions made using AI trained on unknown data is problematic. > KDE does also create a lot of data that could be used to improve KDE. It > may be good to see if AI or ML tools could use some of this

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

2025-05-15 Thread Konstantin Kharlamov
On Fri, 2025-05-16 at 00:29 +0930, Justin Zobel wrote: >   > On 15/05/2025 23:57, Konstantin Kharlamov wrote: >   >   > >   > > On Thu, 2025-05-15 at 16:09 +0200, Felix Ernst wrote: > >   > > >   > > > > > > > > > Late reply, but I also wanted to mention that I am 100% in > > > support of > > > a

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

2025-05-15 Thread Mark Penner
May 15, 2025 09:10:39 Felix Ernst : > I wouldn't even mind if we went one step further and actively promoted e.g. > Plasma as "free of AI". This does not need to be fully true, but this would > be more of an activism and marketing angle I would like to see. There is a > good chance though that

Re: Proposal: Encourage squashing commits when merging

2025-05-15 Thread Konstantin Kharlamov
On Thu, 2025-05-15 at 16:55 +0200, Felix Ernst wrote: > Gitlab allows squashing commits while merging. I suggest to have the > checkbox for this ticked by default. Contributors would still be able > to untick it as they see fit. > > I think "encouraging squashing" is the better default because Git

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

2025-05-15 Thread Justin Zobel
On 15/05/2025 23:57, Konstantin Kharlamov wrote: On Thu, 2025-05-15 at 16:09 +0200, Felix Ernst wrote: Late reply, but I also wanted to mention that I am 100% in support of any anit-AI messaging and policies we might choose. The wording as linked by Akseli in their first post seems like a goo

Proposal: Encourage squashing commits when merging

2025-05-15 Thread Felix Ernst
Gitlab allows squashing commits while merging. I suggest to have the checkbox for this ticked by default. Contributors would still be able to untick it as they see fit. I think "encouraging squashing" is the better default because Gitlab has features like the "Apply suggestion" button which pro

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

2025-05-15 Thread Benson Muite
Code contributions made using AI trained on unknown data is problematic. KDE does also create a lot of data that could be used to improve KDE. It may be good to see if AI or ML tools could use some of this data to improve KDE in an ethical manner. On Thu, May 15, 2025, at 5:09 PM, Felix Erns

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

2025-05-15 Thread Konstantin Kharlamov
On Thu, 2025-05-15 at 16:09 +0200, Felix Ernst wrote: > > > > Late reply, but I also wanted to mention that I am 100% in support of > any anit-AI messaging and policies we might choose. > > The wording as linked by Akseli in their first post seems like a good > starting point in that regard: >

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

2025-05-15 Thread Felix Ernst
Late reply, but I also wanted to mention that I am 100% in support of any anit-AI messaging and policies we might choose. The wording as linked by Akseli in their first post seems like a good starting point in that regard: >Other projects have already done something similar, see for example

Re: Korean text rendering

2025-05-15 Thread Sung-Jae, Cho
Thanks for reporting. :) Have a nice day. On Thu, May 15, 2025 at 10:27 PM Igor Mironchik wrote: > Hi. > > > Could you check your system health check with memtest86 or > > gnome-disk-utility? > > I checked my hardware - everything is fine. I was just wondering why the > Korean text is so slow.

Re: Korean text rendering

2025-05-15 Thread Igor Mironchik
Hi. Could you check your  system health check with memtest86 or gnome-disk-utility? I checked my hardware - everything is fine. I was just wondering why the Korean text is so slow. I think it's a problem on my end in some software. Well, guys, as on your end, Korean works fine - everything i

Re: Korean text rendering

2025-05-15 Thread Konstantin Kharlamov
On Thu, 2025-05-15 at 12:46 +0300, Igor Mironchik wrote: > Hi. > > On 15.05.2025 10:48, Konstantin Kharlamov wrote: > > On Thu, 2025-05-15 at 10:38 +0300, Igor Mironchik wrote: > > > I guess too this is system specific. I'm on openSUSE Tumbleweed. > > > Changing editor's font to Droid Sans doesn't

Re: Korean text rendering

2025-05-15 Thread Sung-Jae, Cho
> I almost sure already this is Intel HD 620 graphics not enough for Koreans :) I think that's also good hardware still. And next test is done with Intel N2840 Celeron notebook with 4 GB RAM, SATA3 SSD. It's not exactly same with Intel HD620 Graphic core, but it was produced with Ivy Bridge base

Re: Korean text rendering

2025-05-15 Thread Sung-Jae, Cho
Hi, again. First test is done with Virtual Box. I captured a video and please check the clip below. https://drive.google.com/file/d/1WXl4CxMv1iNkO72F_5uXnLyOGVG33ytA/view?usp=sharing I think it is not much delayed. After installing OpenSuse tumbleweed, I added ibus-hangul package with ibus-daemon,

Re: Korean text rendering

2025-05-15 Thread Sung-Jae, Cho
Thanks for the information. :) Additionally, I'll test with an Intel HD Graphics 620 notebook, too. On Thu, May 15, 2025 at 5:09 PM Igor Mironchik wrote: > On 15.05.2025 10:44, Sung-Jae, Cho wrote: > > I'll try again with openSUSE Tumbleweed. :) > Please, wait a day. I'll try with virtual machi

Re: Korean text rendering

2025-05-15 Thread Igor Mironchik
On 15.05.2025 10:44, Sung-Jae, Cho wrote: I'll try again with openSUSE Tumbleweed. :) Please, wait a day. I'll try with virtual machines and real machines, both. And if you can bring some hardware information with a video card driver, xorg-driver, etc, it'll be helpful for finding the cause.

Re: Korean text rendering

2025-05-15 Thread Konstantin Kharlamov
On Thu, 2025-05-15 at 10:38 +0300, Igor Mironchik wrote: > I guess too this is system specific. I'm on openSUSE Tumbleweed. > Changing editor's font to Droid Sans doesn't help. > > Ok. I see that this issue is system specific, so my question is > answered. Maybe somebody can check this issue on