Support/SUMOMigrationOrder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 93: Line 93:
=== Timeline ===
=== Timeline ===


*3-4 weeks development  
*3-4 weeks development (start April 8?)
*2 weeks QA
*2 weeks QA



Revision as of 15:09, 17 February 2010

Functionality can be classed into a set of dependency groups. Note that some functionality will need to be done over several milestones, e.g. search.

Functional groups

Group 1: independent low risk

  • Search UI
  • Basic forums: Contributor, off topic, wiki articles ("discuss")
  • Event signup system

Group 2: infrastructure

  • Admin console: Initial setup, then admin for each component will be added when the component is added.
    • User management
    • Basic forum management
    • Support forum management
    • Search
    • Template management
    • Breadcrumbs
    • Categories
    • Feedback management
    • l10n control (create new locales, appoint locale leaders, manage translations
    • Tag management
  • Users table: Needs to be kept in sync with users_users for the time being, until we are completely out of tiki
  • Feedback system (formerly CSAT)
  • API
  • Tagging

Group 3: Forum related

  • Support forum
  • Sphinx indexer for support forum

Group 4: Wiki related

  • Wiki
  • Sphinx indexer for wiki
  • Wiki l10n
  • API for wiki content

Group 5: Dashboards and reporting

  • Contributor dashboard
  • Locale leader dashboard
  • Metrics

Group 6: l10n

  • gettext setup
  • Locale leader dashboard
  • l10n workflow

Milestones

Milestone 1: Search and feedback

We will start with migrating some independent low risk items and the associated infrastructure.

Our initial plan is to prototype these items in Django.

  • Search UI: none of the back end or indexing work.
  • Feedback system: We can rewrite this, put the data in new tables, and host the content in an iframe on wiki pages. Support/FeedbackSystem2PRD
  • Neither of these items requires migration of users table, will require some migration of templates, and understanding of Tiki sessions

Timeline

  • 5 weeks of development including associated tests
  • Mid term review at 3 weeks to see if we are on track, what else we need, review scope, etc
  • 2 weeks QA
  • Started week of Feb 8
  • Review week of March 1

Interlude

  • Review plans and timeline based on what we learned in Milestone 1

Milestone 2: Users and admin

  • Users table, sessions, and user sync between old and new code
  • Basic admin console: search, users, new template management

Timeline

  • 3 weeks of development (start March 15?)
  • 2 weeks QA

Milestone 3: gettext

Set up gettext for UI items in new parts of interface.

  • gettext setup
  • verbatim integration

Timeline

  • 3-4 weeks development (start April 8?)
  • 2 weeks QA

Milestone 4: support forums

PRD

Support forums are the main goal of this milestone. Again, we will move over associated infrastructure

  • Support forums
  • Feedback system for support forums
  • Admin for support forums
  • Sphinx indexer for support forums

Timeline

  • 6 weeks of development with QA cycles as we go
  • 2 weeks of QA

Milestone 5: Wiki Part 1

This milestone will focus on getting some infrastructure in place.

  • Wiki schema
  • Sync existing articles into new schema
  • Display articles with new code; edit with old?
  • Admin for wiki
  • Sphinx indexer for wiki

Timeline

  • 6-8 weeks of development
  • 3 weeks QA

Milestone 6: Wiki part 2

Focus on wiki and l10n workflow

  • New workflow for contribs and localizers
  • Locale leader dashboard
  • Contributor dashboard

Timeline

  • 5 weeks of development
  • 2 weeks QA

Future Milestones

  • Any remaining functionality
  • New features