I’m working on a very KDE-focused project called Operese, which is a tool to automatically migrate computers from Windows 10 to Kubuntu (or hopefully eventually any KDE distro). It’s open-source on Codeberg (link) under the AGPLv3.
Operese has to do quite a bit of automated configuration in the process of migrating everything over from Windows, and I’d like to know what the best way to go about that is.
For example, the janky solution currently being used for wallpapers is to create a systemd service which runs plasma-apply-wallpaperimage when first logging in, since to my knowledge such Plasma scripts can only be used when the user D-Bus session is active. I’d rather use something more flexible like kwriteconfig, but I’m not sure whether there’s any documentation and/or stability guarantees for the relevant configuration values.
And the second thing is that, although it’s been open-source for about 5 months now, I remain the only contributor. I’d really love to change that as I start working towards new features like UEFI support, localization, and many more. So, if you’d have any interest in:
Development
UI design
Logo design
My abominable temporary logo has been there for the better part of a year…
Or really anything else!
there’s a Zulip chat you can join and I would be very excited to collaborate with you (link) With that being said, I realize most of the people reading this are already very busy, and I don’t want to shamelessly ask you to become even busier.
Some time ago I read about your project and loved the idea.
I am not a developer, but I would like to help with localization. Does it have .po files or a Weblate / Codeberg Translate page?
Also currently KDE is making it’s own operating system, KDE Linux. They had an idea about an “Upgrade to KDE Linux” tool, and looks like if Operese in the future supports distros other than Kubuntu, Operese could be a great solution.
This might also be something that could integrate with Plasma Setup
Some of the things it sets up are likely part of the settings you are transferring from Windows.
Having that said: while a number of developers are visiting the forum, it might be faster to check on one of the Matrix channels, e.g. the one for Plasma Desktop development
I had actually commented on that issue a while back to see about collaborating, and it sounds like the KDE Linux team would be interested in that sort of thing, which would be fantastic.
Amazing, that would be super helpful. Although I will warn you that the UI text might be changing quite a bit before any sort of release, it is set up for localization already using Fluent (.ftl). Would it be beneficial for you if I were to set up a Codeberg Translate project, or are you comfortable editing the files directly?
Excellent call on both counts, thanks! I was only vaguely aware of Plasma Setup, but upon looking more closely, it seems quite well suited for my purposes.
It would be nice because Lokalize doesn’t support Fluent files.
The Fluent localization format is new to me, but it doesn’t seem too complicated (I have experience with .po, .json and .yaml), so I could probably edit it manually.
I’ve created a Weblate project for Operese on Codeberg Translate (KDE Discuss doesn’t seem to like me putting a link here)
I don’t think I’ve quite set it up correctly, as the test French translations I’ve added are missing quite a few strings. But we can probably move the localization conversation to Zulip, and see if it works for your native language
With that being said, I realize most of the people reading this are already very busy, and I don’t want to shamelessly ask you to become even busier.
