6 May
2011
6 May
'11
11:06 a.m.
Okay guys...
Enough of it, not need to give such an image of the ReactOS project.
Victor, you've already been said several times (and not from Olaf only) that some of
your bug reports were lacking consistency, details, interest, whatever. Or even some of
your answers (let's think about bug #5657).
So now, it may be understandable that such a bug report which is not that good produces
such reaction.
Talking for me, and for me only, I would be assigned this bug, I would close it
immediately. Not enough material, nothing really concrete. Typically, that's kind of
stuff it's better to discuss with developers instead of writing a bug report. It's
a really specific issue, without any debug output, and with source available. Be sure
developer will do their own tests to get more information and the report won't be that
useful.
The idea of a bug report is to point the issue to the developers without *that much*
investigations. Here, all the stuff is to be done. That's why a bug report seems not
to be appropriate in the way it doesn't bring anything more than just: "Oops, it
doesn't work".
Finally, try to keep the mailing-list out of personal conflicts and childish stuff.
It's not its purpose. Just insulting each other won't help the project in any way.
If you know you are tempted to overreact, then, take a deep breath, go outside and finally
write answer when you are back and cool.
We are currently in Google Summer of Code period for the ReactOS project. Many new comers
eyes are watching us and I definitely don't think that's a good idea to offer them
such show.
Show instead how both you are involved in the project by posting nice mails, doing great
job, offering beers to students (and eventually helping them).
Regards,
P. Schweitzer