Re: KDE Review Request: Keep Secret

Pretty nice app! I opened some Issues on the Gitlab issue tracker (since no Bugzilla product for it is set up yet) and then fixed a few of them with https://invent.kde.org/mart/keepsecret/-/merge_requests/2. Nate On 7/15/25 6:22 AM, Marco Martin wrote: Hi all, I have been working over the

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

This is a complex topic that could go on for ages. For me, if I can tell you used AI for something, it's because the result wasn't good, and had that "obviously AI" flavor to it. You wasted both of our time and some of the planet's resources. For this reason, we already have written guidance

Re: Proposal: archive plasma-pk-updates

On 4/17/25 8:42 PM, Ben Cooksley wrote: In favour of all three being archived, if there are no objections can someone please file a ticket and i'll handle the archival? Done! Nate

Proposal: archive plasma-pk-updates

https://invent.kde.org/system/plasma-pk-updates/-/commits/master?ref_type=heads It has not been ported to Qt 6 nor gotten any meaningful development in years. Nate

Proposal: archive KMplayer

https://invent.kde.org/multimedia/kmplayer/-/commits/master?ref_type=heads It appears to not have had any meaningful development in 3 years, and it's listed as "still in development and isn't released yet" on https://apps.kde.org/kmplayer. It's not ported to Qt 6, the last release appears to

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

Hooray! Thanks for being on top of this, Albert, and thanks everyone for keeping our apps' CI pipelines green! Nate On 3/4/25 11:45 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

Re: Move Breeze to Framework

On 1/3/25 8:17 AM, Nicolas Fella wrote: Am 30.12.24 um 18:51 schrieb Nate Graham: A long term concern I have is that it's messy and unpleasant to have default styling data scattered across so many places. Ideally we'd be able to centralize *all* data about a particular style in a s

Re: Move Breeze to Framework

On 12/31/24 4:59 AM, Ingo Klöcker wrote: On Montag, 30. Dezember 2024 18:51:39 Mitteleuropäische Normalzeit Nate Graham wrote: A long term concern I have is that it's messy and unpleasant to have default styling data scattered across so many places. Ideally we'd be able to centralize

Re: Move Breeze to Framework

On 12/30/24 12:31 PM, christ...@cullmann.io wrote: On 2024-12-30 18:51, Nate Graham wrote: I see an opportunity to move closer to that here. So my preference would be to implement the proposal, but also: - the default window decorations remain in Breeze - the default colors remain in Breeze

Re: Move Breeze to Framework

A long term concern I have is that it's messy and unpleasant to have default styling data scattered across so many places. Ideally we'd be able to centralize *all* data about a particular style in a single repo, so that making changes is easy and that repo can be swapped out for another one in

Re: KSMServerInterface logout

On 9/8/24 1:33 PM, Martin Koller wrote: In KF5 times there was a DBus method "logout" in KSMServer. In KF6 this is no longer there. What is the replacement / how can I invoke the logout step from within my application ? You want the "promptLogout" method in org.kde.LogoutPrompt Nate

Re: Current Konsole Crashes

On 8/31/24 9:38 AM, Tomaz Canabrava wrote: Hello all, konsole started to crash a lot; daily for me. i tried to find the culprit but it doesnt seem to be in konsole code - at least theres no change in the code that it crashes for many years. i believe there is a change in kxmlgui actionCollect

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

+cc Matthias On 6/5/24 1:16 PM, Ingo Klöcker wrote: On Mittwoch, 5. Juni 2024 20:24:52 CEST Ben Cooksley wrote: On Wed, Jun 5, 2024 at 7:26 PM Ingo Klöcker wrote: In my opinion, the ID of massif-visualizer should be changed back to org.kde.massif-visualizer. Or massif-visualizer needs to for

Re: Proposal unify back our release schedules

On 4/22/24 19:19, Albert Astals Cid wrote: El dilluns, 22 d’abril del 2024, a les 17:12:46 (CEST), Nate Graham va escriure: Now, let's say we make Gear use Plasma's current release schedule by syncing up the feature releases and adopting the Fibonacci bugfix releases. If we do

Re: Proposal unify back our release schedules

Ok, so happily I actually see quite a bit of agreement here, regardless of what else we do. 1. Fibonacci bugfix releases are good, and we could benefit from having Gear adopt these. 2. Severing implicit dependencies is a good idea. Shared libraries in Gear are especially problematic and coul

