Thunderbird/MovingSuMoMoToMozillaDotOrg

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

This is a draft web page for discussion only. It will be superseded by bugs in bugzilla and other web pages which will NOT be labelled DRAFT

Context:

Now that Mozilla Messaging is part of Mozilla Corporation, it doesn't make sense to have separate mozillamessaging.com websites and collateral. Therefore it doesn't make sense to have SuMoMo, i.e. the Mozilla Thunderbird Support Knowledge Base at support.mozillamessaging.com

Accordingly, we would like to move support.mozillamessaging.com elsewhere as soon as possible.

Ideal Scenario: support.mozilla.org/<locale>/thunderbird w/SSO

move to support.mozilla.org/<locale>/thunderbird with "support" single sign on

• SuMoMo moves to support.mozilla.org/en-US/thunderbird
• Single Sign on for all support websites for all verticals: Firefox, Firefox Mobile, Sync and Thunderbird

Pros:

1. Big win for users!

Cons:

1. requires a single Kitsune consolidated "super-instance" to handle all four verticals which Kitsune is not currently designed for (NB(james) we already have 3 of these, and will presumably also be dealing with other services and somehow with Apps eventually. To support more products, there are changes we can make but we don't have to.)
2. we're not YET ready to merge Thunderbird support into SUMO which handles the other three verticals
3. considerable implementation cost for the SUMO dev and SUMO teams as well as Thunderbird teams but this kind of work needs to be done eventually for Mobile, and Sync and eventually Apps as well

proxy: support.mozilla.org/thunderbird/<locale> to existing momo server

• SuMoMo moves to support.mozilla.org/thunderbird/en-US which proxies to a separate TB Kitsune instance from the Firefox Kitsune instance

Pros:

1. Minimizes development cost to SUMO dev team
2. Since Thunderbird and Firefox are still running separate Kitsune instances, data is separated so nothing needs to change in the day to day running of the Kitsune instances

Cons:

1. Potentially confusing to users but still less confusing than mozillamessaging.com
2. No support single sign on i.e. different userids for support of Firefox and support of Thunderbird which is the case today
3. Ugly re-direct rules and urls will change when we move to support.mozilla.org/<locale>/Thunderbird
4. proxying is slow

interim solution: move to other mozilla.org subdomain

e.g. thunderbird-support.mozilla.org

Pros:

1. can be done very quickly
2. no dev impact to SUMO team
3. no dev required for Kitsune

Cons

1. Yet another subdomain for mozilla.org which will have to be approved by the "one mozilla" team