119
We are looking for a new set of Community KDE Goals to work on.
(cdn.masto.host)
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/
@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.