Re: AppStream Metadata with our releases

On 3/25/24 23:27, Albert Astals Cid wrote: El dilluns, 25 de març de 2024, a les 19:37:07 (CET), Volker Krause va escriure: As Itinerary was mentioned, the process there currently is to run David's KF changelog script over all repositories in Itinerary's dependency chain and take the top 5 or so

Re: Proposal unify back our release schedules

Thanks for taking the time to assemble this email, Carl. These are arguments I've brought up individually myself for years, and I think they have merit. Taken together, for me they paint a picture of a project that was attempted, faithfully executed on, but didn't end up delivering the benefi

Re: Automation & Systematization sprint in Berlin in late April

Hello Tracey and anyone else interested--If you're coming, please add yourself to the table at https://community.kde.org/Sprints/Goals/2024. Also if you need support for travel and lodging costs, you can apply at https://reimbursements.kde.org/events/187. For those of us traveling across the wo

Re: Automation & Systematization sprint in Berlin in late April

Sorry for the crazily delayed response. I'm digging out from under the megarelease email bomb. On 3/3/24 16:23, Albert Astals Cid wrote: What's the plan for travel support requests? Should we start filing requests at https://reimbursements.kde.org ? Yep. The event is https://reimbursements.k

Re: Automation & Systematization sprint in Berlin in late April

Quick update on this. the dates are now locked in, but we're still finalizing a venue in Berlin. More information will be provided as it becomes available. Thanks for your patience here, everyone! Nate On 1/31/24 16:26, Nate Graham wrote: Hello folks! I'd like to gauge interes

Post-MegaRelease projects

Hello everyone, Congrats to the entire KDE community on the impending launch of the KDE 6 MegaRelease! I'm so impressed with how folks came together to make it amazing. It's a very impressive release and I think people are gonna love it. I've started pondering post-megarelease projects. We'v

kio-gdrive changes needed to conform to new Google requirements

Hello folks, The KDE e.V. board received an email from Google about changes required for kio-gdrive. I've opened an Issue about it at https://invent.kde.org/network/kio-gdrive/-/issues/1 with more details. To my knowledge, kio-gdrive is maintainerless, so we're in need of a kind soul who will

Re: Defining a developer name for our applications metadata

Sounds good! Thanks for tackling this, Timothée. Nate On 2/2/24 08:55, Timothée Ravier wrote: Hi everyone, Following suggestions in the thread, I'll start updating our AppStream metadata with: ``` KDE ``` Thanks -- Timothée Ravier CoreOS co-Team Lead Red Hat

Automation & Systematization sprint in Berlin in late April

Hello folks! I'd like to gauge interest in an in-person sprint supporting the Automation & Systematization goal. Right now we are targeting Berlin on April 19th - April 24th. KDE e.V. has budget available to help with travel and lodging costs. This will be a triple-threat sprint, with the Ac

Re: Defining a developer name for our applications metadata

What sprang immediately to my mind was simply "KDE". Short and sweet. Nate On 1/30/24 10:34, Timothée Ravier wrote: Hi folks, Flathub is now requiring that applications define a "developer_name" tag in their metadata (see [1], [2]). What do folks think would be a good value for our applic

Re: Exception request: High contrast frames and separators

The underlying work is already there, and this doesn't seem to add much new code, just some UI changes and new strings (which will also need a string freeze exception). In light of the Accessibility Goal, I support an exception here. +1. Nate On 12/31/23 10:59, Akseli Lahtinen wrote: Hi!

Re: Spacing in our apps

This is an important topic, so I appreciate you bringing it up, Carl. It's been on my mind recently as well. For some background, the reason why we have multiple spacing values in Kirigami and Plasma (e.g. SmallSpacing, LargeSpacing, GridUnit, etc) is because in the past we didn't want develop

Re: Ark Qt Version

I'm not a heavy user of Ark, but I haven't noticed any glaring defects in its Qt 6 version over the past few months. FWIW. I vote for adding it to the list to encourage wider testing. Nate On 12/11/23 04:07, Jonathan Riddell wrote: I'm e-mailing everyone who has committed to Ark in the last

Unified internal communications channel

