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

Re: KDE Frameworks 6.2

[dropping kde-announce] Hello folks, Can we get a new release of Kirigami that includes https://invent.kde.org/frameworks/kirigami/-/commit/722dc268ccc8921552c027d67d5b11d1d5307ec9? This fixes a significant issue that snuck into the release which breaks a bunch of dialogs in System Settings,

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 don't end up

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

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

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

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

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

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 interest

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.

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

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

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

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

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

Re: per-issue notifications from sentry

I have personally disabled this functionality for my account already as I found them useless. Nate On 11/26/23 07:38, Harald Sitter wrote: does anyone else find the emails from sentry when a new issue appears to be rather useless? they are very noisy and often times not interesting since a

Re: plasma-framework, kactivities and kactivities-stats: please consider proper de-KF-ication now

On 11/5/23 07:42, Kevin Ottens wrote: I was clumsily advocating for this Akademy 2021 or 2022 (can't remember which). This way it's clearer to application authors when they tie themselves to a given workspace or not. Also, isn't Elisa able to work without Baloo? It even seems to do the right

Re: plasma-framework, kactivities and kactivities-stats: please consider proper de-KF-ication now

On 11/5/23 07:09, christ...@cullmann.io wrote: On 2023-11-05 12:59, Friedrich W. H. Kossebau wrote: Hi, with plasma-framework, kactivities and kactivities entering the Plasma product bundle, I assume they also will adapt to Plasma versioning. Hi, if we are atm moving stuff, might it make

Re: Bug Safari Project

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: +Justin Very cool. Can we see

Retroactive kdereview: ocean-sound-theme

Hello kde-core-devel folks, We did the KDE Review process for ocean-sound-theme a bit wrong and forgot to email this mailing list before moving it to its final home. So I'm retroactively submitting it for review in case folks see anything wrong that needs to be corrected. See

Re: KDE Review: Hash-o-Matic

On 10/2/23 13:53, Albert Astals Cid wrote: El diumenge, 1 d’octubre de 2023, a les 21:49:36 (CEST), Carl Schwan va Who checked all those marks? There's no way to know. If you scroll down to "Activity", it says who checked them after the issue was opened. I agree that the person who opened

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

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 developers to help

Re: drkonqi's many debuggers

On 8/28/23 22:25, Thiago Macieira wrote: It does because it might be missing in the system far more often than gdb. We'd get more backtraces and therefore more data if we focused on gdb Another point is that Linux distributions have been shipping gdb with debuginfod support for a year or two.

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: 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

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

Re: Per project repository snapcraft files?

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...@kde.org>&

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

Re: Bug Safari Project

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 get

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

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

Re: Bug Safari Project

this link: https://benbonacci.com/files/shares/1w-bug-safari-demo.mp4 (Expires in 1 week) Regards, Ben On 23/7/23 23:43, Nate Graham wrote: 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 ea

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,

Re: KSvg in kdereview

FWIW the code itself is almost entirely just moved verbatim from plasma-framework, which is already a framework. Nate On 6/21/23 12:41, Friedrich W. H. Kossebau wrote: Am Mittwoch, 21. Juni 2023, 12:23:55 CEST schrieb Ben Cooksley: On Wed, Jun 21, 2023 at 10:12 PM Harald Sitter wrote:

Re: sentry evaluation

To be honest, I haven't found Sentry to be that useful in its current implementation. The primary issue is that it represents a second source of truth for where crash reports live. As a result, developers who already struggle to notice Bugzilla-based crash reports have to look in a second

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'

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

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

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

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 Utkarsh,

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

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

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

Re: Proposal for using gitlab for kdereview process

Overall I think it makes sense. The key players are all already on GitLab and it's where we do code review for established projects. Nate On 2/22/23 00:59, David Redondo wrote: Am Samstag, 18. Februar 2023, 12:02:38 CET schrieben Sie: I'm not convinced more paper work is going to help us

Re: Question about the source code

you a good continuation for your amazing work. Regards, Matthieu 'Rubisetcie' Carteron Le ven. 10 févr. 2023 à 21:27, Nate Graham <mailto:n...@kde.org>> a écrit : Hello Matthieu, This behavior comes from Qt, not any KDE code. You might try looking at the source code for QM

Re: Question about the source code

Hello Matthieu, This behavior comes from Qt, not any KDE code. You might try looking at the source code for QMenu. Good luck! Nate On 2/10/23 06:00, rubisetcie wrote: Hello KDE core developer team, I hope you're having a good day. I have a question about the KDE source code : I would

Re: New repo in kdereview: kclock

I'm happy with KClock now, FWIW. I'm going to start sending merge requests for some of the little tiny UI things I notice that I don't think are worth prolonging KDEReview over. Nate On 2/2/23 21:11, Devin wrote: Hi everyone, Is there any feedback left for KClock? If not, I will consider

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

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

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: New repo in kdereview: KRecorder

of Kirigami.Units.GridUnit, which hopefully should be easy to fix. I've changed it to be based on gridUnit. On Mon, Dec 5, 2022 at 4:55 PM Nate Graham wrote: On 12/4/22 16:47, Devin wrote: I can reproduce it in the following way on Desktop: Hmm, I'm on Kirigami from master and still can't reproduce it, see

Re: New repo in kdereview: KRecorder

On 12/4/22 16:47, Devin wrote: I can reproduce it in the following way on Desktop: Hmm, I'm on Kirigami from master and still can't reproduce it, see the attached video. I think I found the problem; I use 11pt Noto Sans font. I can't reproduce the issue with the default 10pt. This probably

Re: New repo in kdereview: KWeather

This happens on X11 when using QtDialogs for reasons I don't understand. See https://invent.kde.org/frameworks/knewstuff/-/commit/ea19fa6e824650f3257e8047d6f90e01899b2e03. Nate On 11/29/22 16:48, Devin wrote: Hmm, I have no idea why the behaviour is different for you, but I get:

Re: New repo in kdereview: KRecorder

ts header. Added On Mon, Nov 14, 2022 at 7:22 PM Nate Graham wrote: Much better! Most issues are fixed now. I feel like we're close. See a few remaining comments: The left pane's placeholder message is off-center with narrow windows. Fixed. I can still see this: https://i.imgur.c

Re: New

On 11/17/22 02:08, David Faure wrote> Done: kconfig v5.100.1 f4dcf631e9f22e25c768c323762672716ddbdd02 8bbb7951d74e8e289f7b0599887ef328b2726fdbdaae18effda2c9d7f18a82da sources/kconfig-5.100.1.tar.xz plasma-framework v5.100.1 0435ec52c76092bc8a8e2703fa0acbbb63484dfe

New

Hello frameworks and release folks, We had a few major regressions in the 5.100 release that have already been fixed; see: - https://invent.kde.org/frameworks/kconfig/-/merge_requests/148 - https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/652 These are significant enough

Re: New repo in kdereview: KWeather

Really great app. I have just a few minor UX comments, in order of how strongly I feel about them: The main page has no scrollbars, so it's not obvious that the view is scrollable, especially because with various window sizes, nothing looks visibly cut off on the bottom to suggest

Re: New repo in kdereview: KRecorder

Much better! Most issues are fixed now. I feel like we're close. See a few remaining comments: The left pane's placeholder message is off-center with narrow windows. Fixed. I can still see this: https://i.imgur.com/MrrwyAo.jpg On the recording page, the "stop recording" button is red

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,

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

Re: New repo in kdereview: KRecorder

Pretty nice app. The app should have a Bugzilla component and its "Report a bug" button should take users there, as we have been migrating towards for other mobile apps recently. Some UI review now: When I open the app for the first time on the desktop, I get a mobile-specific floating

Re: Plasma Welcome Center on KDEReview

I know about that page, but I haven't memorized every detail of it, or been able to always recall it as the location for the exact piece of information I was looking for. If you have, I'm impressed! Nate On 10/25/22 02:01, Ingo Klöcker wrote: On Montag, 24. Oktober 2022 23:16:50 CEST Nate

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

Re: Plasma Welcome Center on KDEReview

Well that's embarrassing. Looks like my email was slow today, and I just now got the message from Jonathan which even lists the commit that changed it! Thanks everyone. Nate On 10/24/22 11:54, Ben Cooksley wrote: On Tue, Oct 25, 2022 at 4:30 AM Nate Graham <mailto:n...@kde.org>&

Re: Plasma Welcome Center on KDEReview

OK great, thanks! Good to notify people when doing it. :) Where does that YAML file live? Nate On 10/24/22 11:54, Ben Cooksley wrote: On Tue, Oct 25, 2022 at 4:30 AM Nate Graham <mailto:n...@kde.org>> wrote: Since it seems there are no more objections, I'd like to consider

