< Firefox2 | StatusMeetings
<< previous week | index | next week>>
- 11:00am PST (19:00 GMT)
- Mozilla HQ, 1st floor conference table
- +1 866 216 2181
- join irc.mozilla.org #bonecho for attendance taking
- 1 In Attendance
- 2 Agenda
- 3 Alpha 1 Status
- 4 Alpha 2
- 5 Developer Roundtable
- 5.1 Visual Refresh
- 5.2 Bookmarks and History
- 5.3 User Experience: Tabbed Browsing
- 5.4 User Experience: Session Restore
- 5.5 User Experience: Spell Check
- 5.6 Feeds: Parser
- 5.7 Feeds: UI
- 5.8 Extension Manager: UI
- 5.9 Extension Manager: Blocklisting
- 5.10 Extension Manager: Locale Packs
- 5.11 Search: UI
- 5.12 Search: Plugin Format
- 5.13 Distribution: Installer
- 5.14 Distribution: EULA
- 5.15 Distribution: Channel Support
- 5.16 Infrastructure: Performance
- 5.17 Infrastructure: Platform Uplift
- 5.18 Infrastructure: Instrumentation
- 5.19 Security: Phishing
- 5.20 Security: SSL
- 5.21 Documentation
- 6 Other Business
Hmmm... didn't get a good list
- Alpha 1 (Status)
- Alpha 2 (Targetted work)
- Development Roundtable
- Any other business
Alpha 1 Status
- 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
- 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
- product name=Bon Echo
- about graphic changed
- action: need to finish new mozilla.org pages before pushing to the wire (see: bug 331121)
- 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
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.
- Round up and decisions based on proposed changes to chrome posted to the wiki and also to the newsgroup
Bookmarks and History
User Experience: Tabbed Browsing
User Experience: Session Restore
- Patch in the review/edit cycle. No other news.
User Experience: Spell Check
Extension Manager: UI
- 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
- 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
- Nothing new
Search: Plugin Format
- Nothing new - focusing on Extension Manager code currently and will move on to the installer once most of that work is complete.
Distribution: Channel Support
Infrastructure: Platform Uplift
- 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!
- 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