Hello everyone, There have been a couple instances of drama this week caused by decisions being made without some of the relevant stakeholders knowing about them. In all cases, the decisions were announced, but either not announced in the places where all the stakeholders saw it, or not all s

Re: Bug Safari Project

ill be migrated there and I'll continue to manage the script itself during that time too. Then if the testing goes well it should be fairly easy to move reports into the Plasma room and find someone to manage the script full-time. Regards, Ben On 15/8/23 10:39, Nate Graham wrote: +

Re: Do you use votes on Bugzilla tickets to help you make decisions?

Elvis Den fre 4 aug. 2023 kl 23:55 skrev Harald Sitter : Never looked at them. Never seen the benefit. On Fri, Aug 4, 2023 at 3:53 PM Nate Graham wrote: Hello folks! I often find myself explaining to users that votes on Bugzilla tickets are generally meaningless and not used by most develope

Re: Planning the final 6 release timeframes

Thanks for organizing this, David. Where and how will the meeting be held? Nate On 8/22/23 09:22, David Edmundson wrote: A time has been chosen on the poll with a clear winner: 4th September 18:00 CEST See you all there David Edmundson

Re: Per project repository snapcraft files?

On 8/19/23 18:42, Scarlett Moore wrote: Only on release! We will not be building from master! We don't want unstable snaps. Thanks, Scarlett Aha! Sounds fine, then. In fact I believe this is the direction we want to go in with FlatHub too: triggering the remote builds from spec files located

Re: Per project repository snapcraft files?

On 8/19/23 15:45, Scarlett Moore wrote: No. It will be telling launchpad to build them via API. Launchpad will upload to store its own artifacts. Our current setup has launchpad sending the snaps back to our server and we upload to store. This new proposal would be significantly less data goin

Re: Per project repository snapcraft files?

to upload something to a remote server on every commit! It would be quite bad if KDE developers were unable to merge merge requests because an external server is down or overloaded. Nate On 8/19/23 09:16, Scarlett Moore wrote: On Sat, Aug 19, 2023, 7:48 AM Nate Graham <mailto:n...@kd

Re: Per project repository snapcraft files?

Right now, our Flatpak CI jobs are self-contained; they generate a Flatpak without the need for any external servers. They're not uploading anything to FlatHub or elsewhere. I might be misunderstanding something, but it seems like these proposed Snap CI jobs will be interacting with an externa

Re: Bug Safari Project

onto the first suggestion, the script still works with non-Plasma bugs if other teams want to use it by modifying bug_lists.json but the bug report name can be set to show what the bugs are for. Regards, Ben On 29/7/23 04:07, Nate Graham wrote: Thanks, looks like a great start! Can we ge

Re: Request for relicensing of CMakeLists.txt files in plasma-welcome from GPL to BSD-2-Clause

On 8/13/23 20:08, Aaron Rainbolt wrote> It's called Karton - it's intended to be a KDE-centric libvirt frontend that will eventually be able to replace GNOME-based tools like virt-manager and GNOME Boxes. It will be written using Qt Quick and Kirigami. Justin made a Matrix room for it at #karton

Re: Request for relicensing of CMakeLists.txt files in plasma-welcome from GPL to BSD-2-Clause

I give my permission. P.S. what's the project? Nate On 8/13/23 18:12, Aaron Rainbolt wrote: Hello, and thanks for your time. As per the KDE Licensing Policy at https://community.kde.org/Policies/Licensing_Policy, all CMake code in KDE must be licensed under BSD-2-Clause. However, several

Do you use votes on Bugzilla tickets to help you make decisions?

Hello folks! I often find myself explaining to users that votes on Bugzilla tickets are generally meaningless and not used by most developers to help prioritize work. After I explain this, they generally express surprise, as it's not obvious. I find myself wondering whether it would make sen

Re: Bug Safari Project

dio-qt&product=systemsettings&product=Touchpad-KCM&product=user-manager&product=xdg-desktop-portal-kde&query_based_on=VHI-priority%20Plasma%20bugs&query_format=advanced On 7/24/23 05:00, Ben Bonacci wrote: Hi Nate, I've recorded the script in action which can be

Re: Bug Safari Project

Very cool stuff. Can we see it in action anywhere? Nate On 7/23/23 01:38, Ben Bonacci wrote: Hi Ben, Thanks for the suggestion! Now after each request the script will wait 1-5 seconds before making the next request. Regards, Ben On 22/7/23 22:30, Ben Cooksley wrote: On Sun, Jul 23, 2023

