On Mar 15, 2005, at 22:36, Tamblyne wrote:
Gene Heskett wrote:
On Monday 14 March 2005 02:00, Naomi Kramer wrote:
Gene...
Huh?
Am I understanding your complaint correctly - that you need to
create an account on the openoffice.org site, and login under that
account name, before filing a bug? It seems fair enough to me -
maybe I'm missing something though?
- Naomi
PS. Most of the people on this Users list are NOT programmers -
they're simply users of the software.
I got the impression from the wording of the 'open an account' page
that I was expected to be a developer. I am not. I look at myself
more as the canary in the coal mine, trying to alert folks to a
problem. If, in Suns infinite wisdom, they don't want to see bug
reports, then they've successfully made their point.
I personally would like to see it succeed, by either name, blowing
M$Office out of both the enterprise and at home just because I'm not
an M$ fan. But IMO, blocking the common user from filing a bug
report is not in your best interests in the long run. If thats not
how I was supposed to interpret that, then please feel free to
correct me, and I'l go register (I thought I did that when it was
installed and I chose the register now option because I'm on DSL) and
file a proper bug report.
[...]
Hello, Gene --
I don't know if anyone's mentioned this to you yet, and even if they
have, I believe it's worth mentioning again --
One of the reasons for asking people to register with the site (which
is not the same as registering OOo, which is basically for
marketing/statistical purposes and does not involve personal
information) is to make sure there is further contact information
available in the event it's needed to help verify and correct the
problem.
When you file a bug report, you are copied on all activity on that
issue as the original reporter. Should further information be
required, requiring registration helps insure that the reporter will
actually be made aware that more information or clarification is
needed.
Nothing is done with an issue until it can be verified and reproduced
-- and many issues languish or are closed because they cannot be
reproduced and needed information is not forthcoming.
All of the triage work is done by volunteers, also, so it would be
nice if you would keep that in mind in the event you find you have the
time, patience and resources to file an issue about your problem.
Tam
Just wishing here, but it would sure be nice if OOo had a toolbar
button for reporting bugs, similar to what Apple uses on Safari. User
registration/verification information could be transmitted to eliminate
spammers automatically. The bug reporting module could dump registers,
stacks, and the last few menu items or commands issued by the user. It
might also copy the console log, if it's relevant. Might simplify
tracking down whether the problem was caused by OOo or the OS. If it
could keep track of where the program is operating, then manual sorting
and prioritizing of bugs could be seriously reduced.
Wish I had the smarts to code that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