Re: Plasma Welcome Center on KDEReview

Since it seems there are no more objections, I'd like to consider plasma-welcome to have graduated form kdereview. Sysadmins, can we get it moved out of Playground and into Plasma? Nate On 10/21/22 12:19, Nate Graham wrote: Any more concerns or objections? Nate On 10/19/22 11:56, Nate

Re: Plasma Welcome Center on KDEReview

Any more concerns or objections? Nate On 10/19/22 11:56, Nate Graham wrote: On 10/19/22 10:03, Albert Astals Cid wrote: El dimecres, 19 d’octubre de 2022, a les 5:22:09 (CEST), Nate Graham va escriure: Ping; if there are no objections I'd consider it approved. I can't still see

Re: Plasma Welcome Center on KDEReview

On 10/19/22 10:03, Albert Astals Cid wrote: El dimecres, 19 d’octubre de 2022, a les 5:22:09 (CEST), Nate Graham va escriure: Ping; if there are no objections I'd consider it approved. I can't still see the toolbar :/ Thanks to Albert's https://invent.kde.org/plasma/plasma-welcome

Re: Plasma Welcome Center on KDEReview

There have been no additional comments or objections for two weeks; can everything brought up in this thread be considered resolved now? Nate On 9/23/22 23:34, Nate Graham wrote: Thanks for your help, everyone. Fixed now with https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/12

