Firefox3/Firefox Requirements Meetings/Places

« Firefox Requirements Meetings

Dial-in Info

• +1 650-215-1282x91 Conf# 8602 (US/INTL)
• +1 800-707-2533 (pin 369) Conf# 8602

Agenda

The following list is taken directly from the 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 an extensible bookmarks back-end platform
  • P1 FR - Provide platform support to enable syncing of Places datamodel object to a remote server
  • P1 FR - Places datamodel to support generic annotations
  • P1 FR - Protection and safeguarding against data loss
  • P1 NFR - Improve search, retrieval, startup performance
  • P1 FR - Allow users to tag/star bookmarks and history
  • P2 FR - Ability to add a note to a webpage which you can see again when you revisit that page
  • Px FR - Export/backup of all Places data model
  • P1 NFR - Ensure that Places includes a usable and Robust API for extensibility

• P3 - Unified user interface that improves the usability and discoverability of features
  • P1 FR - Parity with Firefox 2 Bookmarks/History UI
  • Px FR - Places organizer redesign

• P3 - Indexing of History
  • P3 FR - Index web page content into a DB that can be queried
  • P3 FR - Provide a UI for querying the DB
  • P3 NFR - History search should also use full text indexes to generate results

Notes

Item

• P1 - Provide an extensible bookmarks back-end platform
  • P1 FR - Provide platform support to enable syncing of Places datamodel object to a remote server
  • P1 FR - Places datamodel to support generic annotations
  • P1 FR - Protection and safeguarding against data loss
  • P1 NFR - Improve search, retrieval, startup performance
  • P1 FR - Allow users to tag/star bookmarks and history
  • P2 FR - Ability to add a note to a webpage which you can see again when you revisit that page
  • Px FR - Export/backup of all Places data model
  • P1 NFR - Ensure that Places includes a usable and Robust API for extensibility

Notes

• P1 #1 = toolkit layer thing
• P1 FR = this is just an event model and not the network infrastructure/sync layer, just the platform hooks. We are not building an actual sync client, just enabling other people to do so.
  • ADD: P3 FR "Build a sync client on this new infrastructure"
• "Places datamodel to support generic annotations" CHANGE TO "Provide platform support to support generic annotations"
• "Protection and safeguarding against data loss" = DELETE THIS, REPLACE WITH:
  • ADD NFR "P1 Bookmark data is never lost between browsing sessions"
  • ADD FR "P1 FR Provide backup and restore functionality for bookmarks" -- specifically better than the existing backup implementation, but defining this is unnecessary -- do we need to surface UI for this if we're going to fix the majority of the dataloss issues? Depends on risk tolerance.
    • Is there going to be UI for export?
• "Improve search..." - needs clarity CHANGE TO "Improve performance (as measured by memory use, transactional speed and Ts) of bookmark and history storage and retrieval operations"
• "tag/star" - this is a mixed metaphor, break out into 3 FRs which have been moved to the next section
  • Is "starring" any URI or already bookmarked items? -- any URI -- this is a way to flagging a URI as interesting
  • Is there a usecase for starring bookmarks as well as starring unbookmarked items? Are these competing classification systems?
  • starring/tagging is not the same as bookmarking
  • This discussion needs to be explored further in design -- FOLLOW UP REQUIRED
• "Add note" DELETE REPLACED WITH ABOVE
• "Export/backup of all Places data model" - DELETE
• P1 NFR (last one) stays as-is

Item

• P3 - Unified user interface that improves the usability and discoverability of features
  • P1 FR - Parity with Firefox 2 Bookmarks/History UI
  • Px FR - Places organizer redesign

Notes

• • "Places organizer redesign" -- this is too undefined to be useful.
  • "Parity..." requirement is important and stays as-is
  • Are there other specific requirements beyond the Fx2 parity that we need to call out specifically?
    • Managing your tagging, starring, and annotations...
    • MOVE THE FOLLOWING TO THIS SECTION
      • P1 FR - Provide some UI that allows users to mark a URI as "interesting"
      • P2 FR - Provide some UI that allows users to annotate a URI with tags
      • P3 FR - Provide some UI that allows users to annotate a URI with free-form notes
  • bump this whole section to P2

• • GENERAL NOTE: get rid of priorities on top level items that have FRs/NFRs and just leave them on FRs/NFRs.

Item

• P3 - Indexing of History
  • P3 FR - Index web page content into a DB that can be queried
  • P3 FR - Provide a UI for querying the DB
  • P3 NFR - History search should also use full text indexes to generate results

Notes

• • "Index web page content..." - stays as-is
  • "Provide UI for querying..." - CHANGE TO "Create an advanced search UI that allows users to search on all available URI metadata" - leave as P3
  • ADD "P3 FR - Support SQL queries of the bookmarks database in the Error Console"
  • "Provide a UI" - "DB" replaced with "Bookmarks, history, and page content where available"
  • LAST NFR gets DELETED

Additional items

• Send different user agent if an RSS item is being refreshed via Live Bookmark or if it's a new subscription. We apparently add something to the header for this already. Not currently sure what the motivation is here yet -- REQUIRES FOLLOW UP

• ADD: P1 FR Make it easy for users to export their bookmarks for use in another application (SECOND SECTION)