Firefox3/Firefox Requirements Meetings/OS Platform Integration: Difference between revisions

mNo edit summary
 
 
(5 intermediate revisions by 2 users not shown)
Line 3: Line 3:
== Dial-in Info ==
== Dial-in Info ==


* 650-903-0800x91 Conf# 8602 (US/INTL)
* +1 650-215-1282x91 Conf# 8602 (US/INTL)
* +1 866 879 4799 (pin 369) Conf# 8602
* +1 800-707-2533 (pin 369) Conf# 8602


== Agenda ==
== Agenda ==
The following list is taken directly from the [http://spreadsheets.google.com/pub?key=p4kVYBRbEKKgFPCn5XmfrXw&gid=0 Firefox 3 Detailed Feature List].  If this list does not match the other, the Google Spreadsheet version takes precedence (I may have made a copying error). 
* P1 - Provide MSI bundle (Windows only)
** P1 FR - Build system should create a .msi bundle
* P1 - Airbag
** P1 FR - Collect crash stack data and report it to central server
** P1 NFR - Improve usability of crash report UI
* P3 - Windows Group Policy support
** P3 NFR - Allow IT administrators to create group profile policies
* P3 - Vista Parental Controls support (Windows only)
** P3 FR - Integrate with Windows Vista parental controls
* Px - Vista compatibility for installation
== Notes ==
=== Item ===
* P1 - Provide MSI bundle (Windows only)
** P1 FR - Build system should create a .msi bundle
=== Notes ===
* Intended to facilitate enterprise deployment.  MSI is useful in a large number of ways in terms of providing flexibility.
* Question: People have been asking for MSI for years, and we've always deprioritized this.  Has this deprioritization of enterprise stuff changed?
* This is actually a P1 because of Vista more than because of enterprise work, although enterprise stuff is becoming increasingly important.
* Question: Is P1 too high a priority?
* Standing Question: Is this absolutely mandatory or should it be a P2? 
* Patches would have to be in .msp format, yes.
* POSSIBLE CHANGE: Change to "Integrate with MSI installation and patching systems"
=== Item ===
* P1 - Airbag
** P1 FR - Collect crash stack data and report it to central server
** P1 NFR - Improve usability of crash report UI
=== Notes ===
* Airbag is a replacement for Talkback. 
* This is largely about the Airbag client, other Airbag reqs are elsewhere.
* There is a lot more work that needs to be done on Airbag than is reflected here.
* We need the Airbag team to flesh this out further. 
* Worst case we have a generic thing to store the Airbag reports if the server is not ready yet. 
* Are we willing to ship Firefox 3 with just the client?  This is really a non-issue because a rudimentary server is already working, so we really just have to make sure the client is in the browser.
* We need to do a bunch of Firefox integration hooks.
* Do we want client-side feature parity with Talkback?  Not really interested in committing to this yet.  There's a meeting next week about Airbag and Airbag server where more info will be made available.
=== Item ===
* P3 - Windows Group Policy support
** P3 NFR - Allow IT administrators to create group profile policies
=== Notes ===
* This is definitely targeted at enterprise systems.
* We need to define this in more detail to come up with actual FRs.
* Agreed that it is a P3
* People will want to be able to enable/disable users ability to install or uninstall extensions as a global setting.  Users would have no choice but to use the extensions that are on the machines.  This would be used in situations like libraries and other shared computer situations.
=== Item ===
* P3 - Vista Parental Controls support (Windows only)
** P3 FR - Integrate with Windows Vista parental controls
=== Notes ===
* We do not currently know what's entirely involved with this, needs to be investigated in more depth.
=== Item ===
* Px - Vista compatibility for installation
=== Notes ===
* This is largely complete and is now a matter of bug tracking and fixing.
* DELETE from PRD
=== Additional stuff to consider and prioritize ===
* Integration with platform-native search services ie: spotlight on Mac
** Search integration should also be brought up in the Places discussion as well (radiant core guy will do it)
* When logging out in Linux it crashes Firefox - it doesn't quit, it just dies, also true with windows.  This is a filed bug.  Potential for data loss?  On restart you get the "Firefox has crashed" dialog, which is uncool.  There's some chance of dataloss.  Myk will provide a bug number.
** Dbaron will be contacted regarding coming up with a list of Linux-related issues that should be included here.
** 333907 - windows specific bug
*** comments have lots of references to other bugs
** 336193 - may be a linux/mac bug equivalent
** 365749 - linux specific bug (there is overlap) - refer to different signals
* Version detection for Windows - Vista vs XP since we may want to have a different theme for each.  Installation configuration piece.
* Growl integration for alerts?  Currently the only alert Firefox throws is download completion.  There is a bug for this (308552, 362685).  Could be useful for extensions.  nsIAlertService stuff.
** ADD: "P3 FR Growl alert notifications"
==== Follow-up (Mar 24th, 2007) ====
* to do per-version OS theming requires
** ADD: "P2 NFR Determine version of OS and select appropriate theme elements"
** ADD: "P2 FR Determine OS version at startup and select/apply appropriate theme"
** ADD: "P3 FR Add css-selector for OS version"
** ADD: "P3 FR Add OS-levels-supported metadata to theme packages and selection system" (this might belong in Add-ons)
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits