MozillaWiki

Firefox3/Firefox Requirements Meetings/Follow up Actions: Difference between revisions

< Firefox3‎ | Firefox Requirements Meetings
mNo edit summary
No edit summary
 
(49 intermediate revisions by 6 users not shown)
Line 1: Line 1:
NOTE: COMPLETE or DELETE items have been removed from this list.  If you think something has been missed, please ping Deb so it can be re-added.  '''NEW:''' Grey background means the item is complete or no longer relevant.
= Actions =
= Actions =


== Gecko Meeting ==
<table class="fullwidth-table">
'''ASSIGNED TO GECKO TEAM'''
<tr>
* "Print layout should look like rendered layout"
<th>Owner</th>
** Needs to be clarified and better defined
<th>Category</th>
** Actual use cases and possible test cases are needed to figure out how this is broken
<th>Action</th>
* "Layout should be zoomed/cropped to fit desired page size"
<th>Status</th>
** Bug numbers needed or bugs need to be filed
<th>Notes</th>
* "Printed material should match user expectations"
</tr>
** Needs to be more clearly defined
</table>
* "Save web pages as PDF"
** Vlad and Pav to investigate further
* "Provide infrastructure for an extensible Web page archiving system"
** Someone needs to investigate how other browsers (ie5 on mac, omniweb, etc) approach this problem
** Do we care enough about this to assign as part of Fx3 or will it be followed up on through a Labs project?  Someone needs to figure that out.
* "TTS/Screenreader support"
** Someone needs to follow up on this by asking Aaron Leventhal if we already have it, and, if not, what it would mean to implement it.
* "CSS 2.1"
** Specifics need to be sorted out.  To be discussed by brendan, dbaron, roc.  We need a set of specific and trackable line items (with priorities) for this.
* "CSS 3 features"
** As with CSS 2.1, specifics need to be sorted out and turned into trackable line items for the PRD.
* Offline apps
** Further investigation and refinement required.  Meeting needs to be scheduled.
 
== Add-ons Meeting ==
* "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.
*** BELTZNER will meet with dveditz and explore further.
* 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 -- 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.
** 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.
** Regular design work - RSTRONG to follow up and get beltzner's time.
 
== 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.
** 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.
** BASIL to follow up here.
* 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 will have this done next week.  Spec, not a specific design.
 
