Firefox2/StatusMeetings/2006-03-21

<< 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

Agenda

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

Alpha 1 Status

Features

• 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

• 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

• alpha2 is "Feature Complete" according to the Firefox2/PRD#Release_Roadmap 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

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

• Round up and decisions based on proposed changes to chrome posted to the wiki and also to the newsgroup

Security: SSL

• beltzner attended a W3C workshop on "Usability and Web Authentication" last week (you can check out his position paper and presentation)
  • 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