I was just entering a bug and I noticed a lack of clarity. While selecting Plasma panel taskmanager it asked for a version number. There was none availble that I could find, so I just entered the KDE version number. I also wish that the selection of components was a drill-down method instead of a list of unknown and unclear selections. Thanks.
Please explain or indicate which page you were using. On https://bugs.kde.org/enter_bug.cgi?product=plasma&format=guided I see a quite clear selectable list of versions for Plasma.
On my desktop!!!!
Please provide a screenshot of the web page or application you are seeing.
Created attachment 76757 [details] The Desktop!!!!! As requested, the screen I am seeing when I look for the Plasma version number. It just ain't there.
Created attachment 76758 [details] Web Site screen To clarify, this is the page regarding the bug category selection problem.
There are relatively few people in the world who understand the odd names for items in the list on the bug reporting web page. The descriptions understandable to only the insider and do not include all the surrounding parts of the component. Again, there should be a drill-down method that accepts the actual user name for items on the desktop. If it has to do with a widget on the panel, one should type widget, then panel and be given the correct category. Simple.
(In reply to comment #6) > There are relatively few people in the world who understand the odd names > for items in the list on the bug reporting web page. The descriptions > understandable to only the insider and do not include all the surrounding > parts of the component. No, bugs.kde.org receives around 350~400 reports per week, and most of them are created by users, not developers.
It would seem extremely narrow-minded to assume that most users understand the explanations given for each odd name.
(In reply to comment #8) > It would seem extremely narrow-minded to assume that most users understand > the explanations given for each odd name. I 'm no saying "most users understand" , I 'm just saying your assumption/statement "The descriptions understandable to only the insider" is wrong. That is it.
The insider would be the ones who know the precise meanings of the names. Very few know that for sure. Therefore, there is work to be done. That this requires a serious attempt at making it clear for all users, goes without saying. Someone should be working on that part, and making darn sure it is absolutely goof-proof. Talking about it solves nothing. Action makes all the difference. Instead of complaining about a differnce of opinion, you could better spend your time with the solution. As always, should you or anyone need direction on how to fix it, I only need to be asked.
Jekyll Wu is full of action. Please pick a nicer tone of voice to talk to him. We have seen your bugreport and will act on it later. Thanks for reporting it.
Tom, why was Jekyll commenting? I thought Ben was taking this one. Further, his comment: "No, bugs.kde.org receives around 350~400 reports per week, and most of them are created by users, not developers." makes no sense. Perhaps you could consider his non-sequitor before commenting so negatively. And, maybe, change your tone. Any job worth doing is worth doing well. You have nothing to defend yet.
Everybody is free to comment on this bug, no single one picked it yet, it is a sysadmin groups bug, as one can see. Jekyll's comment was supposed to show that not just a few users are able to submit a bug even without a fix for this problem. Speaking of that, Tom made it already quite clear enough how we can act on this bug, so there was no further comment needed, and neither did it add any value. Maybe we find a solution or not. But most likely not with a discussion about who sounds more negative.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
(In reply to tech from comment #6) > [...] > > Again, there should be a drill-down method that accepts the actual user name > for items on the desktop. If it has to do with a widget on the panel, one > should type widget, then panel and be given the correct category. I am sorry but can you clarify that last sentence? Provide an example?
(In reply to Jekyll Wu from comment #7) > (In reply to comment #6) > > There are relatively few people in the world who understand the odd names > > for items in the list on the bug reporting web page. The descriptions > > understandable to only the insider and do not include all the surrounding > > parts of the component. > > No, bugs.kde.org receives around 350~400 reports per week, and most of them > are created by users, not developers. That possibly proves that maybe 200 people report to bugs.kde.org every week, which is probably less than the number of people who maintain(ed) KDE products. And anyone who reports *is* a developer. I believe the description of some products is good, but I would easily agree with the reporter if he merely claimed that many (maybe most) are understandable only to few people. Just in the screenshot he provided, we see Akonadi described as a "PIM framework". I don't think 1% of computer users could define PIM, and most professional software developers would say they've never even seen that acronym. I think most of the descriptions can be improved, but in reality, even if we were to craft the best 1-line description for each item, it would still be hard for someone who's used KDE for years without getting involved in development to understand what a large part of these products are about. Ultimately, this comes down to the fact that, to put it simply, "KDE is complicated". We could still do a lot better if we wanted, linking each product to its homepage. Reporter, on which URL did you take the "Web Site screen" (screen.png) screenshot?
Reporter, you described several issues in this ticket. You described issues indicating the product affected, and an issue identifying the version affected. Thank you for reporting these, but doing that in a single ticket makes your requests harder to understand and can cause confusion. In the future, please open different tickets to report different issues (this ticket should have been at least 2). VERSION IDENTIFICATION Are you still affected by the version identification issue? If so, please file a new ticket specifically on this issue, indicating the operating system which you use. Please also attach a screenshot of the problematic screen; I'm afraid the "Desktop" screenshot you attached is not a screenshot of the right screen (it basically only shows a picture of a river). PRODUCT INDICATION The "drill-down" aspect is under discussion in ticket #360400. If you have specific advice on that aspect, please provide it there. The clarity aspect is more complicated. You may open a new ticket asking product descriptions to be clarified, but do not be surprised if someone requests examples. And if you provide examples, do not be surprised if the ticket is marked as resolved as soon as these examples are solved.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!