On Tue, Mar 28, Joe Salmeri wrote:
On 3/27/23 02:31, Thorsten Kukuk wrote:
It is really a bad idea to add many random people who have nothing to do with the problem, but not including the one for which this bug is relevant.
The correct way to handle it: assign it to KDE, because it looks like a sddm configuration problem.
I did NOT add random people to the bug.
You did, and I can prove that, since you added me ;)
Since it was a problem with a PAM configuration file, I ran osc to find out who the PAM people were and I added those people to the bug.
Again, your list did contain many random peole who have nothing to do with PAM anymore, maybe in the past. What you wanted to achieve is, that somebody is looking at your bug with high priority immeaditly. But with your action, what you have achieved, is more people get more for them useless bug reports and as result more people ignore bugzilla notifications. So exactly the opposite of what you wanted to achieve.
How exactly is the typical end user supposed to determine that KDE was the correct component ?
You had this problem with KDE, so you select KDE.
A LARGE percentage of the time when submitting bug reports, the component or area that I want to assign a bug to is NOT in the list.
That's why there are components like "Basesystem", "other", or "KDE".
Everyone is NOT intimately familiar with every piece of software to know which items belong in the various categories when they are NOT in the component list.
Absolut correct. And why do you then add random people if you don't know if they are responsible?
I'll bet a large number of bug reports submitted are NOT anywhere near as detailed OR clear as the bug report I submitted.
This has nothing to do with adding random people to bug reports.
Most developers would be extremely grateful if all the bug reports they received were as well written and debugged as what I submitted.
This has nothing to do with adding random people to bug reports.
What is the best method for making sure the correct people are notified about the bug? Not by adding random people to that bug :(
Create a bug, select the _correct_ _component_ (so KDE) and let the people do their job.
About your bug: you added 7 people and a mailing list, but the relevant people are still missing...
Providing misleading statements indicating that I just added random people to the bug is also NOT a very good method for addressing a bug.
But you did add random people to the bug! The statement is not misleading. How can you claim that you did not add random people to the bug if the people you add tell you the opposite?
The logic for why I added those people is quite easy to follow and understand why I came to the conclusion that they were the best ones to notify.
And I tell you that your logic was wrong.
So instead of LYING and saying I added random people and completely IGNORING why they were really added, how about providing useful information, like how to determine what component to assign a bug to when you don't see the component in the list of available options?
I'm not LYING! Calm down, read again and think about what you did! Doing a mistake and then claiming that the people making you aware of that mistake are lying is really very, very bad habit!!!
Now THAT would be REAL USEFUL!
Don't make wrong assumptions and assign it to the wrong components. That's the best way to make sure that the correct people will NEVER see this bug.
Are you this RUDE and disrespectful to everyone you respond to because I have CERTAINLY noticed a pattern over the years.
Maybe people would do a better job of assigning bug reports to the correct component if you actually HELPED them instead of being so combative
We are not speaking about compontents, but that you did add random people to a bug report! Don't always try to distract from your mistake! Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)