Labs/Ubiquity/Meetings/2009-06-17 Weekly Meeting

From MozillaWiki
< Labs‎ | Ubiquity‎ | Meetings
Jump to: navigation, search

Details

Time

5:00pm Pacific time

Location

  • IRC channel: #ubiquity
  • Dial in:
    • +1 800 707 2533 (pin 369) Conf# 202 (US Toll Free/Skype)
    • +1 650 903 0800 x92 Conf# 202 (US/International)
    • +1 416 848 3114 x92 Conf# 202 (Canada)

Agenda

Talk about getting ready for Ubiquity 0.5 release on Monday!!!

Attendees

  1. Jono
  2. mitcho
  3. brandon
  4. cers
  5. heather
  6. zac
  7. blair

Notes

Preparation for 0.5

  • 0.5 Release will be next Monday!
  • Today or the first half of tomorrow should be the end of adding new features to code for 0.5.
  • Spend Thursday, Friday, and Monday focusing on bug fixes and testing, as well as localizing strings
  • This is not really a "beta", refer to it as Ubiquity 0.5
  • blockers still to be fixed for 0.5
    • Localizing commands
    • Parser 2 unit tests
  • Suggested parser features to get in to 0.5
    • Trac reports #732, #738, #752
    • Brandon is handling #732, will be in 0.5

Publicity and Documentation

  • Lots of work needed to be done
  • Heather made 0.5 documentation page in Wiki which links to important pages
  • Mitcho will be working on wiki pages for...
    • converting commands to Parser 2 api
    • updating author tutorial
    • making your commands localize-able and localizing commands
  • Let's do as much of the documenting as we can by Monday. On Tuesday we will focus on finishing any documentation that didn't get done.

Localization discussion

  • Decided on a single method for rendering templates using CmdUtils.renderTemplate
    • have _() wrap output in renderTemplate
    • mitcho's example: if _("template ${var}",{var:var}), run it through renderTemplate


Things not included in 0.5

  • Data Collection will be a 0.6 thing
  • Plug-in provider verbs not essential for this release. Can be released as a smaller thing after 0.5 (like 0.5.1).

Other

  • Zac would like everyone to check out his latest blogpost[1] and provide feedback