From MozillaWiki
Jump to: navigation, search

Meeting Details


  • 09:00 PDT
  • 11:00 CDT
  • 12:00 EDT
  • 16:00 UTC
  • 18:00 CET

Phone call details:

  • California: 650-903-0800 then extension 92
  • Toronto: 416-848-3114 then extension 92
  • Toll-free: 800-707-2533 then password 369
  • Skype (free): +18007072533 then password 369

Then, enter the conference number: 9435#

Video details:

  • Guest video link
  • You will need to download and install the Vidyo desktop software. #sumo <== Click the link to use web-based chat

Link to meeting video

Actions from last week

Design & Development work

  • Michel will be wrapping up the Title & Slugs and Summaries workshops over the next few days with proposals for the final style guide wording.
    • Question: How should we go about re-naming and re-summarizing articles?
      • Answer: Finish the workshop with the style guide final recommendation. Then create a spreadsheet of articles with their proposed new names (we can start with Susan's recommendations) and ask for feedback before changing them.
    • Question: Is there anything we can do to help localizers?
      • Answer: We need to work with Rosana to let localizers know about this and all of the other IA & UX work that is going on and how it will affect them.
  • We need to start the topic workshop, which means we need to decide on a final list of topics. Maybe Michael, Michelle, Bram and Matt can figure that out in the next week.
  • Ask a question button/topic: Susan recommends linking this to a task landing page. We used to use /ask for English. Should we change the button behavior back pending a new layout and update /ask with her recommendations (forum expectations, registration, public, etc.)?
    • The plan: Have the "Join the discussion" topic on the front page like Susan recommends and link that to /ask. This will be in addition to the button. We can re-evaluate after that. If having two ways to get to the AAQ flow makes things crazy we can get rid of the front page topic. The button can stay as is for now since it will go away with the re-design.



To do for nativeUI:

  • Download manager documentation
  • recommend using Adobe reader app for PDFs
  • Language information for beta
  • UA sniffing issues on SUMO
  • Updates to the list of supported devices and min version of Android
  • New documentation for About Firefox page
  • Updates to how Firefox uses the permissions it requests (personal info and accounts are new)


  • The article, How do I add a device to Firefox Sync?, was moved to the admin category because we only wanted it visible from it's in-product link. The problem with that is that it takes it off of localization dashboards. It's currently back in the How-to category but couldn't we put this in "Navigation" for now to remove it from sumo searches but still have it visible on L10n dashboards? This is not a good permanent solution though. Discussion
    • The plan: Just rename the category to something like "No Index." That will make it work for both navigation articles and the articles like the one in question. Also, we should document what the categories mean. More questions in the discussion.






Comments, questions, ideas

  • User education: Michael and Michelle talked about it briefly the other day. There's lots to do. We should brainstorm and prioritize. Probably a project to tackle in Q3.
  • Enterprise support: David proposed, "A knowledge base section with the most common questions around enterprise deployment answered in easy-to-follow howto's." Thoughts?
    • The plan:
      • David will run this by the ESR users.
      • Create a landing page (similar to Sync or Firefox Home) at /enterprise.
      • Create some KB articles with the topic "enterprise" (and don't make them "relevant to" anything else) and link them on this landing page.
      • Questions will still be handled by the ESR email list
      • Enterprise won't be integrated in SUMO as a product. It will mainly be found from the ESR mailing list and possibly linked from the ESR download page.
      • We should create one regular KB article to about enterprise support and have it point people to /enterprise.

Actions for next week