Joerg Barfurth wrote:
Of course the problem is how to teach people the rules for handling issues that don't understand the underlying developement process without scaring them away from submitting issues at all.
I've been experimenting with using server-side programs to *guide* users towards making useful bug reports:
http://website.openoffice.org/tryouts/dcarrera/miniZilla/
The advantage I see of this is that you can see it without having to login.
But if you login to the OOo website and go to http://qa.openoffice.org/issues/enter_bug.cgi?component=%2ATestproduct there is not much difference between the current form and minizilla
The trickiest bits and the most enquiries that come to webmasters are wrt to logging in and choosing the relevant component. How is this addressed in minizilla?
All the best Jacqueline McNally Lead, OpenOffice.org Marketing Project
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
