On Fri, May 16, 2014 at 5:06 AM, Tal Daniel <tal.re...@gmail.com> wrote: > +1 for Adding a "Report a bug/issue" link, that will open Bugzilla/issues > site. > > Making it easier for people to reports bugs conveys an implicit message of > "we want your feedback". >
Here's the challenge: What happens when we make it easy for 100 million people to enter bug reports? We have some sense of that when we had a prominent link to reporting problems with the website on the footer of every page. What we saw was many emails a day to that address, asking support questions about OpenOffice. They were not reporting bugs, but asking functional "how to questions". So the challenge is how to make it easier to report bugs, and at the same time not suggest that this is an avenue for getting support questions answered. Even if 1% of users are confused by this, multiply by many millions of users, and you have a big mess. Because of this we made some bug reporting information harder to find, so a casual user would not accidentally go down the wrong path. I don't know of any perfect solution here, but maybe we could have two paths: 1) One project participants and other technically savvy folks, who can be expected to know what a defect report is and how to write one. Remove the hassles for them to enter a defect report. 2) Everyone else should be encouraged to go to the forums. Most times it is a functional question or a known issue. Bugzilla is not a kind tool for either of those cases. So use the forums for that. But then have a *one-button solution* for transferring information from a forum post to Bugzilla, something that the forum moderators can use. So with a single click open up a new draft Bugzilla issue, copying the information and attachments from the forum post. -Rob > Brennan, did you file your idea as an enhancemet request? > > Tal > > > On Thu, May 8, 2014 at 5:55 PM, Brennan Novak <h...@brennannovak.com> wrote: > >> Hello OpenOffice Team, >> >> My name is Brennan. I am a user experience designer & engineer, I am >> currently building the FOSS crypto-webmail project Mailpile... perhaps you >> have heard of it :) >> >> Here is a link explaining the current user experience flow which I >> experienced as a major pain point this morning trying to file my first >> OpenOffice bug report: >> >> https://brennannovak.com/notes/432 >> >> I believe my initial bug is quite valid and should be fixed. But, I also >> believe that it is equally valid to improve the user experience of >> reporting bugs themselves- the 10 step process I found myself in was a >> quagmire that I almost gave up on, but I resolved when I started working on >> Mailpile to be better member of the FOSS community and to strive to report >> UX bugs by giving other FOSS projects more patience, empathy, and effort to >> help them improve! >> >> I realize that making it easier to file bugs will probably increase your >> volume of bugs filed (certainly a mixed blessing), and that this will >> require more filtering & diligence from your team to weed through them. I >> am completely unaware of what resources OO has and how feasible this, but >> it seems fortuitous to improve things a bit from the current state. >> >> I have numerous other improvement ideas I have encountered in the setup >> and updating flows of OpenOffice and would be willing to share them, so >> long as it is helpful to your team! >> >> Sincerely, >> Brennan Novak >> Mailpile - taking email back! >> https://mailpile.is >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > > -- > טל --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