Re: Plasma Welcome Center on KDEReview

, Sep 16, 2022 at 6:00 PM Nate Graham wrote: Hello folks! I've been working with Aleix on an onboarding wizard for Plasma, based on work originally started by Felipe Kinoshita last year. You can see some screenshots at https://invent.kde.org/websites/product-screenshots/-/commit

Re: Plasma Welcome Center on KDEReview

On 9/18/22 11:03, Harald Sitter wrote: Not all code is licensing policy compliant (e.g. appdata is missing spdx tags). I'd suggest enabling the reuse linter pipeline. How do I do this? Is there an example I can copy from elsewhere (which in case people haven't noticed, is basically how I do

Re: Plasma Welcome Center on KDEReview

On 9/19/22 01:42, Ingo Klöcker wrote: Please try to keep in mind that there are people who cannot see screenshots. They may not need captions, but they do need a textual description of the screenshot. That's an excellent point, and thanks for the reminder. Captions added. Nate

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: Plasma Welcome Center on KDEReview

On 9/18/22 11:44, Nicolas Fella wrote: Hi, - I'd suggest to rename the repository to plasma-welcome to be consistent with the internal name and also other Plasma repos Requested with https://phabricator.kde.org/T15840 - The version number in KAboutData says "1.0", this should follow the

Re: Plasma Welcome Center on KDEReview

On 9/17/22 02:16, Albert Astals Cid wrote: Understanding that this is a standalone app and none of its contents are reused to be shown in other apps a KLocalizedString::setApplicationDomain("welcomecenter"); call in its main.cpp will do. Sidenote, given the name of the app is plasma-welcome

Re: Plasma Welcome Center on KDEReview

On 9/16/22 15:46, Nicolas Fella wrote: Am 16.09.22 um 23:40 schrieb Nate Graham: On 9/16/22 15:31, Albert Astals Cid wrote: Those screenshots show me the Wayland icon, please fix. Sure, how do I fix that exactly? Either - Fix the first argument to KAboutData to be the same as the base

Re: Plasma Welcome Center on KDEReview

On 9/16/22 15:31, Albert Astals Cid wrote: Those screenshots show me the Wayland icon, please fix. Sure, how do I fix that exactly? I see the app has a Messages.sh but I remain unconvinced that the generated welcomecenter.po generated file is used. Is there something that needs to be

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

Plasma Welcome Center on KDEReview

Hello folks! I've been working with Aleix on an onboarding wizard for Plasma, based on work originally started by Felipe Kinoshita last year. You can see some screenshots at https://invent.kde.org/websites/product-screenshots/-/commit/e300be66e62263c63d8a85ba391bbcc1de691148. I'd like to

Re: KDE Goal Project specific issue: Automate and systematize internal processes

[Apologies for the delayed reply; your email was erroneously sorted into my spam folder and I missed it until now.] All of these proposals are just proposals. Nothing mandatory, required, or burdened with rules. Just something that overall, would probably improve thing such that I would hope

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

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

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

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

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: Telemetry in Plasma and Discover

/091049.html Aleix On Tue, Jul 12, 2022 at 1:53 AM Nate Graham wrote: Hello all, It's come to my attention that Plasma and Discover implemented support for opt-in-telemetry without complying with the requirements listed at https://community.kde.org/Policies/Telemetry_Policy#Compliance. The Request

Telemetry in Plasma and Discover

Hello all, It's come to my attention that Plasma and Discover implemented support for opt-in-telemetry without complying with the requirements listed at https://community.kde.org/Policies/Telemetry_Policy#Compliance. The Request for review was done solely in a merge request, not also on these

Re: Eloquens now on KDEREVIEW

On 6/21/22 13:24, Harald Sitter wrote: some desktop file validation: (the last point is because SingleMainWindow isn't actually a valid key, you should remove it I guess) org.kde.eloquens.desktop: hint: value "Qt;KDE;Development;Utility;" for key "Categories" in group "Desktop Entry" contains

Re: KF 5.95-rc1 delayed

On 6/9/22 11:18, Nate Graham wrote: Both are merged now. I think that should be everything. ...One more regression was found which is fixed with https://invent.kde.org/frameworks/plasma-framework/-/commit/1fb2198fcee0ec909fed2f1cb6f2d16f27513d57. Can you please add that to the 5.25 tarball

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

  1   2   3   4   5   >