The Mozilla Support Blog

Rocking the helpful web since 2007.
Categories: Contributor News

Minutes of Weekly Meeting 3/3

5 responses

Attendees: djst, cilias, lucy, nkoth, zzxc

Sumo

  • Weekly metrics [1]
    • Traffic to site steadily increasing — more than doubled the last couple of weeks!
  • 0.5 milestone status (localization) [2]
    • Done, pending one low-priority bug [3] that we will slip
  • 0.6 milestone status (in-product help) [4]
    • In-product mode will land this Friday [5]
    • Start page has been cleaned up [6], but we need to move top 10 list out to a content id block to make sure we can change it without touching the localized pages. Also, we need to decide on the New to Firefox box. Suggestion: just a stylish, large box with the text “New to Firefox? Click here!” Clicking on it would take you to the in-product landing page [7]

Knowledge Base

  • Week before last: 0 article requests, 3 new articles [8]. Last week: 0 article requests, 4 new articles[9].
  • New en-US contributor: David Naylor (naylor83), who has been fixing use of language, to make English articles more understandable. Also, he has translated some articles to Swedish. Welcome, and thanks, David!
  • Big thanks to Alice Wyman, who improved the Importing from Netscape article.
  • SHOWFOR
    • Per djst’s request, we’re not going to bother making sure SHOWFOR is applied to all article that need it. Instead, we’re going to make sure the top 50 articles are taken care of, and hope the community takes care of the rest.
      • Just to clarify, I don’t think it’s a high enough priority for us to do the update on all articles. The important thing is that we make the technology easy for other contributors to use and understand, and update the most read articles to show how we intend for the technology to be used. — djst
    • The above necessitates that we create new dynamic content, that is basically the current dynamic content, but with SHOWFOR. This way, articles without SHOWFOR won’t be broken.
  • Content ID
    • We’re currently reusing blocks of text in articles that are used in more than one article, e.g. instructions on how to access the Options/Preferences window. To make this easier to use, we currently use something called content ids, which is like a variable we insert in a wiki document, e.g. {content id=4}, which then translates to the actual text, e.g. “In the menu, click Tools and then click Options…”
    • We need to switch from using e.g. {content id=4} to use {content label=options} instead.
      • Unlike content ids, content labels are localizable
      • Easier to remember a word than a number
      • Chris to write documentation for contributors and localizers on how to use this
  • Need to switch from using content ids to use content label

Forums

  • Jason couldn’t make it to this meeting.

Live Chat

  • Presented list of our biggest issues with the live chat software to Jive
    • Initial response from Jive that it would be too time consuming for them to work out an arrangement where we can hack on it ourselves. They will try to work on some of the stuff on the list while considering other ways we could collaborate with them instead
  • Need to focus on recruiting — excellent doc written by Cww after brainstorming with other community members.
    • Definitely some very good points on things we can do to improve our community energy
    • Nelson to ask Mark Laporte of TikiWiki to read the document and see if there’s anything about the IssueTracker feature that can be used here

5 comments on “Minutes of Weekly Meeting 3/3”

  1. David Naylor wrote on

    I’d like to suggest a scheme were the content labels are localized in this way:

    en-US: label=Options
    sv-SE: label= Options-sv-SE

    Otherwise, if the label is simply translated, there will be clashes between languages. Swedish and Norwegian for instance often use the same words.

    I have also come across article titles which clash between different l10ns. The Norwegian title for the “Profiles” article is “Profiler”. Hence (?) I couldn’t create a Swedish article “Profiler”.

  2. David Naylor wrote on

    BTW, it’s fun to be able to help. But I’d say I’m mainly a sv-SE contributor, even though I’ll edit the en-US articles too when I can improve them.

  3. David Tenser wrote on

    David: Actually, the content labels are localizable without using different names. If you put a {content label=options} in a Swedish translation of an article, the Swedish content of that item will be used, unless it’s not yet translated, in which case it will fallback to English. So, we just need people to localize the contents of the content labels and can use the same label name in all languages. Chris will write documentation on how to translate content labels soon.

    About the problem with two articles with the same name, that is indeed an issue. Technically, we can’t allow two articles to have the same name, so in this case you would have to call the Swedish article e.g. “Profiler (svenska)”. The better solution is to not use short article names like this and instead name it something more meaningful. However, we’ll still run into problems when supporting dialects, e.g. pt-PT and pt-BR, so ideally we would support two articles with the same name, but automatically generate unique URLs for them. We should look into that.

  4. David Tenser wrote on

    By the way, it’s really great to have you on board! :)

  5. David Naylor wrote on

    “Actually, the content labels are localizable without using different names.”

    Ok, great. :)