Support/Kitsune/Thunderbird-integration: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 9: Line 9:
==Open issues/risks==
==Open issues/risks==
* Very high effort for only one product, probably only makes sense to go this way once we have to support more products.
* Very high effort for only one product, probably only makes sense to go this way once we have to support more products.
* How feasible is moving over articles from SUMOMO?
* How feasible is moving over articles from SUMOMO, including images and templates?
 
We can do a move in phases:
* 1st phase:
** Move over articles
** offer faceted search
** offer contributor dashboards separated by product
 
* 2nd phase:
* offer forum for more than product


==Definition==
==Definition==

Revision as of 14:07, 18 April 2012

Purpose

  • Reduce the maintenance costs of the two installations of SUMO for Firefox and Thunderbird.
  • Reducing user confusion since search from the start page currently only shows Firefox results.

Outcome

  • One installation with one database, a unified search.


Open issues/risks

  • Very high effort for only one product, probably only makes sense to go this way once we have to support more products.
  • How feasible is moving over articles from SUMOMO, including images and templates?

We can do a move in phases:

  • 1st phase:
    • Move over articles
    • offer faceted search
    • offer contributor dashboards separated by product
  • 2nd phase:
  • offer forum for more than product

Definition

Feature overview

  • Need to show dashboards independently for products.
    • KB dashboard
    • L10n dashboard
    • KPI dashboard
    • Karma dashboard
  • Needs KB article discussions overview for separate products
  • Needs faceted search to distinguish between products
  • Needs clearly separated forums


Users & use cases

Dependencies

Requirements

Non-Goals

Design

Functional Spec

What contributors should do

Things that will need to be figured out

User experience design

Implementation plan