https://bugs.kde.org/show_bug.cgi?id=402789
--- Comment #12 from Claudius Ellsel <claudius.ell...@live.de> --- (In reply to Nate Graham from comment #10) > I remember being where you are right now, Claudius. You want to have an > impact on big things, but none of the channels of communication available to > you as a user seem adequate for this. The solution is to step up and become > a contributor! Join the mailing lists, get on IRC, start triaging existing > bugs, submit some patches, etc. If you want your voice to have the kind of > impact it seems you're looking for, you gotta start contributing first. > Trust me, it works. ;) > > https://community.kde.org/Get_Involved Also sorry to you Nate that it took me so long for a reply. I had this in mind several times, but never got to it. Basically I want to improve KDE. I'd like to contribute (in my scope), I already opened issues, what I also consider a contribution. However, the current workflow is not really what I am used to. I don't really like mailing lists (as written above) and Bugzilla. They don't seem very efficient or easy to use to me. I really appreciate that you continued moving more stuff to GitLab. I hope the issue tracker will follow (and be merged with the current Phabricator replacement, so issues are not divided between developer and user scope). Then I might do some issue triaging which I currently find unattractive due to the usage of the rather unintuitive Bugzilla. > If you want your voice to have the kind of > impact it seems you're looking for, you gotta start contributing first. I hope also good arguments alone can have an impact :D -- You are receiving this mail because: You are watching all bug changes.
