> We usually recommend contributors to create branches in the main repository
> (work/gsoc/...). Is it possible without a developer account?
>
> Johnny
It doesn't have to be the GSoc student that creates the branches, only that
they are the ones putting commits in it. Something I've seen done is
Welcome back to KDE! Yes, involving yourself in bug reports is in my opinion
the best way to get started, especially if you want to orient yourself with
the gargantuan codebase of KDE.
> I'd also be interested in having something like the mouse button mapping UIs
> that Windows users get from th
> Hello,
>
> I have created a libmpv wrapper library for qtquick/qml (no widgets)
> https://invent.kde.org/georgefb/mpvqt.
>
> I created it mostly because I use mpv in Haruna and other personal projects
> and keeping the code in sync got annoying. There are also other kde
> projects
> using mpv (
Hey Loren,
I agree with everyone else that as long as the model is ethically sourced and
local-by-default (which is my two main problems with modern LLMs.) I see no
qualms about including such a frontend in KDE.
I think the hardest part will be the marketing around this new software. One
of ou
Hey Nate, thanks for formalizing this discussion 🙂
Maybe you should give some examples of "internal communication" topics here
too, because it might not be clear to everyone.
I'm also curious about the implications of mirroring such topics to
discuss.kde.org and other "user support" type of pla
Hi Carl,
> Adding a new channel that is either a mailing list, rss feed or a forum
> category won't help and will probably only makes it worse. It's also very
> difficult to defines that is an important internal news for the whole
> community is as it will be different for every subproject in KDE.
> Hello,
>
> What do you think about https://github.com/RazrFalcon/resvg in case of
> processing and rendering SVGs?
In case anyone hasn't seen this before, Harald has already tried integrating
resvg with Plasma: https://kde.haraldsitter.eu/posts/resvg-for-svgs-in-qt/
Josh
> Hi!
>
> Arjen Hiemstra and me have been working on a RDP server called KRDP.
> This allows remote desktop connections over RDP protocol. Arjen
> did the heavy lifting with the streaming side and the actual protocol side.
>
> https://invent.kde.org/plasma/krdp
I'm not knowledgeable about RDP st
> Hi,
>
> +1 in general. The documentation particularly for Kirigami and QML stuff
> is quite sad.
>
> Does the switch to qdoc mean we have to write documentation in the _cpp_
> file, though? That would be unfortunate.
>
No, see his patch at the bottom of the e-mail. Hopefully that won't be the
On Thursday, August 8, 2024 9:06:03 AM EDT Nicolas Fella wrote:
> Hi,
>
> TL;DR: Call KCrash::initialize() after setting up KAboutData
>
> crash reporting via DrKonqi to Bugzilla and Sentry is powered by the
> KCrash framework, which acts as the crash handler inside the application.
>
> To insta
On Friday, August 9, 2024 11:54:39 AM EDT Joshua Goins wrote:
> Thanks for posting this to the ML Nico. I'm wondering since 24.08 is close
> to releasing I want to get KCrash in for some of my applications. We're
> past dependency freeze, though. Assuming I do the usual
On Tuesday, December 24, 2024 4:00:54 AM Eastern Standard Time Albert Astals
Cid wrote:
> tokodon - NEW
> * https://invent.kde.org/network/tokodon/-/pipelines/848675
> * flatpak build fails
I fixed this recently and now the Tokodon master CI is all green.
Josh
On Tuesday, January 28, 2025 5:27:15 PM Eastern Standard Time Albert Astals
Cid wrote:
> neochat - 2nd week
> * https://invent.kde.org/network/neochat/-/pipelines/874963
> * flatpak build fails
This is now fixed, along with neochat master which was failing due to an
outdated kquickimageeditor
On Tuesday, December 17, 2024 6:05:46 PM Eastern Standard Time Albert Astals
Cid wrote:
> kunifiedpush - 3rd week
> * https://invent.kde.org/libraries/kunifiedpush/-/pipelines/834459
> * connectortest fails on freebsd
I looked into this tonight, and from what I can tell this is some unknown
b
14 matches
Mail list logo
