chofmann wrote:We do love you, and I definitely want to go thought all the suggestions here, figure out what is possible, and organize into a plan that we can start to act on. There is a lot to do so I'm hoping that folks can be patient.
Thanks for all the great thinking and responses that have come on this thread over the last several weeks.
A few of us at Mozilla have final carved out some time to dedicate to this important issue. In the next couple of weeks we will be settting up conference call for interested participants to dial in and get some live discussions going on building out a task list of action items, setting some priorities on the list, and getting some dedicated resources engaged in working on the list of improvements. We also will be setting up a newsgroup with e-mail and google group access where all the folks interested in participating and following along with the the progress of improvements can get engaged.
Watch for those announcements in the next few days.
I've also put together a recap of all the great observations and ideas that have been posted in the last weeks and months to start off this next round of discussion and action... If you see any addtions or improvements to this recap please feel free to pitch in.
--------------------------------------------------------------------------------------------------
Support problem summary from the Mozillazine Forum
---
-MediaWiki - KB (content shared across all mozilla software confuses firefox-only users)
--article can be overwhelming for this and many more reasons... articles not target at novice end users
--improvments needed in the way disputes are handled.
http://kb.mozillazine.org/Knowledge_Base_changes
--mozillazine can't handling UA sniffing as a strategy for helping to direct users at relevant content
-phpBB forum(s) mozillazine -- main and back channels
--Volume/Scalabilty problems
--- forum posting now roll-off the main page before questions can be answered. its not scaling well
--site goes down/becomes slow at peak download times when new users are in most need of info
--no good way of duping or leading users to info on their topic (better search?)
--lack of strategy and sticky issues around handling "guest posts" and user registration
-IRC channel #firefox, others...
--(no web-based chat solution incurs download cost., communication cross talk problems
-newsgroups
-end user documentation
-end user help
-I'm sure I'm missing others...
-lack of cross over and communication between volunteers acting in each area
--no regular meetings to roll up and discuss common issues and develop strategies for key problems
-No *Mozilla* hosted central support repository, contributed to by all the different branches of user support, as well as bugzilla triagers
-All these problem mutliply across all 40+ locales where firefox is shipping.. each locale is left to deal with support and support infrastructure on their own.
Missing pieces to the support equation and support feedback mechanism..
-no continuing data analysis to prioritize navigation most visable problems
--need data on frequency of problems and links quick survey to findout about the usefulness of solutions. (was this page useful?)
-need to figure out other possible metrics
1. What fraction of problems on forums/irc/newsgroups are successfully resolved?
2. Are some kinds of problems resolved more/less frequently?
3. Do some resources provide solutions more/less often?
4. Do successful solutions depend on other factors? Completeness/accuracy of initial problem descriptions (if so, we could provide a form)? Native language (or are we only concerned with English here)? Time of day (if so, we could adjust resources or inform the user)? A combination of factors (e.g., maybe IRC is a better place to go with networking issues)? Something else?
-no systematic trainning for helpers (Quick, easy, basic training in troubleshooting and problem diagnosis.)
-no "escalation" or support tiering system where problem can be rolled up to draw in more experience where needed.
-no good custom search set up for people to find resources for more obscure problems
-Too many lost souls showing up at webmaster, security and other aliases
-No low cost real-time channel offering
-No phone support via mozilla.com
-no central repository of diagnositc tool to help evaluate problems.
--lack of tools is also a problem
---http://groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/4706f1b67b218829/bbb5fc9c52579102?lnk=gst&rnum=1
In general we need to step back, and then figure out systems, processes, and community building that can help with fragementation problems:
-Fragmentation of content and number support channels and
-Fragmentation of contributors and contributions
-The goal of work in this area would be to simplfy the process and navigation path for users trying to get help, but also to better support the community of people that want to help other firefox users.
-There is a lot of evaluation, prototyping, and engagement with the Mozilla support communities that needs to happen before we do any major overall to the wide variety of support systems that are in place, but we should also open the door to improving our systems, rather than smaller refinements to existing systems.
--Something like
http://qunu.com/search/firefox or packages from
http://www.jivesoftware.com/ could offer improvements and interesting solutions to some of our problems. These packages offer things like real-time chat with zero download and should be pretty easy to deliver conversational kinds of help to novice users. Solutions like this might also offer possible better integration across all the forms of support that we need to offer, and hold the promise of providing better data and feedback mechisms for continual improvments.
--Its understood that one of the big challenges to bringing in new systems like qunu, jivesoftware or others is going to be figuring out how to build/migrate support community participants that will adopt to new kinds of systems.
--If anyone knows of support packages or tools that we should look at to help attack problems that everyone has worked together to outline now is a good time to make suggestions.
-chofmann