On Monday 08 December 2014 05.00:10 Carlos E. R. wrote:
On 2014-12-07 18:21, Bruno Friedmann wrote:
On Sunday 07 December 2014 15.01:02 Carlos E. R. wrote:
You never live the case as bugowner you ask information to user and never never get it :-)
Oh, I do. I "own" very few bugs, but I do ;-) I contribute as translator.
I have bugs opened for years. Eventually, somebody comes and just closes them saying that the openSUSE version I reported against does not exist, and please try on a new version - without anybody ever doing anything about the bug. I doubt the person closing it even reads it, maybe it is a script doing the closing.
Find friends, and organize a bug squashing to confirm each bug open and also participate to the next bug squash day organized.
Pointless.
Those pesky bugs do not need extra confirmation, there are logs with detailed and hard to obtain information, requiring things like modifying the kernel, maybe place video cameras or hook a second computer to capture kernel messages over a serial port...
It just needs a developer to get inside and code, or ask pertinent questions, provide patches that I can install and test and give further info. I have done everything possible from my side.
How can dev fix a problem that can't be reproduced ... That's why adding people with same trouble or similar can really improve the situation
Others are quite evident from the bug report and do not need anybody else confirming that they also get it. Specially if the logs says: this is a bug, please report me.
Finding friends looks to me "political lobbying". It is corruption. It is out of place in engineering and science, IMNSHO. If it is a bug, it is a bug, period. Perhaps a crate of beer will help to solve my bugs, leaving other people bugs unsolved? >:-)
Some of these bugs took me days, even weeks, to try collect the data.
Some of these automatically closed bugs are still present on the new releases (sometimes obviously so), so I reopen them. And they often are eventually closed again without activity on the next release.
Quality of the report, wrong product ?
Nope.
If it were, the bugowners/asignees/whatever could simply ask for clarification. I'm well known, I believe. I can make mistakes, I'm human, but every report I write has a lot of effort and care behind. They can be mistaken, but I do my best so that they are good quality.
Then perhaps a list of concerned bugs would help to understand the why and what.
It is very discouraging. So each time I report less and less.
There's something you could do, find who make changes in the rpm changelog located the package on obs, use "users" tab and pick email of bugowner / maintainers try to add them in cc list
Not my job.
I'm not going to install obs in order to find the maintainer. It is a large package and needs an account, and some reading documents.
The only thing you need is a web browser and you openSUSE login. Nothing more, nothing less.
That's the screening or triage team job, not users job. Guess who is triage/screening team : you and me and others its not only "their" responsibility.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org