Re: Retiring Phabricator - Migrating tasks to Gitlab

On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks have no real "home"; they just have project tags, and they can have multiple such tags to be able to belong to multiple projects. For example "VDG" and also "Plasma". Such a Task shows up in both projects' workboar

Re: Retiring Phabricator - Migrating tasks to Gitlab

Great, this will be a good thing to have behind us. Because workboards in GitLab are Label-driven via automation, I think we would have to make each workboard column in Phabricator transform into a custom label in GitLab so that Tasks' positions in workboards can be preserved when they move to

KDE scanning apps (From: Part-time KDE sabbatical, feedback or guidance appreciated (but no pressure) )

On 5/8/23 10:12, Martin Steigerwald wrote: As for your ideas for Skanpage: I like them! At the moment I find myself using either Skanpage or Skanlite depending on use case. I'd love to have it all in one app, but that may not be feasible. Unrelated to the original subject of this email, but Ska

Re: developer account set up

There's also no reason anymore why they need to use a work branch in the main repo; a fork works just fine. I do nearly all of my development using personal forks; it's a 100% supported first-class citizen experience. Nate On 5/7/23 17:06, Joshua Goins wrote: We usually recommend contributors

Re: developer account set up

-Utarsh It might be worth re-thinking this policy now that we use GitLab. People don't need a developer account to fully contribute anymore. Nate On 5/7/23 09:41, Johnny Jazeix wrote: Le sam. 6 mai 2023 à 23:31, Nate Graham <mailto:n...@kde.org>> a écrit : Hello Utk

Re: developer account set up

Hello Utkarsh, You don't need a developer *account* to start contributing, and in fact you can't have one until you've made a number of contributions already. :) If you're looking for information about starting the process of contributing with code, we have a bunch of documentation at https:

Re: Ask about new KDE functionnalities.

On 4/28/23 04:14, Nicolas Lécureuil wrote: Hello, i don't know if i post on the good ML but i have a friend searching for developpers to mostly integrate ChatGPT into KDE. He accepts to contribute financially. "     I don't know if it's possible, but for example, I would like to allow the

Re: Proposal to deprecate KFloppy

Does it work for *anyone* with a modern distro? If not, then I think archiving it makes sense. Time marches on. :) If it does work for *someone* with a modern distro then at the very least the UI needs to detect when it will be broken and tell this to the user in advance to prevent frustration

Re: About automatic day/night theme changing feature.

Hello Hakan, You can CC yourself on https://bugs.kde.org/show_bug.cgi?id=408563 to be notified once the feature is implemented implemented. Work has begun already; see https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2567. Plasma 6.0 is the release targeted for it. Nate On

Re: Update | BE4FOSS project coming to an end, KDE Eco continues to grow

Thank you so much for your work to organize and push forward this initiative, Joseph! It's great to see how the ethos of energy efficiency has taken root in the community. Nate On 3/22/23 09:54, Joseph P. De Veaugh-Geiss wrote: Dear KDE community, I am sad to inform you that next week on 3

Re: "Gardening" old bugreports

We can turn it off for bugs reported by you, but I'm not sure "I'm getting too many emails" is a good reason to turn it off for whole products. These products aren't owned by you; they're community property and it's important for them to get triaged for the benefit of everyone. Nobody wins when

Re: VDG application design sprint?

On 1/24/23 09:42, Vinzenz Vietzke wrote:> Hey there, Just to have it said: if you want to make it a in person sprint we (TUXEDO) can offer rooms, network, food etc. at our office in Augsburg. Cheers, vinz. That is super generous, thanks so much for the offer, Vinzenz! Nate

Re: VDG application design sprint?

Very interested! Ever since the GNOME folks created Libadwaita, I feel like their 3rd-party app ecosystem has really taken off, and it seems like something they put a lot of planning and foresight into making happen. In KDE land we have a lot of 1st-party apps but not as much on the 3rd-party

Re: "Gardening" old bugreports

Hello folks, I did approve this initiative and I do think there's value to it, but of course we can definitely have this discussion in the open and tweak its parameters, or end it if we think it's destroying more value than it's creating. I totally agree with Nicolas that in an ideal world,

Re: Unknown protocol "konq"

