What I believe the OE/OZ developers want us to do is:
if you think it might be a bug report it to the tracker.
If you think it might be a bug, but it might not be a bug, report it to the tracker.
If you think it might be a bug, reported it to the tracker, but discovered later that it wasn't a bug - report THAT CONDITION to the tracker.
Raduga: I cannot say that better
When bug is reported then OE developers are noticed and can look at it (only subset of them use OESF forum).
If bug is already solved we close it (you got info by mail).
If bug was already reported we mark it as duplicate (you got info by mail).
When bug will be resolved we will close it (you will... yes - you will get info by mail). then you check does it really fixed for you and if not then you reopen it (and we will get info by mail).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128446\"][{POST_SNAPBACK}][/a][/div]
I have observed that some users find it frustrating, that the OZ/OE developers want discussion of problems to be focused in a place designed for bug-repairing,
rather than a place for general chitchat, like the forums or IRC.
What might be helpful to users who do find it frustrating (including sometimes myself) would be to remember that OpenZaurus releases, in general, are works in progress-
and this work is
vitally dependent on people reporting bugs, and having those bugs fixed.
Meaning... if you use it, you ought to consider yourself part of the quality assurance/beta test group, and if you gain any value from using the software,
you should report your experiences, as they are, to the core developers.
If you don't want the burden of responsibility for helping fix OpenZaurus,
it might be better not to use it; at least, until a stable release is out.
I still send out "feelers" to devs outside the tracker, when I suspect something is a bug, but am not sure; but its becoming more and more clear that
proper reporting is an ethical necessity.
thanks - everyone
