From MozillaWiki
Jump to: navigation, search

<< previous week | index | next week>>

Meeting Details

  • 11:00am PDT (18:00 UTC)
  • Mozilla HQ, 1st floor conference table
  • +1 866 216 2181
  • join #bonecho for attendance taking


  1. Bon Echo Alpha 2 (Tracking & Status)
  2. Development Roundtable
  3. Any other business

Bon Echo Alpha 2

Developer Roundtable

Add notes about work being actively done at the moment, areas where you'll need help/review, or things which the rest of the team should be made aware of. Leaving the section blank or linking to current discussion threads in dev.apps.firefox is perfectly acceptable.

Visual Refresh: Chrome Polish

  • no news from last week

Visual Refresh: Theme Polish

  • Radiant Core will be delivering 4 theme design mockups at the end of next week; also talking to RaizLabs.

Bookmarks and History: Places

  • ben to add any new update
  • Performance (brettw): Places Tp < 2% regressed on gaius. Startup time is probably faster than noplaces with reasonably-sized histories. Autocomplete is definitely faster than noplaces with reasonably-sized histories. Shutdown time is good.

User Experience: General & Tabbed Browsing

  • mconnor to add any new update

User Experience: Session Restore

User Experience: Spell Check

  • Branch patch completed but rejected due to potential security problem. Need to refactor a couple things to expose less on the XULDOMDocument. Need to fix on trunk as well.

User Experience: Microsummaries

  • attached initial patch to bug 334471 (alias: microsummaries)
  • the patch supports microsummaries specified by pages, the application, and third-party microsummary definition files;
  • per discussion in mda.firefox, switched from the extension model to the search engine model for installation of third-party definitions;
  • RSS/Atom feed microsummaries are not supported yet, but the architecture is now mostly there to support them, and I'm working on this next;
  • looking for all kinds of review (design, code, UI, etc.) and would like to figure out who the appropriate authoritative reviewers will be.

Feeds: Parser

  • SAX landed on trunk bug 325080. There are a couple follow-on bugs listed there. The most critical one adds asynchronous capabilities. bug 334304. It has sr already. Landing on branch will require some string munging in ReportError and a strategy for setting channel status in ParseFromStream. -sayrer
  • Toolkit FeedProcessor.js is @ 75%. I have time to push on it this week. -sayrer

Feeds: UI

  • ben/rsayre to add any new update

Extension Manager: UI

  • Close to finish (e.g. one to two days)

Extension Manager: Blocklisting

  • Complete except for blocklist web page and AMO integration

Extension Manager: Locale Packs

  • May miss A2

Search: UI

  • gavin to add any new update

Search: Plugin Format

  • gavin to add any new update

Distribution: Installer

  • Work will continue after Extension Manager UI patch is submitted (e.g. a day or two)

Distribution: EULA

  • cbeard to add any new update

Distribution: Channel Support

Infrastructure: Performance

  • shaver: SVG performance update code seems to be avaialable; Tor gave me a summary today. I'd be interested in hearing people's opinions on the cost vs. value on this one. The other thing on my radar is cairo uplift; there's a bunch of performance work upcoming, but likely after A2 so we'd need to be ready to review and take it for B1.
  • darin: are those text-rendering regressions different than those related to thebes?
    • shaver: yes, based on new stuff stuart put in based on text on the path and text shaping and positioning issues

Infrastructure: Platform Uplift

  • blocking-1.8.1 triage underway, about 15% done, would appreciate people going back and clearing any noms that they no longer believe in

Infrastructure: Instrumentation

The current proposal is to implement instrumentation as an extension. The advantages to this approach include the ability to update the extension independent of a release, in addition to greater flexibility in promoting the extension through vehicles such as

We'll continue to develop the code in the Mozilla CVS repository while evaluating options to host the data within the domain. Target release date for an Instrumentation Extension is TBD.

Security: Phishing

Currently working through policy and UI design elements around multi-provider support.

Security: SSL

User Documentation

Other Business