On 12/27/22 11:26, Reindl Harald wrote: but given i use konqueror only as filemanager because dolphin with the lack of bookmarks is a joke Dolphin has bookmarks, FWIW: https://i.imgur.com/ylXHTBf.jpg Nate

Re: Would Scandoc be somthing for Extragear?

Hello TObias, Have you checked out Skanpage? It does PDF scanning, including creating multi-page PDF documents out of the scanned files. It also integrates with the Purpose framework to offer a simple "Share" menu that lets you email scanned documents very quickly. Nate On 11/9/22 06:32, T

Funding opportunity for your projects

Hello KDE community members and developers! I'm writing to everyone about something very exciting: the NLnet Foundation (https://nlnet.nl) has made us aware that they have substantial quantities of funds available for FOSS projects that KDE is eligible for: up to 5€ per project. If you hav

Re: Archiving KDE Telepathy?

+1 for the reasons you provided. Nate On 10/25/22 11:08, Nicolas Fella wrote: Hi, there various KTP modules have seen very little development over the last years. Most of the activity that did happen was either release housekeeping stuff like version bumps or general code cleanup (i.e. the ki

Re: Product organization in Bugzilla

On 9/19/22 15:33, Johannes Zarl-Zierl wrote: To end my rant on a productive note: Yes, sure - hide internal components as you see fit (maybe hide archived/unmaintained components as well, while you're at it). But IMO the main problem is that users have to search on bugzilla instead of clicking a

Re: KDE on Linux Unplugged this week

An interesting listen. Here's the tl;dl regarding Brent's complaints: - Kubuntu 22.04 seemed buggier than 20.04 - Kubuntu repo management password bug stayed unfixed for too long - Plasma 5.25 on other distros seemed buggier than usual too, specifically: -- Multimonitor was a pain -- Activities w

Product organization in Bugzilla

Hello folks, We often get feedback from bug reporters that it's hard to find the right product in https://bugs.kde.org/enter_bug.cgi because it contains just a giant intimidating list. Yes, people can use their browser's search function, and yes, if a bug is files in the wrong place, it will

Re: New releases for bugfixes

On 9/8/22 05:51, Nicolas Fella wrote: Hi, I don't think Nate or anyone wants to propose a strict policy that when X then Y has to happen. That's just not how we operate in KDE. I do think it is valuable though to discuss and create some guidelines/shared understanding/soft policy that maintainer

Re: New releases for bugfixes

To revive this thread, I think the issue is that it feels sort of subjective what kind of bugs are bad enough that we think like a new release is worth it. So maybe we can try to get specific and say that we should make a new release for fixes of Bugzilla bug reports where: - Priority is VHI or

Re: New releases for bugfixes

On 8/25/22 22:59, Albert Astals Cid wrote: c) Who decides which bugs "are important" because for every bug, there's always a person out there that thinks it's the most important bug ever. d) What do we release? i.e. imagine we find one of those "important bugs" in dolphin and we have to release

New releases for bugfixes

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 ma

Re: Missing product versions in Bugzilla

IIRC, the release team takes care of updating product-versions of apps on Bugzilla using a script. CCing them. Nate On 7/23/22 16:10, Glen Ditchfield wrote: Phabricator has a task T2373: Make sure Bugzilla versions of our products are updated.  I've noticed an assortment of missing versions

Re: Asking for a new project

If you're aiming to compete with Krita and try to siphon users away from it and towards your fork instead, then you are producing what's known as a "hostile fork" and I very much doubt that Krita's developers will be interested in helping you with it. If on the other hand your fork is simply a

Re: Approval request for feature idea

Hello Samuel, There's an idea for the future of theming in Plasma 6 that would use CSS to define a "universal theme" that would then be consumed by our QQC2, Plasma, and GTK theming to keep them all in sync automatically. See https://phabricator.kde.org/T13467. This is one of the options prese

Re: Asking for a new project

Indeed, I would recommend working with them on a plan to make sure your changes are mergeable and eventually merged into the main repo. If that doesn't end up happening, all your hard work will have been wasted. Nate On 5/31/22 18:45, Aleix Pol wrote: There's a big "Fork" button on top here:

Are translation changes required when switching to the cherry-pick workflow

Hello folks, If a project switches from the merge-forward workflow to the cherry-pick-backward workflow, is anything needed to make sure translations end up both in master and also the stable branches? Nate

