Support/Kitsune/Thunderbird-integration: Difference between revisions

 
(18 intermediate revisions by 2 users not shown)
Line 10: Line 10:
* 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, including images and templates
* How feasible is moving over articles from SUMOMO, including images and templates
** seems very doable, based on documentation and a chat between developers: the changes between SUMO and SUMOMO are documented [https://wiki.mozilla.org/Thunderbird/Support/sumomoModsToKitsuneKB here]
* {{bug|754439}} is a bug to create a SuMoMo database dump so that a more detailed investigation can be done


==Definition==
==Definition==
Line 40: Line 42:
* Faceted search to distinguish between products
* Faceted search to distinguish between products
* Forums that are browsable by product
* Forums that are browsable by product
* SuMoMo Migration: NB -  Migrations are messy and imperfect so we'll do our best in code and the rest will be done by humans before going live if possible! (not going to migrate Get Satisfaction  Data, GS migration if any belongs to a future phase TBD; for this phase GS forums may continue to exist unchanged)
* Showfor support for Thunderbird - perhaps as easy as productizing :sancus's showfor thunderbird modifications that are currently working on SuMoMo
** Articles, Images, Videos
 
*** History: don't bring over, just bring over a list of users who have contributed to an article
====SuMoMo Migration====
*** Title - if the title is identical to existing SuMo article title then i) don't migrate but save the article and metadata to a file OR ii) tag or keyword it thunderbird or add "Thunderbird" to the end of the title and then migrate it
:Sancus has agreed informally to help do the migration in Q1 2014. We'll verify that once we get closer to the date!
*** Other Metadata - keywords, etc: just bring over unchanged if possible, if not delete it during migration (of course keep a backup)
 
** Users (only migrate users who have created or localized articles or created images or video)
NB -  Migrations are messy and imperfect so we'll do our best in code and the rest will be done by humans before going live if possible! (not going to migrate Get Satisfaction  Data, GS migration if any belongs to a future phase TBD; for this phase GS forums may continue to exist unchanged)
*** if the SuMoMo username is identical to an existing username and email address in SuMo, assume that it's the same person and don't migrate it otherwise migrate (and of course keep a backup) - Roland will manually check this on staging (assuming this is possible) before we go live
* Articles, Images, Videos
** Articles:
*** <del>History, Ideally: migrate the whole article with history and match users with existing SUMO users or create them</del>
*** History, Fallback: Only migrate the latest revision. Provide a list of users who have contributed to an article - :sancus to write a script to add the users to the contribution field (or if that's not possible we can use a keyboard automation utility to drive firefox to do this manually)
*** Title - if the title is identical to existing SuMo article title then add "Thunderbird" to the end of the title and if possible tag or keyword it thunderbird ; SUMO developers to provide a list of naming collisions so that Roland can manually double check this
*** Other Metadata <del>- keywords, etc: just bring over unchanged if possible, if not delete it during migration</del> Please do not migrate other metadata please (of course keep a backup)
** Images, Videos: Migrate and if there is a collision, add "thunderbird" to the name. Provide a list of the collisions for manual repair post migration
** showfor - if there are any articles with '''pre tb 17 showfor''', please provide a list and Roland will correct manually post migration
* Users <del>- only migrate users that have edited articles. If we go with fallback,</del> Please don't migrate any users.
* KB Article Forum content - don't migrate


===Non-Goals===
===Non-Goals===
Line 66: Line 77:
We can do a move in 2 phases:
We can do a move in 2 phases:
* 1st phase:
* 1st phase:
** offer contributor dashboards separated by product
** offer faceted search
** Move over articles
** Move over articles
** offer faceted search
** offer contributor dashboards separated by product


* 2nd phase:
* 2nd phase:
** offer user to user support for more than one product
** offer user to user support for more than one product
== Standard Rationale ==
(so that Thunderbird KB integration follows the same format as all other features)
=== Title ===
Integrate the Thunderbird Knowledge Base into the SUMO Knowledge Base
=== Problem Statement / Description ===
Users only see one Mozilla and are confused by the fact that the Thunderbird Knowledge Base and Support Forums are not integrated with Firefox and vice-versa. This was confirmed by Susan's IA user study.
=== Measureable Outcome ===
* Reduced user confusion
* More contributors since this means we will have single sign-on for the Knowledge Base (instead of 2 today) and therefore Thunderbird contributors will be able to cross-over into Firefox seamlessly and vice-versa
=== Solutions ===
Integrate Thunderbird KB into SUMO as described by the remainder of this wiki page; any other solution is non elegant and long term leads to more developer effort.
Confirmed users
5,365

edits