Re: What can we expect from our developers
On 1/2/24 20:04, Jonathan Riddell wrote: My opinion is that KDE project maintainers should aspire to get the projects into the hands of users in a way which makes it a useful tool for the user. That means ensuring the projects are packaged and distributed and updated. That's a big ask of course especially from volunteers but it would be the same of self hosted open source projects on Github or commercial proprietary projects, the difference is we have a community process where if you aren't sure how to achieve something there is probably other people who can help out. When I first took over Umbrello 20 years ago I was surprised that as well as learning C++ and Qt I'd also need to know some artwork and how to make it translatable and follow UI design. Actually making it available to users through app stores is another ask for sure but it's why I'd like that integrated into processes like the KDE Gear release service so projects can offload some of the work. There seems to be minimal interest in this though which I worry keeps KDE projects back. Jonathan Also if you'd like your app build as a Flatpak in CI or on Flathub please don't hesitate to ping us in the Matrix channel: #flatpak:kde.org
KDE Review OptiImage
Hi, After writing the initial commit back in 2021 and several rewrite (hello Rust, goodbye Rust ), I finally finished working on a new app: OptiImage. It's a GUI wrapper for a few tools: oxipng, jpegoptin, scour, cwebp to compress images. It's relatively basic and inspired by the following GNOME app: https://apps.gnome.org/Curtail/ Here is the issue to track the kde review https://invent.kde.org/graphics/optiimage/-/issues/2 I already fill all the trivial checkbox: e.g. CI running and reuse conformance. Clazy is unfortunately not working due to the lack of compiler support for coroutines in clazy. Cheers, Carl
Re: What can we expect from our developers
My opinion is that KDE project maintainers should aspire to get the projects into the hands of users in a way which makes it a useful tool for the user. That means ensuring the projects are packaged and distributed and updated. That's a big ask of course especially from volunteers but it would be the same of self hosted open source projects on Github or commercial proprietary projects, the difference is we have a community process where if you aren't sure how to achieve something there is probably other people who can help out. When I first took over Umbrello 20 years ago I was surprised that as well as learning C++ and Qt I'd also need to know some artwork and how to make it translatable and follow UI design. Actually making it available to users through app stores is another ask for sure but it's why I'd like that integrated into processes like the KDE Gear release service so projects can offload some of the work. There seems to be minimal interest in this though which I worry keeps KDE projects back. Jonathan