Re: The KIPI fate

So we just got our first bug report about this: https://bugs.kde.org/show_bug.cgi?id=452738 The reporter says he was using two plugins that still worked: one to upload files to Google Drive, and one to print multiple images arranged on a single piece of paper. He notes that the Google Drive

Re: Marge bot integration

We have this issue all over Plasma. I think adopting a bot to do it would be a great idea. It seems like this could also be used to automatically cherry-pick commits. Perhaps if the merge request has `cherry-pick` in its tags, it could automatically cherry-pick the commits to a branch correspo

Re: Starting with Contribution

Hello Abhinav, There are many ways to contribute. Check out https://community.kde.org/Get_Involved/development, if you haven't already. In general we find that it's best to "scratch your own itch" by working on something that you're personally interested in, or whose bugs annoy you. Looking

Re: Genderidentity

On 1/6/22 10:56, Nicolás Alvarez wrote: There is a time and place to teach kids about the complexity of gender and I don't think an exercise about arithmetic/counting is the right place. https://en.wikipedia.org/wiki/Lie-to-children Speaking from the perspective of being a parent of two childre

Re: Moving Kile to KDE Gear

Sounds good, thanks. Where is the documentation task tracked? Can I help? Nate On 12/28/21 03:43, Michel Ludwig wrote: Hi Nate, On 28.12.21 05:10, Nate Graham wrote: Hello folks, I landed some patches for Kile recently and noticed that it hasn't had any releases in a while

Re: Moving Kile to KDE Gear

Sounds good, thanks. Where is the documentation task tracked? Can I help? Nate On 12/28/21 03:43, Michel Ludwig wrote: Hi Nate, On 28.12.21 05:10, Nate Graham wrote: Hello folks, I landed some patches for Kile recently and noticed that it hasn't had any releases in a while

Moving Kile to KDE Gear

Hello folks, I landed some patches for Kile recently and noticed that it hasn't had any releases in a while, and development activity is a bit low. Given that it seems to be community-maintained at the moment, I'd like to propose that it be added to KDE Gear so that it can at least have regul

Re: Contribute to KDE community

Hello Neeraj, Welcome! Feel free to get started on any of those projects that interest you. We find that it is best to "scratch your own itch" by working on software that you personally use and like. When you're ready to get started, you might find these links useful: https://community.kde.o

Re: Merge stable to master vs cherry-picking

I don't have any insights into any technical blockers, but if it is technically feasible, I think it would be good to move everything to the cherry-pick model due to the following advantages: 1. Unlike the merge-stable-to-master workflow, cherry-picking can be done from the GitLab web UI, whic

Re: GitLab config in older repositories

We have rebasing in the UI in our CE instance. Nate On 12/3/21 11:06, Christoph Grüninger wrote: Hi Kai Uwe, Last time I tried, rebasing in the UI was an GitLab enterprise feature. Not sure what we use in KDE. I searched for a source to back this up, and found that you can rebase with a com

Re: KDE Incubator Project Application

Hello Frank, The name makes me think the app would be a converter of file formats (e.g. MP3 -> Ogg Vobris), rather than a unit converter. I might suggest renaming it. This is because unit and scientific conversion functionality already exists in KRunner and Kickoff, using the data from the KU

Re: Fixing XWayland HiDPI scaling

ll and shouldn’t be too difficult to maintain. I think the benefits are very clear. On 12/11/2021 19:45, Nate Graham wrote: Hello Alex, Please feel free to help get these issues fixed upstream, as it seems like you already have a good grasp of the technical issues at play. Nate On 11/1

Re: Fixing XWayland HiDPI scaling

Hello Alex, Please feel free to help get these issues fixed upstream, as it seems like you already have a good grasp of the technical issues at play. Nate On 11/11/21 06:03, Alex Bujorianu wrote: The current status of XWayland applications in both Gnome and KDE Wayland implementations leave

Re: Rollout of Gitlab CI

