Support/SUMOMigrationOrder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
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.
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 =
= Functional groups =
== Group 1: independent low risk ==
* Search UI
* Basic forums: Contributor, off topic, wiki articles ("discuss")
* Event signup system


== Group 2: infrastructure ==
== Group 1: independent low risk  ==
* 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 ==
*Search UI
* Support forum
*Basic forums: Contributor, off topic, wiki articles ("discuss")
* Sphinx indexer for support forum
*Event signup system


== Group 4: Wiki related ==
== Group 2: infrastructure  ==
* Wiki
* Sphinx indexer for wiki
* Wiki l10n
* API for wiki content


== Group 5: Dashboards and reporting ==
*Admin console: Initial setup, then admin for each component will be added when the component is added.
* Contributor dashboard
**User management
* Locale leader dashboard
**Basic forum management
* Metrics
**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 6: l10n ==
== Group 3: Forum related  ==
* gettext setup
* Locale leader dashboard
* l10n workflow


= Milestones =
*Support forum
== Milestone 1: Search and feedback ==
*Sphinx indexer for support forum
We will start with migrating some independent low risk items and the associated infrastructure. 


Our initial plan is to prototype these items in Django.
== Group 4: Wiki related  ==


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


===Timeline===
== Group 5: Dashboards and reporting  ==
* 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


== Milestone 2: Users and admin ==
*Contributor dashboard
* Users table, sessions, and user sync between old and new code
*Locale leader dashboard
* Basic admin console: search, users, new template management
*Metrics


===Timeline===
== Group 6: l10n  ==
* 3 weeks of development
* 2 weeks QA


== Milestone: gettext ==
*gettext setup
Set up gettext for UI items in new parts of interface.
*Locale leader dashboard
* gettext setup
*l10n workflow
* verbatim integration


===Timeline===
= Milestones  =
* 3-4 weeks development
* 2 weeks QA


== Milestone: support forums ==
== Milestone 1: Search and feedback  ==
[https://wiki.mozilla.org/Support/ForumRedesignPRD PRD]


Support forums are the main goal of this milestone.  Again, we will move over associated infrastructure
We will start with migrating some independent low risk items and the associated infrastructure.
* Support forums
 
* Feedback system for support forums
Our initial plan is to prototype these items in Django.
* Admin for support forums
 
* Sphinx indexer for support forums
*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 ===
=== Timeline ===
* 6 weeks of development with QA cycles as we go
* 2 weeks of QA


== Milestone: Wiki Part 1 ==
*5 weeks of development including associated tests
This milestone will focus on getting some infrastructure in place.
*Mid term review at 3 weeks to see if we are on track, what else we need, review scope, etc
* Wiki schema
*2 weeks QA
* Sync existing articles into new schema
 
* Display articles with new code; edit with old?
== Interlude ==
* Admin for wiki
* Review plans and timeline based on what we learned in Milestone 1
* Sphinx indexer for wiki
 
== 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 ===
=== Timeline ===
* 6-8 weeks of development
* 3 weeks QA


== Milestone: Wiki part 2==
*3 weeks of development
Focus on wiki and l10n workflow
*2 weeks QA
* New workflow for contribs and localizers
 
* Locale leader dashboard
== Milestone 3: gettext  ==
* Contributor dashboard
 
Set up gettext for UI items in new parts of interface.
 
*gettext setup
*verbatim integration


=== Timeline ===
=== Timeline ===
* 5 weeks of development
 
* 2 weeks QA
*3-4 weeks development
*2 weeks QA
 
== Milestone 4: support forums  ==
 
[https://wiki.mozilla.org/Support/ForumRedesignPRD 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

Revision as of 17:59, 12 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

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
  • 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
  • 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
Retrieved from "https://wiki.mozilla.org/index.php?title=Support/SUMOMigrationOrder&oldid=202067"