Transition help.ubuntu.com to SUMO

Registered by Benjamin Kerensa

This blueprint has been superseded. See the newer blueprint "Shaping a plan for the future of Ubuntu Documentation Team" for updated plans.

Mozilla SUMO is the product that powers support.mozilla.org and we are aiming to transition help.ubuntu.com in its entirety to SUMO in the Q-Cycle or at the very least get excellent work done towards that goal.

Blueprint information

Status:
Complete
Approver:
Jono Bacon
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Benjamin Kerensa
Definition:
Superseded
Series goal:
Proposed for quantal
Implementation:
Needs Infrastructure
Milestone target:
None
Started by
Benjamin Kerensa
Completed by
Benjamin Kerensa

Related branches

Sprints

Whiteboard

Evaluating SUMO to be the portal to find user help for Ubuntu on help.ubuntu.com (starting with community docs)
The official Ubuntu Docs generated from the ubuntu-docs package could still be hosted there (e.g. h.u.c/12.04/index.html)

Previous discussion on the ubuntu-docs mailing list:
https://lists.ubuntu.com/archives/ubuntu-doc/2012-February/016330.html
https://lists.ubuntu.com/archives/ubuntu-doc/2012-February/016358.html
https://lists.ubuntu.com/archives/ubuntu-doc/2012-February/016362.html

Mozilla very excited about Ubuntu using it, and very cooperative and willing to fix things if needed

Benefits:
Much easier to contribute to
Much richer in terms of finding the information you need
In-built localization support to show help in everyone's language
Actively Developed with Bright Roadmap

Challenges:
Moderation is only language-based

IDEAS:
Tracking Lifecycle of Documentation (How do we have automation for ensuring fresh content)
https://wiki.ubuntu.com/ubuntu-support-and-learning-center ?
make 'do not import', 'obsolete', etc. tags for documentation on '/community'

DOCS: http://kitsune.readthedocs.org/en/latest/index.html
Upstream roadmap: https://wiki.mozilla.org/Support/Kitsune/Roadmap2012

(?)

Work Items

Work items:
[cprofitt] Write a blog post about SUMO: TODO
[mhall119] Deploy SUMO beta-testing instance on EC2: TODO
[mhall119] File RT with IS to get a permanent home for SUMO: TODO
[bkerensa] Develop deployment plan for IS (possibly using juju): TODO
[bkerensa] Develop deployment plan for IS (possibly using juju): TODO
Discuss theming work with design team: TODO
[cprofitt] determine if it is feasible to review current documentation to mark as 'do not import': TODO
[daker] Create script to migrate content from moin to SUMO: TODO