canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Firefox3/Firefox Requirements Meetings/Follow up Actions: Difference between revisions
Jump to navigation
Jump to search
m
Firefox3/Firefox Requirements Meetings/Follow up Actions (view source)
Revision as of 20:05, 13 February 2007
, 13 February 2007no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
== Gecko Meeting == | == Gecko Meeting == | ||
'''ASSIGNED TO GECKO TEAM''' | |||
* "Print layout should look like rendered layout" | * "Print layout should look like rendered layout" | ||
** Needs to be clarified and better defined | ** Needs to be clarified and better defined | ||
| Line 26: | Line 27: | ||
* "Remove extension installation whitelist" | * "Remove extension installation whitelist" | ||
** Requires investigation to sort out how better this problem can be solved for users. Whoever does the design should work with dveditz. | ** Requires investigation to sort out how better this problem can be solved for users. Whoever does the design should work with dveditz. | ||
*** BELTZNER will meet with dveditz and explore further. | |||
* Extension first-run experience | * Extension first-run experience | ||
** Some extension first-runs pop up windows and dialogs, which is very jarring. Someone needs to think about how better to do that sort of thing. Extension authors should use the same model as Fx (notification system, UI flow). "Best practices" and evangelism required here as well -- | ** Some extension first-runs pop up windows and dialogs, which is very jarring. Someone needs to think about how better to do that sort of thing. Extension authors should use the same model as Fx (notification system, UI flow). "Best practices" and evangelism required here as well -- SHAVER + DevRel team. | ||
*** Assign to Shaver + DevRel team to discuss what they want to do re: the API for extension developers. DRIA WILL FOLLOW UP. | |||
* We are expecting some possible line items from shaver re: Add-ons section of the PRD, so someone needs to follow up on that after the Remora launch. | * We are expecting some possible line items from shaver re: Add-ons section of the PRD, so someone needs to follow up on that after the Remora launch. | ||
** DRIA will follow up with SHAVER | |||
** Rob Strong also has some items to add. DRIA to follow up with RSTRONG. | |||
* Rob strong needs a solid UI design provided for the addition of Add-ons configurations into the prefs panel. UI/UE team needs to provide that. | * Rob strong needs a solid UI design provided for the addition of Add-ons configurations into the prefs panel. UI/UE team needs to provide that. | ||
** Regular design work - RSTRONG to follow up and get beltzner's time. | |||
== Identity and Password Manager Meeting == | == Identity and Password Manager Meeting == | ||
* Need to talk to Identity system developers (OpenID, Cardspace, etc) and figure out how Firefox can better support those mechanisms. | * Need to talk to Identity system developers (OpenID, Cardspace, etc) and figure out how Firefox can better support those mechanisms. | ||
** Already started - BELTZNER to either hand off or complete. Also partially assigned to BASIL and WINDOW regarding follow up. | |||
* Talk to people doing OpenSource CardSpace implementations and find out what's needed to support those other providers. | * Talk to people doing OpenSource CardSpace implementations and find out what's needed to support those other providers. | ||
** BASIL to follow up here. | |||
* Beltzner to start a discussion thread about this in dev.planning. | * Beltzner to start a discussion thread about this in dev.planning. | ||
** Not yet | |||
* Mconnor to write up a spec for "way to do login through chrome rather than through a web page". | * Mconnor to write up a spec for "way to do login through chrome rather than through a web page". | ||
** MCONNOR will have this done next week. Spec, not a specific design. | |||
== Security and Privacy Meeting == | == Security and Privacy Meeting == | ||
* "Alert user when they're providing info on a suspicious website" | * "Alert user when they're providing info on a suspicious website" | ||
** This has been removed from the PRD but has been flagged as warranting follow up investigation. Should this be a Labs project? Could be related to password management. | ** This has been removed from the PRD but has been flagged as warranting follow up investigation. Should this be a Labs project? Could be related to password management. | ||
*** DRIA to move to IdeaCenter | |||
* "Private Browsing Mode" | * "Private Browsing Mode" | ||
** Someone needs to investigate liability issues related to this feature and how we "sell" it. | ** Someone needs to investigate liability issues related to this feature and how we "sell" it. | ||
*** BASIL or DRIA will take this action to contact our lawyers. | |||
* "Blacklisting of malicious sites" | * "Blacklisting of malicious sites" | ||
** Definition of "malware" is required -- needs to be thought through very carefully. | ** Definition of "malware" is required -- needs to be thought through very carefully. | ||
*** SCHREP will set up a meeting to get further definition here. | |||
== Content Handling Meeting == | == Content Handling Meeting == | ||
* "Play all popular media formats when plugins are installed" | * "Play all popular media formats when plugins are installed" | ||
** Follow up required here to investigate bundling possibilities and options. | ** Follow up required here to investigate bundling possibilities and options. | ||
*** BASIL will do follow up here | |||
* "Plugin crashes should not crash the entire application" | * "Plugin crashes should not crash the entire application" | ||
** Must be added to Moz2 tracking | ** Must be added to Moz2 tracking | ||
*** REMOVE from Fx3, move to Moz2 | |||
* Improve download handling | * Improve download handling | ||
** Requires support from Gecko side, so this has to be discussed with the Platform team. | ** Requires support from Gecko side, so this has to be discussed with the Platform team. | ||
*** Add this to the GECKO bucket | |||
* "Download manager can be extended in a way that feels tightly integrated" | * "Download manager can be extended in a way that feels tightly integrated" | ||
** Requires further investigation and refinement | ** Requires further investigation and refinement | ||
*** MCONNOR to follow up on this | |||
* "Microformats" | * "Microformats" | ||
** Entire section needs to be revisited and possibly reworded with intention of deemphasizing "microformats" and focusing on a more generalizable system of inferred pieces of data, metadata, other forms of structured information on a page. | ** Entire section needs to be revisited and possibly reworded with intention of deemphasizing "microformats" and focusing on a more generalizable system of inferred pieces of data, metadata, other forms of structured information on a page. | ||
** All FRs/NFRs need to be revisited with this in mind | ** All FRs/NFRs need to be revisited with this in mind | ||
*** MCONNOR will take this for now | |||
* RSS enclosure handling | * RSS enclosure handling | ||
** Further investigation and discussion required here as it's currently a mess and the existing PRD doesn't deal with it at all. | ** Further investigation and discussion required here as it's currently a mess and the existing PRD doesn't deal with it at all. | ||
*** DMOSE will investigate further in March | |||
== Tabbed Browsing and Search Meeting == | == Tabbed Browsing and Search Meeting == | ||
* "Rich search results (needs to be more clearly defined)" | * "Rich search results (needs to be more clearly defined)" | ||
** This needs to be more clearly defined and turned into a set of actionable PRD line items. | ** This needs to be more clearly defined and turned into a set of actionable PRD line items. | ||
*** MYK to come up with further examples, services, and details | |||
== Help and User Support Meeting == | == Help and User Support Meeting == | ||
* | * MCONNOR to provide Visio for help/support flow | ||
* We need a separate effort outside of the Firefox3 scope towards investigating and doing something about user help and support. This doesn't necessarily have to be absolutely tied to the product. | * We need a separate effort outside of the Firefox3 scope towards investigating and doing something about user help and support. This doesn't necessarily have to be absolutely tied to the product. | ||
* Larger project is out of band for Firefox 3 and needs to be taken on as a separate independent project. | ** Larger project is out of band for Firefox 3 and needs to be taken on as a separate independent project. | ||
* We need someone who can own this entire world. | ** We need someone who can own this entire world. | ||
* "Showcase breadth of customization options" | *** Being escalaed through Steering Committee | ||
* "Showcase breadth of customization options" - discoverability of customization | |||
** Requires clearer definition in consultation with Beltzner | ** Requires clearer definition in consultation with Beltzner | ||
*** BELTZNER | |||
* "Crash reporting" | * "Crash reporting" | ||
** Requires follow up and refinement | ** Requires follow up and refinement | ||
*** REMOVE | |||
== OS Platform Integration Meeting == | == OS Platform Integration Meeting == | ||
* MSI priority needs to be verified | * MSI priority needs to be verified | ||
** Vista work - schrep says right now P1 - may be deprioritized during global priority pass | |||
* Airbag team needs to be involved with fleshing out Airbag PRD items where/if required. | * Airbag team needs to be involved with fleshing out Airbag PRD items where/if required. | ||
** Yes, we'll have that team do a review when they're able. | |||
* "Windows Group Policy support" | * "Windows Group Policy support" | ||
** More detail required as it currently has no concrete FRs | ** More detail required as it currently has no concrete FRs | ||
*** MCONNOR will find someone to own this | |||
* "Vista Parental Controls support" | * "Vista Parental Controls support" | ||
** We do not currently know what's entirely involved with this, needs to be investigated in more depth. Specific FRs required. | ** We do not currently know what's entirely involved with this, needs to be investigated in more depth. Specific FRs required. | ||
*** BASIL or DRIA for initial scoping, possibly leveraging DOUGT | |||
* Dbaron to come up with a list of specific Linux issues that should be dealt with in Firefox 3 and those will be added to the PRD as FR line items. | * Dbaron to come up with a list of specific Linux issues that should be dealt with in Firefox 3 and those will be added to the PRD as FR line items. | ||
** DRIA to follow up with DBARON | |||
* "Version detection for Windows - Vista vs XP since we may want to have a different theme for each. Installation configuration piece." | * "Version detection for Windows - Vista vs XP since we may want to have a different theme for each. Installation configuration piece." | ||
** This is largely undefined and was not expanded upon further in the meeting. See meeting notes for info. | ** This is largely undefined and was not expanded upon further in the meeting. See meeting notes for info. | ||
*** BELTZNER to crisp up the requirements and find a driver for this work | |||
* '''NEW''' Get all the Linux distros involved in Firefox development. We are not going to ship release binaries for Linux, so someone needs to get them involved. Ubuntu, SUSE, RedHat, Fedora...etc. | |||
** Someone needs to own this, not Mconnor. | |||
== Places Meeting == | == Places Meeting == | ||
* "UI for Export" | * "UI for Export" -- this is mostly about having a bookmarks.html file | ||
** Needs to be discussed and decided. If UI is required, must be added to the PRD. | ** Needs to be discussed and decided. If UI is required, must be added to the PRD. | ||
*** Basically just keep writing out bookmarks.html and don't provide any UI for users to do export. Basically keep this around - it's easy, doesn't cost us much. | |||
*** CHANGE requirement to "Maintain existing bookmarks.html functionality (no new API or dataformats involved)" | |||
* "Places organizer redesign" | * "Places organizer redesign" | ||
** Too vague to be useful. Needs to be investigated in more depth for actual requirements which should then be added to the PRD. | ** Too vague to be useful. Needs to be investigated in more depth for actual requirements which should then be added to the PRD. | ||
*** ASSIGNED TO PLACES TEAM | |||
* Live Bookmark vs New Subscription user agent string? Basil's question requires follow up. | * Live Bookmark vs New Subscription user agent string? Basil's question requires follow up. | ||
** RESOLVED | |||