== Security and Privacy Meeting ==
* "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.
*** DRIA to move to IdeaCenter
* "Private Browsing Mode"
** 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"
** 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 ==
= Completed Items =
* "Play all popular media formats when plugins are installed"
<table class="fullwidth-table">
** Follow up required here to investigate bundling possibilities and options.
<tr>
*** BASIL will do follow up here
<th>Owner</th>
* "Plugin crashes should not crash the entire application"
<th>Category</th>
** Must be added to Moz2 tracking
<th>Action</th>
*** REMOVE from Fx3, move to Moz2
<th>Status</th>
* Improve download handling
<th>Notes</th>
** Requires support from Gecko side, so this has to be discussed with the Platform team.
</tr>
*** Add this to the GECKO bucket
<tr style="background:#ddd;>
* "Download manager can be extended in a way that feels tightly integrated"
<td>Basil</td>
** Requires further investigation and refinement
<td>Sec, Priv</td>
*** MCONNOR to follow up on this
<td>Consult with lawyers re: Liability issues related to how we sell/promote "Private Browsing Mode"</td>
* "Microformats"
<td>No liability issues per se but privacy policy needs to be updated to reflect new mode</td>
** 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.
<td></td>
** All FRs/NFRs need to be revisited with this in mind
</tr>
*** MCONNOR will take this for now
<tr style="background:#ddd;">
* RSS enclosure handling
<td>Basil, Dria</td>
** Further investigation and discussion required here as it's currently a mess and the existing PRD doesn't deal with it at all.
<td>Gecko</td>
*** DMOSE will investigate further in March
<td>Follow up with AaronL re: Accessibility reqs for Fx3</td>
<td>COMPLETE</td>
<td>2 line items added to PRD in OS Integration section</td>
</tr>
<tr style="background:#ddd;">
<td>Beltzner</td>
<td>Add-ons</td>
<td>Investigate removing extension installation whitelist, consulting with Dveditz</td>
<td>COMPLETE</td>
<td>whitelist will remain but UI will change such that it doesn't interrupt installation task flow and doesn't require users to add the site to the whitelist to continue, bug to be filed</td>
</tr>
<tr style="background:#ddd;">
<td>Beltzner</td>
<td>Help/Support</td>
<td>"Showcase breadth of customization options + discoverability of customization" needs to be refined and turned into actionable line items</td>
<td>COMPLETE</td>
<td>see [[Firefox3/Firefox_Requirements_Meetings/Help_and_User_Support#Follow-up|here]]</td>
</tr>
<tr style="background:#ddd;">
<td>Beltzner, Rstrong</td>
<td>Add-ons</td>
<td><del>UI design required for addition of Add-ons prefs to prefs panel</del></td>
<td>REMOVED</td>
<td>Will be handled as part of feature design phase</td>
</tr>
<tr style="background:#ddd">
<td>Dria, Basil</td>
<td>Places</td>
<td>"UI for Export" - requirement involved with this to "Maintain existing bookmarks.html functionality (no new API or dataformats involved)"</td>
<td>NO ACTION REQUIRED</td>
<td></td>
</tr>
<tr style="background:#ddd;">
<td>Dria, Rstrong</td>
<td>Add-ons</td>
<td>Define additional Add-ons-related line items for PRD</td>
<td>COMPLETE</td>
<td>Items will be part of Feature plan, not PRD.</td>
</tr>
<tr style="background:#ddd;">
<td>Unowned</td>
<td>Gecko</td>
<td>Investigate Web page archiving systems and devise an approach for sorting this out for Firefox (be it a Labs project or what-have-you)</td>
<td>Deferred for now since it's a P3. If we decide to pick this up then we'll revisit how the feature is designed.</td>
<td>Someone needs to sort out if this is in-scope for Fx3 or not.  This needs an owner/driver. DECISION: Out-of-scope for Fx3</td>
</tr>
<tr style="background:#ddd">
<td>Vlad, Pav</td>
<td>Gecko</td>
<td>"Save web pages as PDF"</td>
<td>COMPLETE</td>
<td>No further PRD changes required.</td>
</tr>
<tr>
<td>Schrep</td>
<td>Sec, Priv</td>
<td>Set up meeting to get further definition of what "malware" means in terms of "Blacklisting malicious websites"</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Schrep?</td>
<td>OS Integration</td>
<td>Airbag/Brakepad PRD line items need to be fleshed out by the Airbag/Brakepad team where required</td>
<td></td>
<td>I've assigned this to Schrep, because it had no specific owner.  If this is incorrect, please reassign.</td>
</tr>
<tr style="background:#ddd;>
<td>Basil</td>
<td>OS Integration</td>
<td>"Vista Parental Controls Support" needs to be investigated in more depth.</td>
<td>Completed</td>
<td>Created a list of bugs - 355554, 355555, 372905, 372914, 372920</td>
</tr>
<tr>
<td>Beltzner</td>
<td>Identity, Password Mgr</td>
<td>Start a discussion thread re: third party Cardspace implementations in dev.planning</td>
<td>Cancelled</td>
<td>After discussion with Higgins team, determined that we'll do some Mozilla Labs postings to accelerate discussion of this topic.</td>
</tr>
<tr>
<td>Beltzner, Window</td>
<td>Identity, Password Mgr</td>
<td>Hand-off or complete discussion with Identity system developers re: how Firefox can better support those mechanisms (OpenID, Cardspace, etc)</td>
<td>COMPLETE</td>
<td>Started discussions with Higgins and OpenID, Cardspace is documented</td>
</tr>
<tr>
<td>Roc, Dbaron</td>
<td>Gecko</td>
<td>Specific line items for CSS 2.1 support are needed</td>
<td>IN PROGRESS</td>
<td>Dria has list and is getting it reviewed.</td>
</tr>
<tr>
<td>Roc, Dbaron</td>
<td>Gecko</td>
<td>Specific line items for CSS 3 support are needed</td>
<td>IN PROGRESS</td>
<td>Dria has list and is getting it reviewed.</td>
</tr>
<tr>
<td>Basil</td>
<td>Identity, Password Mgr</td>
<td>Talk to third parties doing Cardspace implementations and find out what's needed to support them as providers within Firefox</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Dietrich</td>
<td>Places</td>
<td>"Places organizer redesign" needs to be investigated and turned into a set of requirements for the PRD as it's currently too vague - assigned to "Places team"</td>
<td>IN PROGRESS</td>
<td>Wiki [http://wiki.mozilla.org/Places:Manager here]. Scoped to some high-priority items after discussion w/ mconnor. Need to meet w/ Beltzner to talk UI/UE for this.</td>
</tr>
<tr style="background:#ddd;">
<td>Dria, Dbaron</td>
<td>OS Integration</td>
<td>Come up with a list of specific Linux issues that should be dealt with in Fx3 and add them to the PRD as FR line items</td>
<td>Dropped</td>
<td>''Need to follow up.''</td>
</tr>
<tr>
<td>Mconnor</td>
<td>Con Handling</td>
<td>Revisit Microformats items on PRD, revisit and reword to deemphasize "microformat" and focus more on generalizable system of inferred pieces of data, metadata, and other forms of structured information</td>
<td></td>
<td></td>
</tr>


== Tabbed Browsing and Search Meeting ==
<tr>
* "Rich search results (needs to be more clearly defined)"
<td>Roc</td>
** This needs to be more clearly defined and turned into a set of actionable PRD line items.
<td>Gecko</td>
*** MYK to come up with further examples, services, and details
<td>Offline apps - further investigation and refinement needed, specific line items required</td>
<td>MEETING HELD</td>
<td>Next step: going through meeting notes and extracting line items for PRD. </td>
</tr>


== Help and User Support Meeting ==
<tr>
* MCONNOR to provide Visio for help/support flow
<td>Basil</td>
* 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.
<td>Help/Support</td>
** Larger project is out of band for Firefox 3 and needs to be taken on as a separate independent project.
<td>Find someone to own the whole Help/Support world</td>
** We need someone who can own this entire world.
<td>Raised to management team</td>
*** Being escalaed through Steering Committee
<td>JT Batson and others are investigating</td>
* "Showcase breadth of customization options" - discoverability of customization
</tr>
** Requires clearer definition in consultation with Beltzner
<tr>
*** BELTZNER
<td>Beltzner</td>
* "Crash reporting"
<td>OS Integration</td>
** Requires follow up and refinement
<td>Refine requirements and find a driver for "Version detection in Windows for theme installation piece"</td>
*** REMOVE
<td>COMPLETED</td>
<td>See [[Firefox3/Firefox_Requirements_Meetings/OS_Platform_Integration#Follow-up_.28Mar_24th.2C_2007.29|here]]</td>
</tr>
<tr>
<td>Dmose</td>
<td>Con Handling</td>
<td>Firefox team needs to get a list of requirements together re: "Improve download handling", then make sure the Gecko team knows about and understands what's required on their part</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Dmose</td>
<td>Con Handling</td>
<td>Refine what "Download manager can be extended in a way that feels tightly integrated" means</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Basil</td>
<td>Gecko</td>
<td>Printing issues need to be clarified and better defined</td>
<td>In Progress</td>
<td>Basil is generating list, triaging [http://tinyurl.com/362fkq critical bugs from this ugly list]</td>
</tr>
<tr>
<td>Basil</td>
<td>Con Handling</td>
<td>Investigate bundling possibilities and options re: plugins for common formats</td>
<td></td>
<td>Deferred due to goals/priorities exercise</td>
</tr>
<tr>
<td>Dmose</td>
<td>Con Handling</td>
<td>Investigate RSS enclosure handling and come up with a set of line items that should be added to the PRD</td>
<td></td>
<td>Rolled into content handling spec</td>
</tr>
<tr>
<td>Dria, Shaver</td>
<td>Add-ons</td>
<td>Define additional Add-ons-related line items for PRD</td>
<td>Met with shaver, have notes.  Need to sort out what if anything needs to hit the PRD.</td>
<td>Done.</td>
</tr>
<tr>
<td>Dria, Shaver, DevRel team</td>
<td>Add-ons</td>
<td>Figure out how to improve extension first-run experience and related API for extension developers.</td>
<td>Met with shaver, have notes.  Need to sort out what if anything needs to hit the PRD.</td>
<td>Ext authors should be able to use the same model as Fx (notification system, UI flow).  "Best practices" and evangelism required here as well. '''Done'''</td>
</tr>
<tr>
<td>Mconnor</td>
<td>Identity, Password Mgr (P3)</td>
<td>Write up a spec about how to do login through chrome rather than through a web page</td>
<td></td>
<td>Deferred due to P3 priority.</td>
</tr>
<tr>
<td>Mconnor</td>
<td>Help/Support</td>
<td>Provide Visio for help/support flow</td>
<td></td>
<td>Handling by JT Batson and customer working group. Deb assisting for Fx 3</td>
</tr>
<tr>
<td>Mconnor</td>
<td>OS Integration</td>
<td>Find someone to own defining what "Windows Group Policy Support" means in terms of line items, then get those items added to PRD</td>
<td></td>
<td>Postponed due to lack of clear enterprise reqs in this area. Basic investigation shows that Active Directory (AD) integration is not as critical since selected enterprises use Fx as backup browser and don't want an AD dependency</td>
</tr>
<tr>
<td>Myk</td>
<td>Search</td>
<td>"Rich search results" needs to be more clearly defined and turned into a set of actionable line items</td>
<td></td>
<td>updated and expanded [http://wiki.mozilla.org/Search/Rich_Results proposal], including adding [http://wiki.mozilla.org/Search/Rich_Results#Proposed_PRD_Items proposed PRD items].</td>
</tr>


== OS Platform Integration Meeting ==
</table>
* MSI priority needs to be verified
= Further Notes =
** 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.
** Yes, we'll have that team do a review when they're able.
* "Windows Group Policy support"
** More detail required as it currently has no concrete FRs
*** MCONNOR will find someone to own this
* "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.
*** 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.
** 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."
** 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 ==
* "Alert user when they're providing info on a suspicious website" has been removed from the PRD but has been flagged as warranting follow up.  This will be brought up in the Labs IdeaCenter forum when it is available.
* "UI for Export" -- this is mostly about having a bookmarks.html file
*  <s>"Plugin crashes should not crash the entire application" has been removed from Fx3, but needs to be part of Moz2 work.  Must ensure that this is added to their list. </s> ACTION: Tracked as part of Mozilla 2 work.
** 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"
** 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.
** RESOLVED

Latest revision as of 23:35, 30 April 2007

NOTE: COMPLETE or DELETE items have been removed from this list. If you think something has been missed, please ping Deb so it can be re-added. NEW: Grey background means the item is complete or no longer relevant.

Actions

Owner Category Action Status Notes

Completed Items

Owner Category Action Status Notes
Basil Sec, Priv Consult with lawyers re: Liability issues related to how we sell/promote "Private Browsing Mode" No liability issues per se but privacy policy needs to be updated to reflect new mode
Basil, Dria Gecko Follow up with AaronL re: Accessibility reqs for Fx3 COMPLETE 2 line items added to PRD in OS Integration section
Beltzner Add-ons Investigate removing extension installation whitelist, consulting with Dveditz COMPLETE whitelist will remain but UI will change such that it doesn't interrupt installation task flow and doesn't require users to add the site to the whitelist to continue, bug to be filed
Beltzner Help/Support "Showcase breadth of customization options + discoverability of customization" needs to be refined and turned into actionable line items COMPLETE see here
Beltzner, Rstrong Add-ons UI design required for addition of Add-ons prefs to prefs panel REMOVED Will be handled as part of feature design phase
Dria, Basil Places "UI for Export" - requirement involved with this to "Maintain existing bookmarks.html functionality (no new API or dataformats involved)" NO ACTION REQUIRED
Dria, Rstrong Add-ons Define additional Add-ons-related line items for PRD COMPLETE Items will be part of Feature plan, not PRD.
Unowned Gecko Investigate Web page archiving systems and devise an approach for sorting this out for Firefox (be it a Labs project or what-have-you) Deferred for now since it's a P3. If we decide to pick this up then we'll revisit how the feature is designed. Someone needs to sort out if this is in-scope for Fx3 or not. This needs an owner/driver. DECISION: Out-of-scope for Fx3
Vlad, Pav Gecko "Save web pages as PDF" COMPLETE No further PRD changes required.
Schrep Sec, Priv Set up meeting to get further definition of what "malware" means in terms of "Blacklisting malicious websites"
Schrep? OS Integration Airbag/Brakepad PRD line items need to be fleshed out by the Airbag/Brakepad team where required I've assigned this to Schrep, because it had no specific owner. If this is incorrect, please reassign.
Basil OS Integration "Vista Parental Controls Support" needs to be investigated in more depth. Completed Created a list of bugs - 355554, 355555, 372905, 372914, 372920
Beltzner Identity, Password Mgr Start a discussion thread re: third party Cardspace implementations in dev.planning Cancelled After discussion with Higgins team, determined that we'll do some Mozilla Labs postings to accelerate discussion of this topic.
Beltzner, Window Identity, Password Mgr Hand-off or complete discussion with Identity system developers re: how Firefox can better support those mechanisms (OpenID, Cardspace, etc) COMPLETE Started discussions with Higgins and OpenID, Cardspace is documented
Roc, Dbaron Gecko Specific line items for CSS 2.1 support are needed IN PROGRESS Dria has list and is getting it reviewed.
Roc, Dbaron Gecko Specific line items for CSS 3 support are needed IN PROGRESS Dria has list and is getting it reviewed.
Basil Identity, Password Mgr Talk to third parties doing Cardspace implementations and find out what's needed to support them as providers within Firefox
Dietrich Places "Places organizer redesign" needs to be investigated and turned into a set of requirements for the PRD as it's currently too vague - assigned to "Places team" IN PROGRESS Wiki here. Scoped to some high-priority items after discussion w/ mconnor. Need to meet w/ Beltzner to talk UI/UE for this.
Dria, Dbaron OS Integration Come up with a list of specific Linux issues that should be dealt with in Fx3 and add them to the PRD as FR line items Dropped Need to follow up.
Mconnor Con Handling Revisit Microformats items on PRD, revisit and reword to deemphasize "microformat" and focus more on generalizable system of inferred pieces of data, metadata, and other forms of structured information
Roc Gecko Offline apps - further investigation and refinement needed, specific line items required MEETING HELD Next step: going through meeting notes and extracting line items for PRD.
Basil Help/Support Find someone to own the whole Help/Support world Raised to management team JT Batson and others are investigating
Beltzner OS Integration Refine requirements and find a driver for "Version detection in Windows for theme installation piece" COMPLETED See here
Dmose Con Handling Firefox team needs to get a list of requirements together re: "Improve download handling", then make sure the Gecko team knows about and understands what's required on their part
Dmose Con Handling Refine what "Download manager can be extended in a way that feels tightly integrated" means
Basil Gecko Printing issues need to be clarified and better defined In Progress Basil is generating list, triaging critical bugs from this ugly list
Basil Con Handling Investigate bundling possibilities and options re: plugins for common formats Deferred due to goals/priorities exercise
Dmose Con Handling Investigate RSS enclosure handling and come up with a set of line items that should be added to the PRD Rolled into content handling spec
Dria, Shaver Add-ons Define additional Add-ons-related line items for PRD Met with shaver, have notes. Need to sort out what if anything needs to hit the PRD. Done.
Dria, Shaver, DevRel team Add-ons Figure out how to improve extension first-run experience and related API for extension developers. Met with shaver, have notes. Need to sort out what if anything needs to hit the PRD. Ext authors should be able to use the same model as Fx (notification system, UI flow). "Best practices" and evangelism required here as well. Done
Mconnor Identity, Password Mgr (P3) Write up a spec about how to do login through chrome rather than through a web page Deferred due to P3 priority.
Mconnor Help/Support Provide Visio for help/support flow Handling by JT Batson and customer working group. Deb assisting for Fx 3
Mconnor OS Integration Find someone to own defining what "Windows Group Policy Support" means in terms of line items, then get those items added to PRD Postponed due to lack of clear enterprise reqs in this area. Basic investigation shows that Active Directory (AD) integration is not as critical since selected enterprises use Fx as backup browser and don't want an AD dependency
Myk Search "Rich search results" needs to be more clearly defined and turned into a set of actionable line items updated and expanded proposal, including adding proposed PRD items.

Further Notes

  • "Alert user when they're providing info on a suspicious website" has been removed from the PRD but has been flagged as warranting follow up. This will be brought up in the Labs IdeaCenter forum when it is available.
  • "Plugin crashes should not crash the entire application" has been removed from Fx3, but needs to be part of Moz2 work. Must ensure that this is added to their list. ACTION: Tracked as part of Mozilla 2 work.
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox3/Firefox_Requirements_Meetings/Follow_up_Actions&oldid=55703"