Support/Weekly Meetings/Minutes 2008-07-14

From MozillaWiki
Jump to: navigation, search

Support » Weekly Meetings » 2008-07-14

Attendees: djst, Cww, cilias, np

Sumo

  • Cww is in MV this week! Sitting in the conf room with djst.
  • Proposed goals for Q3:
    • Establish formal feedback loop to QA/dev about user's most common Firefox problems
    • Develop performance & customer satisfaction metrics to determine our quality of support
    • Get better understanding of how people are using SUMO to further improve the site -- are people searching? what do they search for? what's the usage ratio of the KB vs user-to-user support offerings?
    • Make the support forum helpful and easy to use for both contributors and users (SUMO 0.7 milestone)
    • Plan, design, and develop improved search engine to replace the one currently used in SUMO
  • New milestone scheme -- instead of major 0.x milestones and ad hoc production server pushes, we're switching to minor 0.0.x milestones on a bi-weekly basis
    • This gives us and IT better control, and allows for more structured scheduling
    • The overall 0.x milestones will still be kept, but they will be fixed incrementally. E.g. 0.7 will be preceded by 0.6.1, 0.6.2, etc.

Knowledge Base

  • Survey results and analysis are posted in mozilla.support.planning [1]. Lots of good feedback that we should digest, e.g.:
    • UI of article editor confusing -- djst has been in contact with Alain Désilets of TikiWiki about what things need improvement in terms of usability. Should definitely share this feedback with Alain.
    • cilias to provide a condensed list of UI/l10n specific feedback and report to djst
  • Bugzilla: 4 new article requests [2], 1 article bug fixed [3].

Forums

  • Similar traffic as last week. No stats this week.
  • np still has some access problems in getting to use the db dumbs for stats analysis. Will comment in bug report about it.
  • One of our biggest problems today is that most users post anonymously, and we have little knowledge of how many of those users actually find their way back to the thread they posted when someone responds to it. This is something we will fix with the 0.7 milestone by sending out an e-mail notification to the original poster whenever someone responds to a thread. The OP should then be able to either:
    • Select "Yes, this response solved my problem," which would mark the thread as solved, or
    • Select "No, this response did not solve my problem," which would take the user back to the thread so he/she can provide more info
  • This will likely dramatically increase the number of users getting their problems solved, and it will also allow us to confirm that we're doing a good job (customer satisfaction metrics).

Live Chat

  • Cww, zzxc, and cilias can all help with covering the shifts for this week. np can't really help out because of his full-time job that conflicts with the hours of operation.
  • cilias has some good feedback about the Live Chat process since he views it from a different perspective than the people who have already used it. Will provide feedback and share with team.
  • More generally, getting feedback from new contributors is something we should focus more on. Actively ask contributors if there are things they find confusing, and pay attention to what questions we receive from contributors/localizers.