KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
We are looking for a new set of Community KDE Goals to work on.
What should KDE focus on over the next two years? Are you ready to share your vision, time and stamina to push KDE to the next level?
Let's evolve KDE together! Find out more here: https://blog.lydiapintscher.de/2024/06/05/what-should-kde-focus-on-for-the-next-2-years-you-can-propose-a-goal/
@kde@floss.social
I know ✋I know ✋ there is already a lengthy list:
https://bugs.kde.org/describecomponents.cgi
@kde@lemmy.kde.social
Those are bugs. Not community-wide projects.
@Bro666
Those are bugs reports and feature requests for all KDE applications including plasma and also including Kate, Yakuake, Konsole, Kmail, rkward ...
Not complaining here, but none of the bugs I ever reported or I'm following were addressed. To me this sounds like a good place to focus on, because these are issues that the community have faced or the suggestions they have come up with.
Bugs are solved all the time. It is not a project for the community because the community already works on correcting bugs all the time. If the correction of bugs is not fast enough for you, we cordially and officially invite you to help out:
https://community.kde.org/Get_Involved
Remember: bugs are corrected by volunteers, many of which also have day jobs and other things going on. We are always understaffed. You can help.
@Bro666
Thanks for your invitation, then I cordially and officially invite you accept the KDE Invent (Gitlab) access which I requested months and months ago.
It is not right to randomly throw such messages and accuse people of not contributing when the contribution is locked behind a login screen that needs approval and the access is never given. I mean you can, but it is, unethical and unfriendly.
For now all I could contribute is by donating money (check the records, it's public).
@kde
A developer account, the kind of account that gives contributors full access to GitLab, gives the power to do a lot of damage too. In view of how malware has been injected into FLOSS projects in the past, you will understand why KDE's Invent instance is not an open, free-for-all affaire.
You have to go through a process, wherein one of the steps entails being sponsored by someone who is already a veteran contributor to KDE. This, in turn, entails contributing to KDE for a while, maybe in a non-development role, or by using the open services of invent. If you have not gone through that process, the sysadmin team will ignore your petition.
That said, properly submitted requests for developer accounts are approved all the time.
See here on how to proceed:
https://community.kde.org/Infrastructure/Get_a_Developer_Account
Notwithstanding, when it comes to bugs, which seems to be your main concern, there is a lot you can do without a developer account. Triaging, for example, wherein you confirm that a bug exists, check if it happens everywhere (i.e. across platforms and distros), and figure out what triggers it is an invaluable contribution that will save developers many hours of hunting and testing.
Why not start there? All you need is an account on https://bugs.kde.org and you will also revive bugs that may have flown under the radar and contribute to getting them sorted once and for all. Your help could be key to that.
And that is much appreciated too. Thanks
@Bro666
I sense some hostility here which I don't appreciate.
>> A developer account, the kind of account that gives contributors full access to GitLab, gives the power to do a lot of damage too.
That sounds very wrong. All PRs (in case of Gitlab MRs) should be ultimately approved, so I cannot see why your Gitlab is vulnerable where as all other instances of Gitlab, the Github and all instances of Forgejo are nor susceptible these "damages"!
🧵 👇🏼
🧵 👆🏼
@Bro666
>> developer accounts are approved all the time.
Not mine! So "all the time" is as false as it gets. No one communicated to me that I need to provide certain information or details!! pure radio silence. So let's be factual.
>> when it comes to bugs, which seems to be your main concern, there is a lot you can do without a developer account.
Bugs **and** feature requests are my main concern.
🧵 👇🏼
🧵 👆🏼
@Bro666
>> Why not start there? All you need is an account on bugs.kde.org and you will also revive bugs that may have flown under the radar and contribute to getting them sorted once and for all.
As mentioned before, I have already done that. it is all public information and you can go and check.
It seems that whatever I say is taken the wrong way, so i'll leave it here.
Have a nice day.