Support/Q42009 Goals: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
{{DRAFT}}
{{DRAFT}}


=Proposed Q4 SUMO Goals=
== Upstream SUMO patches to TikiWiki ==
* [https://wiki.mozilla.org/Support/TikiUpstreamPlanning Planning]


== Upgrade Sphinx search engine==
=High-level SUMO Focus of Q4=
The over-arching theme of our focus in Q4 can be summarized as:
 
== Paving the way for a better SUMO platform ==
SUMO is build on a two-year-old version of TikiWiki (version 1.10, a beta version). The immaturity of the platform has made it more complicated to add new features to SUMO and we have instead spent a great deal of our time working on performance and security improvements and bug fixes. In order to build a better foundation for SUMO, we need to upgrade and ultimately rewrite parts of the platform to ensure higher code quality and happier SUMO developers.
 
The goals of Q4 are just the first steps in the effort to improve the SUMO platform. However, during this effort, we will go from a "consumer" to an active participant of the Tiki community, which will hopefully lead to a much stronger collaboration.
 
The next steps would then be to [https://wiki.mozilla.org/Support/TikiWikiUpgrade upgrade to Tiki 4.1/5.1] and rewrite the bad parts of the platform to improve code quality. However, these steps are unlikely to happen in Q4 given our limited time and resources.
 
== Growing our SUMO community ==
 
This has been an ongoing focus of the SUMO project in 2009 and will continue to be the case in 2010: a healthy and strong support community paves the way for a good web experience for our users. The specific focus in Q4 should be to fix bugs and add features to SUMO that has the strongest potential of having a positive impact on the community volunteers' experience on the platform.
 
The SUMO team will work on identifying this list of bugs together with the community. Special consideration should be given to bugs/features reported by or confirmed to be frustrating/lacking and as such making it harder to use the support platform.
 
We also see opportunities of community growth in the upcoming Firefox Support for Mobile website, which means that bugs related to this SUMO-powered support website should be taken into consideration as well.
 
=Proposed SUMO Q4 Goals=
== A. Upstream SUMO patches to TikiWiki ==
* See the [https://wiki.mozilla.org/Support/TikiUpstreamPlanning proposed plan]. If needed, this goal could be further split up into:
** a1) Upstream major SUMO features to TikiWiki -- this would include the features listed under [https://wiki.mozilla.org/Support/TikiUpstreamTriage#Features_.2F_enhancements_that_should_go_to_Tiki Features / enhancements that should go to Tiki]
** a2) Upstream remaining SUMO patches to TikiWiki -- this would include all other bug fixes/changes that would be needed in TikiWiki in order to successfully upgrade SUMO to Tiki 4.1/5.1 in the future.
 
By splitting the goal up into two sub-goals, we could give them different priorities and allow goals B and C below take priority over a2 (or even move a2 to Q1 2010).
 
== B. Upgrade Sphinx search engine==
AMO is running the newer version.  This also entails a rewrite of the way we do indexing - we can shed the XML generation and speed up indexing which will allow us to reindex more often, improving user experience and decreasing machine load.
AMO is running the newer version.  This also entails a rewrite of the way we do indexing - we can shed the XML generation and speed up indexing which will allow us to reindex more often, improving user experience and decreasing machine load.


== Do one maintenance release ==
== C. Community-focused release ==
The scope of this should be carefully controlled.  Based on experiences in q1 and Q3, we should limit this release to approximately 30 bugs.  Prioritization can be done by the SUMO team.  Suggest focus on:
The scope of this should be carefully controlled.  Based on experiences in q1 and Q3, we should limit this release to approximately 30 bugs.  Prioritization can be done by the SUMO team.  Suggest focus on:
*Fix remaining high priority ForumUX bugs that were pushed out of 1.4.
*Fix remaining high priority ForumUX bugs that were pushed out of 1.4.
*Fix a controlled number of other long term bugs (e.g. l10n related)
*Fix a controlled number of other long term bugs (e.g. l10n related)
This goal could also be split up into two separate goals in order to increase focus and reduce risk of defining ambiguous goals.
1,623

edits

Navigation menu