Support/Kitsune/Thunderbird-integration: Difference between revisions

 
(5 intermediate revisions by the same user not shown)
Line 45: Line 45:


====SuMoMo Migration====
====SuMoMo Migration====
:Sancus has agreed informally to help do the migration in Q1 2014. We'll verify that once we get closer to the date!
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)
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)
* Articles, Images, Videos
* Articles, Images, Videos
** Articles:  
** Articles:  
*** History, Ideally: migrate the whole article with history and match users with existing SUMO users or create them,
*** <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)
*** 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
*** 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 - keywords, etc: just bring over unchanged if possible, if not delete it during migration (of course keep a backup)
*** 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 with the collisions for manual repair.
** 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
* Users - only migrate users that have edited articles. If we go with fallback, don't migrate any users.
** 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
* KB Article Forum content - don't migrate


Line 90: Line 93:


* Reduced user confusion
* Reduced user confusion
* More contributors since we have only one support userid and Thunderbird contributors will be able to cross-over into Firefox seamlessly and vice-versa
* 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 ===
=== 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.
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