On 9/30/21 17:00, Amber Schenck wrote: Would it be possible for a project outside of KDE infra (https://sourceforge.net/projects/kuroo/) to use KDE CI? Unit tests have been on the TODO list for a long time, but the extra effort of setting up CI has discouraged it so far. Using KDE CI would make t

Re: [PATCH] ksystemstats use KDE_INSTALL_DBUSINTERFACEDIR

Hello Kelly, Thanks for the patch! However KDE does not do patches over email anymore; we use Merge Requests on invent.kde.org. This facilitates better code review, milestone tracking, and CI integration (soon). Can you submit this patch at https://invent.kde.org/plasma/ksystemstats/-/merge_r

Re: Project Submission

Hello Farkas, Have you considered making this a Plasma widget using QML? Plasma has an existing infrastructure for installing, deleting, adding, and removing widgets, and allowing users to see alternatives. Since this is basically an alternative launcher, it would make sense for it to appear i

Re: I want to start collaborating

Hello Alessandro, Sounds good! I would recommend reading through https://community.kde.org/Get_Involved/development and seeing what strikes your fancy. There are many possible entry points. More generally, we encourage "scratching your own itch". What issues bother you about the KDE software

Re: Should we change how we approve developer account requests?

On 8/16/21 10:11 PM, Nicolás Alvarez wrote: It's not that odd :) We as sysadmins don't know if you're actually sponsoring them until you reply approving the request, since people can request developer access and enter any name as the sponsor. That's pretty much what the approval is for, to con

Should we change how we approve developer account requests?

While writing an email in support of a recent request for developer access that I encouraged someone to apply for, it struck me as odd that the sponsor can approve. I would expect the sponsor to approve or else they would not have sponsored the application in the first place! Instead, wouldn't

Re: Shall we condense the bots' commit announcements

The code has been changed to make this a possibility. If you'd like to opt into it for your channels, you need to set `short_message=True` in the appropriate channel config in the sysadmin/irc-notifications repository. Nate On 5/26/21 7:49 AM, Frederik Schwarzer wrote: Am 26.05.2021 03:12 s

Re: Notice of withdrawal of CI services: KDevelop and KDE Connect

This kind of problem will be generically solved for everyone once we get GitLab's pre-commit CI, which can block merging of MRs until the failures are resolved--so they actually *will* be resolved. How soon can we get that finally rolled out across KDE? Until that happens, this sort of problem

Re: Can we get tags and tarballs for the KDE Qt patch collection

On 6/8/21 9:02 AM, Nicolas Fella wrote: On 07/06/2021 20:46, Nate Graham wrote: Hello folks, The Fedora packagers were mentioning to me today that it would be a lot easier for them to ship Qt with our patch collection if we made tags and tarballs. Is this something we could look into doing

Re: Can we get tags and tarballs for the KDE Qt patch collection

On 6/8/21 5:20 AM, David Redondo wrote: Am Dienstag, 8. Juni 2021, 12:51:35 CEST schrieb Neal Gompa: You *already* are using version numbers and bumped it to 5.15.3: https://blog.neon.kde.org/2021/06/04/kde-neons-qt-is-now-built-from-kdes-git -branches/ KDE did not bump the version number, the

Can we get tags and tarballs for the KDE Qt patch collection

Hello folks, The Fedora packagers were mentioning to me today that it would be a lot easier for them to ship Qt with our patch collection if we made tags and tarballs. Is this something we could look into doing? Nate

Re: kdesrc-build expects fixed path

I think a better change would be to return to the older, simpler, shorter "flat" folder structure. See https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/96 Nate On Sat, 05 Jun 2021 22:27:44 -0600 Ömer Fadıl USTA wrote > I think we need to change templates and other docs fo

Re: Thanks for maintaining Baloo

[cc Stefan Brüns, the maintainer. :) ] I agree! It's been working nicely for me too. Nate On 6/3/21 1:55 AM, Shantanu Tushar Jha wrote: Hey folks, Just a quick shout-out to those of you working on Baloo. I have not been following development but I have observed that searching for my docume

Shall we condense the bots' commit announcements

Hello all, Recently we removed the commit announcement bots from the #plasma and #kwin chatrooms because we felt their output was too noisy. However for the rooms where they are still active and announcing git commits, would people appreciate it if the announcements were shorter? For example

Re: Any interest in a batch file renamer in KIO?

On 5/19/21 9:10 AM, Nomen Luni wrote: I can't remember if KRename comes pre-installed in Neon? If not, doing so would increase discoverability- which may filter to other distributions. Also, the Dolphin service menu entry appears as 'Rename with KRename,' which IMO could do with changing. 'Batch

  1   2   3   >