To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53861
------- Additional comments from [EMAIL PROTECTED] Wed Apr 11 15:50:15 +0000 2007 ------- Opionion: To ooo staff/Sun Microsystems, system architect ESC and all users: There have been calls for a more user friendly method of reporting bugs or issues:(issue 63325 and 55306, and 16926 are examples). The attitude of dealing with the "tsunami of bugs" (see issue 63325), seems to reflect the fact that the bug/issue reporting system is badly in need of a fix. Resolving and weeding out the influx of bugs, should be accommodated by Sun, supporting higher level tool to properly manage the project. I would recommend that ooo should institute a formal feedback poll to truely understand the frustration of the user/developer community (at all technical levels), as to the inadequacy of the current bug/issue reporting and query system. Few people want to take the time to look up and thus properly use the cryptic field values; The modality of the forms are at best archaic and confusing to even experienced, but non ooo specific developers. Addressing these needs at a higher than individual developer level, would proove support of the endorsing sponsor. It would free developers to deal with issues at their level more efficiently, and improve the flow of information from the end users by inhibiting the ill-conceived "Barrier" mentality. Users WANT to contribute, and make a better product. However, as in the case of issue 16926 and others that I have seen but not cited, most will simply throw up their hands at the pathetic state of trying to submit help, suggestions, and features. There are several levels of need. As noted in this and other reports, the ability to integrate issue feedback into the Help menu, into the ooo Help system, and into context sensitive or error dialogs, would all be noteworthy features, to help mitigate errors, and to be more user friendly. Above I mentioned internal project tools, to allow developers and architects to consider all feedback in proper perspective, and to help inter-relate cross entity issues, which would more rapidly leverage the overall suite progression. By ignoring or attempting to mute end-user input, you are loosing your most important perspectives, and consumer driven needs. All other industries have learned to benefit from direct consumer feedback, why not ooo? I respect the individual developers, and see them benefiting as much from the recommended changes, as the end users... after all this is supposed to be a collaborative effor, is it not. Respectfully, sRiffle --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
