MozillaWiki

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

Page Discussion

Firefox3/Firefox Requirements Meetings/Follow up Actions (view source)

Revision as of 21:26, 22 February 2007

1,398 bytes removed ,  22 February 2007
m
no edit summary
mNo edit summary
Line 1: Line 1:
= Actions =
= Actions =


== Gecko Meeting ==
<table class="fullwidth-table">
* "Print layout should look like rendered layout"
<tr>
** Needs to be clarified and better defined - PRODUCTS TEAM
<th>Owner</th>
** Actual use cases and possible test cases are needed to figure out how this is broken
<th>Category</th>
* "Layout should be zoomed/cropped to fit desired page size"
<th>Action</th>
** Bug numbers needed or bugs need to be filed - ???
<th>Status</th>
* "Printed material should match user expectations"
<th>Notes</th>
** Needs to be more clearly defined - PRODUCTS TEAM
</tr>
*** STATUS: 02-20-07/Basil is generating list, triaging [http://tinyurl.com/362fkq critical bugs from this ugly list]
<tr>
* "Save web pages as PDF"
<td>Airbag Team</td>
** Vlad and Pav to investigate further - VLAD AND PAV OWN
<td>OS Integration</td>
* "Provide infrastructure for an extensible Web page archiving system"
<td>Airbag PRD line items need to be fleshed out where required</td>
** Someone needs to investigate how other browsers (ie5 on mac, omniweb, etc) approach this problem
<td></td>
** 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.
<td>Someone needs to own and drive this</td>
** Can we use [http://www.idpf.org/ocf/ocf1.0/index.htm OCF]?
</tr>
** UNOWNED - DRIA will follow up
<tr>
* "TTS/Screenreader support"
<td>Basil</td>
** 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.
<td>Gecko</td>
** DRIA OR BASIL TO FOLLOW UP WITH AARON
<td>Printing issues need to be clarified and better defined</td>
*** STATUS: Aaron has been contacted - two items to be added to the PRD
<td>In Progress</td>
* "CSS 2.1"
<td>Basil is generating list, triaging [http://tinyurl.com/362fkq critical bugs from this ugly list]</td>
** 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.
</tr>
** ROC
<tr>
* "CSS 3 features"
<td>Basil</td>
** As with CSS 2.1, specifics need to be sorted out and turned into trackable line items for the PRD.
<td>Identity, Password Mgr</td>
** ROC
<td>Talk to third parties doing Cardspace implementations and find out what's needed to support them as providers within Firefox</td>
* Offline apps
<td></td>
** Further investigation and refinement required.  Meeting needs to be scheduled.
<td></td>
*** STATUS: Meeting has been held, notes need to be gone through to see what needs to be added to the PRD -- CURRENTLY UNOWNED
</tr>
* (See one additional item regarding download in the Content Handling section below)
<tr>
<td>Basil</td>
<td>Sec, Priv</td>
<td>Consult with lawyers re: Liability issues related to how we sell/promote "Private Browsing Mode"</td>
<td>In progress</td>
<td></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></td>
</tr>
<tr>
<td>Basil</td>
<td>OS Integration</td>
<td>"Vista Parental Controls Support" needs to be investigated in more depth and turned into a set of actionable line items</td>
<td>In progress</td>
<td></td>
</tr>
<tr>
<td>Basil</td>
<td>Help/Support</td>
<td>Find someone to own the whole Help/Support world</td>
<td>Being escalated through Steering Committee</td>
<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. Larger project is out of band for Firefox 3 and needs to be taken on as a separate independent project.</td>
</tr>
<tr>
<td>Basil, Dria</td>
<td>Gecko</td>
<td>Follow up with AaronL re: Accessibility reqs for Fx3</td>
<td>DONE</td>
<td>2 line items added to PRD in OS Integration section</td>
</tr>
<tr>
<td>Beltzner</td>
<td>Add-ons</td>
<td>Investigate removing extension installation whitelist, consulting with Dveditz</td>
<td></td>
<td></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>ON HOLD</td>
<td></td>
</tr>
<tr>
<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></td>
<td></td>
</tr>
<tr>
<td>Beltzner</td>
<td>OS Integration</td>
<td>Refine requirements and find a driver for "Version detection in Windows for theme installation piece"</td>
<td></td>
<td>See OS Plat Int meeting notes for more info</td>
</tr>
<tr>
<td>Beltzner, Rstrong</td>
<td>Add-ons</td>
<td>UI design required for addition of Add-ons prefs to prefs panel</td>
<td>DELETE?</td>
<td></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></td>
<td></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></td>
</tr>
<tr>
<td>Dria, Basil</td>
<td>Places</td>
<td>"UI for Export" - CHANGE requirement involved with this to "Maintain existing bookmarks.html functionality (no new API or dataformats involved)"</td>
<td>Discussion Held + this decision was made</td>
<td>Needs to be added to PRD</td>
</tr>
<tr>
<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></td>
<td></td>
</tr>
<tr>
<td>Dria, Rstrong</td>
<td>Add-ons</td>
<td>Define additional Add-ons-related line items for PRD</td>
<td>MAIL RECEIVED</td>
<td>Next action: get items added</td>
</tr>
<tr>
<td>Dria, Shaver</td>
<td>Add-ons</td>
<td>Define additional Add-ons-related line items for PRD</td>
<td>MAIL SENT</td>
<td></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>MAIL SENT</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.</td>
</tr>
<tr>
<td>Mconnor</td>
<td>Identity, Password Mgr</td>
<td>Write up a spec about how to do login through chrome rather than through a web page</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Mconnor</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>Mconnor</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>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>
<tr>
<td>Mconnor</td>
<td>Help/Support</td>
<td>Provide Visio for help/support flow</td>
<td></td>
<td></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></td>
</tr>
<tr>
<td>Mconnor</td>
<td>OS Integration</td>
<td>Find an owner for "Get all Linux distros involved in Firefox development" - ubuntu, suse, redhat, fedora, etc</td>
<td></td>
<td></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></td>
</tr>
<tr>
<td>Places Team</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</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Roc</td>
<td>Gecko</td>
<td>Specific line items for CSS 2.1 support are needed</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Roc</td>
<td>Gecko</td>
<td>Specific line items for CSS 3 support are needed</td>
<td></td>
<td></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>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></td>
<td>Someone needs to sort out if this is in-scope for Fx3 or not.  This needs an owner/driver.</td>
</tr>
<tr>
<td>Unowned</td>
<td>Gecko</td>
<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 - someone needs to own this action.</td>
</tr>
<tr>
<td>Vlad, Pav</td>
<td>Gecko</td>
<td>"Save web pages as PDF"</td>
<td>In progress</td>
<td></td>
</tr>
</table>


== Add-ons Meeting ==
= FURTHER NOTES =
* "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.
**** STATUS: Follow-up mail sent to SHAVER, waiting on replay
* 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
*** STATUS: Mail sent to SHAVER, waiting on replay
** Rob Strong also has some items to add.  DRIA to follow up with RSTRONG.
*** STATUS: Mail sent to RSTRONG, waiting on replay
* 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 ==
* "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.
* Need to talk to Identity system developers (OpenID, Cardspace, etc) and figure out how Firefox can better support those mechanisms.
* "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.
** 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 ==
* "Play all popular media formats when plugins are installed"
** Follow up required here to investigate bundling possibilities and options.
*** BASIL will do follow up here
* "Plugin crashes should not crash the entire application"
** Must be added to Moz2 tracking
*** REMOVE from Fx3, move to Moz2
* Improve download handling
** Requires support from Gecko side, so this has to be discussed with the Platform team.
*** Add this to the GECKO bucket - eventually.
*** FIREFOX TEAM NEEDS TO GET A LIST OF REQUIREMENTS TOGETHER AND THEN MAKE SURE GECKO TEAM KNOWS ABOUT IT
* "Download manager can be extended in a way that feels tightly integrated"
** Requires further investigation and refinement
*** MCONNOR to follow up on this
* "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.
** All FRs/NFRs need to be revisited with this in mind
*** MCONNOR will take this for now
* 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.
*** DMOSE will investigate further in March
 
== Tabbed Browsing and Search Meeting ==
* "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.
*** MYK to come up with further examples, services, and details
 
== 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.
** 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.
*** Being escalaed through Steering Committee
* "Showcase breadth of customization options" - discoverability of customization
** Requires clearer definition in consultation with Beltzner
*** BELTZNER
* "Crash reporting"
** Requires follow up and refinement
*** REMOVE
 
== OS Platform Integration Meeting ==
* 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.
** 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 ==
* "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.
*** 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
Dria
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/49833"