Visit Mozilla.org

Firefox2/StatusMeetings/2006-03-21

From MozillaWiki

<< previous week | index | next week>>

Meeting Details

  • 11:00am PST (19:00 GMT)
  • Mozilla HQ, 1st floor conference table
  • +1 866 216 2181
  • join irc.mozilla.org #bonecho for attendance taking

Contents

In Attendance [edit]

Hmmm... didn't get a good list

Agenda [edit]

  1. Alpha 1 (Status)
  2. Alpha 2 (Targetted work)
  3. Development Roundtable
  4. Any other business

Alpha 1 Status [edit]

Features [edit]

  • all work on alpha 1 features has landed and is complete
    • places infrastructure
    • undo close tab (pushed to A2)
    • tab overflow (pushed to A2)
    • extension blocklisting
    • extension dependencies
    • search plugin format changeover & sherlock importer
    • spell-as-you-type (pushed to A2)
    • instrumentation infrastructure (note: blocked on server-side)
    • RSS parser (not reviewed in time, pushed to A2)
    • RSS content detection

Release Issues & Timing [edit]

  • Last check-in was around 5:30pm PST on 3/20/06. The build has been tagged
  • The message to the community should be that this is a developers release!
  • branding changes complete
    • rv=2.0a1
    • product name=Bon Echo
    • about graphic changed
    • action: need to finish new mozilla.org pages before pushing to the wire (see: bug 331121)

Alpha 2 [edit]

  • alpha2 is "Feature Complete" according to the proposed roadmap
    • this means that all feature work is done, but UI can still be in progress using placeholder dialogs and strings
    • feedback from A2 should be used to revise the UI for the features
    • intended for high-risk early adopters
  • action: ensure that work targetted for A2 is marked with the appropriate milestone in BugZilla
  • action: need to start scoping work for A2 and delivering estimates so we can plan and track to a date (approx 2 months)
  • action: group to comment on substance of PRD especially as it relates to Bon Echo Alpha 2

Developer Roundtable [edit]

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. Leving the section blank or linking to current discussion threads in dev.apps.firefox is perfectly acceptable.

Visual Refresh [edit]

Bookmarks and History [edit]

User Experience: Tabbed Browsing [edit]

User Experience: Session Restore [edit]

  • Patch in the review/edit cycle. No other news.

User Experience: Spell Check [edit]

Feeds: Parser [edit]

Feeds: UI [edit]

Extension Manager: UI [edit]

  • Will have the wiki finished by the end of the week and emails sent to the dev.apps.firefox list for further discussion.

Extension Manager: Blocklisting [edit]

  • landed... so far the only regressions are a couple of ui glitches that were known prior to landing and will be fixed by the Extension Manager UI rewrite.
  • Going to try to finish plugin blocklisting for Alpha 2.

Extension Manager: Locale Packs [edit]

  • Nothing new

Search: UI [edit]

Search: Plugin Format [edit]

Distribution: Installer [edit]

  • Nothing new - focusing on Extension Manager code currently and will move on to the installer once most of that work is complete.

Distribution: EULA [edit]

Distribution: Channel Support [edit]

Infrastructure: Performance [edit]

Infrastructure: Platform Uplift [edit]

  • SVG textPath landed, minor regressions also fixed.
  • Unicode-XPCOM-file-path work still underway, no ETA for trunk or branch landing.
  • Looking for other perf (time and space) wins.
    • Need to measure with an updated cairo and see which camp's predictions hold!

Infrastructure: Instrumentation [edit]

Security: Phishing [edit]

Security: SSL [edit]

  • beltzner attended a W3C workshop on "Usability and Web Authentication" last week (you can check out his position paper and presentation (big, flash, sorry!))
    • most plausible suggestions for Firefox2 timeframe were Google Safe Browsing, some form of heuristic detection based on browsing history and bookmarks, use of <browsermessage> notification, potentially a mechanism for disabling JS and other technologies that assist spoofing on SSL signin pages, and APIs to allow easy integration of third party tools for security
    • W3C will be producing notes and summary soon, I'll link to that as we get it
    • will follow up with Sherman offline about phishing-related discussions

Documentation [edit]

Other Business [edit]

Retrieved from "http://wiki.mozilla.org/Firefox2/StatusMeetings/2006-03-21"