= Coordination page for http://tiki-trunk.mozilla.com/ testers.=

== Background ==
tiki-trunk.mozilla.com contains real SUMO data from November 2009, on a environment similar (same?) to the real thing. The code will soon be updated daily from Tiki trunk

== Notes ==

=== 2009-12-28 ===
* http://tiki-trunk.mozilla.com/ is now testable
** Very soon, automatic svn upgrades will be sorted (and we'll have revision number if bottom bar)
** However, http://tiki-trunk.mozilla.com/tiki-admin.php "reports Database Version Problem"
*I get logged out every once in a while. Perhaps the load balancers?

== Some things to think about ==

*plugins need to be re-created (keyboard, etc)
*Need to know last date of update
** If site is updated via doc/devtools/svnup.sh, the version number will appear in the footer. ex.: "Last update from SVN(4.0): Monday 07 December, 2009 19:53:19 UTC - REV 23720"

2009-10-03T00:06:05Z

MarcLaporte: /* tiki_triage */ me!

= Tiki Upstream Planning =

Looking so far, my very rough, unscientific estimate is that a good day is getting two patches committed. More likely is less than 1.5 on average, to manually resolve conflicts, merge, and do enough BFT to know it's not completely broken.

One wrench in the estimation is that of the almost 900 or so closed (reso fixed or veri fixed) SUMO bugs [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&component=Forum&component=General&component=Knowledge+Base+Software&component=Localization&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=], only around 200 have been triaged so far. I'll deal with this below.

== Breakdown of triaged bugs ==

'''Bold''' are blockers in bugzilla.

=== tiki_feature ===

* '''[https://bugzilla.mozilla.org/show_bug.cgi?id=398246 Bug 398246]''' - no patches or revisions, partially server configurations
* [https://bugzilla.mozilla.org/show_bug.cgi?id=395271 Bug 395271] - patch
* [https://bugzilla.mozilla.org/show_bug.cgi?id=480223 Bug 480223] - revision number
* [https://bugzilla.mozilla.org/show_bug.cgi?id=465518 Bug 465518] - patches
* '''[https://bugzilla.mozilla.org/show_bug.cgi?id=412265 Bug 412265]''' - no patches or revision
* [https://bugzilla.mozilla.org/show_bug.cgi?id=441858 Bug 441858] - patch
* [https://bugzilla.mozilla.org/show_bug.cgi?id=506547 Bug 506547] - patch
* [https://bugzilla.mozilla.org/show_bug.cgi?id=433341 Bug 433341] - patch
* [https://bugzilla.mozilla.org/show_bug.cgi?id=436679 Bug 436679] - patch
* [https://bugzilla.mozilla.org/show_bug.cgi?id=429784 Bug 429784] - revisions
* [https://bugzilla.mozilla.org/show_bug.cgi?id=498001 Bug 498001] - patch, revisions
* [https://bugzilla.mozilla.org/show_bug.cgi?id=492697 Bug 492697] - patch, revisions, parallel work in tiki
* [https://bugzilla.mozilla.org/show_bug.cgi?id=452830 Bug 452830] - patch, sql
* [https://bugzilla.mozilla.org/show_bug.cgi?id=465029 Bug 465029] - patch, revision
* [https://bugzilla.mozilla.org/show_bug.cgi?id=509864 Bug 509864] - patch, revision

=== tiki_bug ===

* [https://bugzilla.mozilla.org/show_bug.cgi?id=514244 Bug 514244] - NEW, untargeted
* [https://bugzilla.mozilla.org/show_bug.cgi?id=429529 Bug 429529] - patch, revision
* [https://bugzilla.mozilla.org/show_bug.cgi?id=512120 Bug 512120] - patch, not in SVN
* [https://bugzilla.mozilla.org/show_bug.cgi?id=485557 Bug 485557] - revision, possibly fixed in tiki
* '''[https://bugzilla.mozilla.org/show_bug.cgi?id=484100 Bug 484100]''' - patch, revisions

=== tiki_fixed ===

[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_fixed&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 21 bugs]. At some point, will need to check that implementations are compatible.

=== tiki_triage ===

[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 38 bugs]. Not sure who's on this. ''marclaporte'' is on this but needs new categories (as discussed on sumo-dev-list)

== Untriaged bugs ==

A bugzilla search for closed (veri fixed or reso fixed) bugs in SUMO excluding Chat and Mobile yields 885 bugs ([https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&component=Forum&component=General&component=Knowledge+Base+Software&component=Localization&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=]).

Using the current percentages as a guide, there's a rough estimate of around 85 bugs to upstream, instead of the 20 we have triaged so far.

{|border=1|
!Component!!Triaged Bugs!!% of all Triaged Bugs!!Estimated total (% * 885)
|-
|tiki_feature||15||7.18%||64
|-
|tiki_bug||5||2.39%||21
|-
|tiki_triage||38||18.18%||161
|-
|tiki_fixed||21||10.05%||89
|-
|sumo_triage||15||7.18%||64
|-
|sumo_only||115||55.02%||487
|}

That would also leave around 160 bugs to check in Tiki.

= Timeline =
With an estimate of 85 bugs to upstream at ~1.5 bugs per day, that's 57 days of dev time, or around 11 weeks.

Resource wise, this corresponds with the initial estimate of one dev for a full quarter. We may also be able to get help from the Tiki community with this task.

The bug triage needs to be finished as quickly as possible so this estimate can be firmed up.

==Questions==
* How many of the triaged/untriaged bugs are just trackers? How many are much bigger/smaller that the 1.5 a day rate?
* How likely is it that the Tiki community would consider either a) holding 4.0 for our upstreamed patches or b) finding contributors to get these patches into 4.0 or c) a combination of both>

Support/TikiWikiUpgrade

2009-09-26T02:40:53Z

MarcLaporte: /* Upgrade */ Morgamic, Laura, James, David, Paul

Support/UpgradeToTiki4/ThemeCoordination

2009-09-24T23:31:25Z

MarcLaporte: /* Breadcrumbs */

About the theme so far...

== Code ==
An experimental branch has been created:
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/experimental/sumo/

== In action ==
In action:
http://sumo.ourwiki.net

== People ==
*Gary
*luci
*Marc
*you?

== Stylesheets ==

There are two basic looks (that I've found so far):
* "Top pages" like the site index page and the top forum page ([http://support.mozilla.com/en-US/kb/Support+Website+Forums]). These have an intro statement and the logo/searchform. The darker blue background extends further down the page to underly this additional content.
* "Normal pages" like, for example, this one. Here the darker background image is positioned higher on the page since the logo/searchform aren't present.

One theme - moz4.css - is the default, and its theme option, moz4intro.css, is for introductory pages such as the site index page. This way they can share any modified templates. (This is an update from the previous arrangement - see the page history for details.) The theme option is assigned to a category "Intro_pages" using the Template Manager (set on a category basis; my first idea was to set the theme option on an object basis but it seems this isn't possible, maybe due to an oversight when the theme options feature was added.)

SUMO currently uses some YUI ([http://developer.yahoo.com/yui/grids/]) methods to reset properties, etc. I'm not really familiar enough with those to implement them here, so have used the ways I know. Probably this can be adjusted if the SUMO people want to do that.

== Templates ==
My goal was to have as little template customization as possible, of course. But I think it's not possible to avoid that altogether. Already, to produce the fixed-width aspects of the pages, I modified tiki.tpl to move the end of div#main above the bottom-bar area so that #main can be narrowed and the footer can be full width.

<blockquote>Regarding: ''"I think it'll also be necessary to modify tiki.tpl to add divs for the bracket images that display above and below the content"'' luci says:

Ideas:

*IMHO you don't have to modify tiki.tpl. Just try to use the layoutshadows feature in Look & Feel
** gary replies: You're right, luci. I turned on the layoutshadows for the extra divs, and used them for the bracket images. Thanks.</blockquote>

I didn't get that far yet, but probably tiki-showpage.tpl will need to be modified also, along with forum tpls.

== Top menu ==
Still details to finish up, but Superfish does a good job replicating the original top menu appearance and function.

== Custom center column heading ==
We talked about this some time ago, and this is a perfect use case. I commit the change today (r21258), and replaced the related files at this site. So "Top pages" use this Look and Feel option. So far, there's just the HTML from the SUMO site pasted in (to produce the site index content), but the forum-top and other top pages (I haven't explored yet to find them) will need either their content pasted in, or maybe the L and F textarea should contain logic to load menupages or something, for the various pages that need the content.

== Footer ==
The L and F bottom bar custom content feature is used for the footer content. This displays the "Switch Language" module floated right and a menupage module (calling page "moz4_footer_menus") floated left, followed by the "about" and "powered by" lines in a div.

<blockquote>Regarding: ''"Aside regarding module names - not about this project - I'm having problems with module names in trunk, maybe due to the work going on with them now. At my wamp install (SVN-upped), the module name menupage works, but at this site I get an error (as can be seen). So looks like one way or another this site should get updated."'' luci says:

Ideas:

*Fixed here. It has to be lowercase "menupage", not "Menupage".</blockquote>

The module names are pretty chaotic right now in trunk IMO and should be systematized some way, I think. I got the switch-language module to work in a module wikiplugin by using the name "switchlang", but there's no indication on the module admin page that this is the name to use (it's listed there as "Switch Language").

== Columns ==
Only the center and right columns are used. I made "Firefox Support" a normal user module and put it at the top of the right column (its top item still needs styling).

== Breadcrumbs ==
The SUMO site uses breadcrumbs, so I turned this feature on here. A problem is that our breacrumbs (neglected feature) only produces links, and these should be in a div, so this should be corrected in the breadcrumb.lib code, for better white space. Also a method is needed to not have the breadcrumbs appear on certain pages. If every page's body tag could be given a class or id similar to every module's div.box tag, then CSS could be used for this.
ML: SUMO fixed breadcrumbs or put content in such a way to simulate content? We should take this opportunity to either fix or remove breadcrumbs :-)

== HomePage page title ==
Not just about this site, but also needed for this site, I've long thought that there should be an admin option to turn off the display of the text "HomePage". Displaying that is fine on an info wiki, but looks very 1990s on most other types of web sites. There are workarounds, like using page descriptions for page titles, but there should be a direct admin solution IMO.

Similarly, refreshing the page by clicking on the page title should be an option IMO, similar to "double-click page to edit", etc.

== Reimplementing SUMO interface parts ==
The wiki action icons, etc., are in a visually distinct box, so this will need to be done.

Please give your input, of course. :-)

Support/Editor:PRD

2009-09-24T14:50:17Z

MarcLaporte: /* Technical Requirements */

Firefox Support Knowledge Base Editor Requirements Document

=Overview=
Intuitive and simplified Knowledge Base article editor.

==Permissions==
* When creating a new article, all options are available.
* After an article has been created, only an admin can change the language.
* When editing an article only locale leaders and admins can change an article category. (Staging area, Knowledge Base, Live Chat, etc.)
* When editing a staging copy, category cannot be changed.

==Fields that require entered data==
* Language
* Summarize your edit and cite a reference

=Options=
* Language: drop-down menu to select language (unknown language not allowed)
* Category:
** Administration (only available to admins and locale leaders)
** How to contribute (only available to admins, locale leaders, and approvers)
** Live Chat
** Knowledge Base (only available to admins, locale leaders, and approvers)
** Staging Area
** Sandbox/Testing Area
* This article applies to:
** Firefox 2 - The content of this article applies to users of Firefox 2.x.
** Firefox 3.0 - The content of this article applies to users of Firefox 3.0.x.
** Firefox 3.1 - The content of this article applies to users of Firefox 3.1
* Type of article:
** Help article - This article is a reference chart, tutorial, or a how-to article.
** Troubleshooting article - This article is for solving a problem.
* Summarize your edit and cite a reference:
** Mark other translations as out of date (only available on English articles)

==Toolbar items==
* Bold
* Italics
* Wiki link
* External link
* Numbered list
* List
* H1
* H2
* H3
* Menu path
* Button
* Kbd
* File name/path
* Pref name/value
* Code
* Note
* Warning
* Insert Image (will pop up prompt for:)
** Image uploader (mandatory)
** Image height
** Image width
** Alignment
* SHOWFOR (will trigger a drop-down, that includes:)
** Windows
** Mac
** Linux
** Windows and Mac
** Windows and Linux
** Mac and Linux
** –separator–
** Firefox 3.1
** Firefox 3.0
** Firefox 3.0 and 3.1
** Firefox 2
* Dynamic Content (will trigger a drop-down that includes all content labels for the language assigned to the article)

==Viewing options==
Tabs at the bottom of content area will choose what you view.
* Windows
* Mac
* Linux
* Source (if you want to edit the tikiwiki markup)

=Mockups=
The top of the editor will contain a warning that content needs to be reviewed before being applied to the Knowledge Base, and provide links to best practices, style guide, and policies page.
* [http://ilias.ca/sumo/creating_an_article.xhtml Creating a new article]
* [http://ilias.ca/sumo/staging_copy_non-locale_leader.xhtml Editing a staging copy]

=Technical Requirements=
* WYSIWYG editor {{bug|454131}}
* Adding and removing tags should not be part of the article editor
* Dynamic content blocks should be part of the editor toolbar as a quickpaste function. {{bug|446078}}
* Buttons on the editor toolbar for applying SHOWFOR. {{bug|446076}}
* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.
* Create or find icons for the editor toolbar that are easily interpretable.
* The image upload feature should be part of the editor toolbar, just like in Wordpress. {{bug|398767}}
* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug|446072}}
* Get rid of the category selector on staging copies.
* Relabel "Edit Summary" in editor and add something to it about citing a reference. {{bug|446070}}
* Re-arrange items in editor {{bug|428073}}
* Add links to best practices, style guide, and policies at the top of the editor {{bug|446071}}

Support/UpgradeToTiki4/ThemeCoordination

2009-09-24T08:54:46Z

MarcLaporte: /* Code */

About the theme so far...

== Code ==
An experimental branch has been created:
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/experimental/sumo/

== In action ==
In action:
http://sumo.ourwiki.net

== People ==
*Gary
*luci
*Marc
*you?

== Stylesheets ==

There are two basic looks (that I've found so far):
* "Top pages" like the site index page and the top forum page ([http://support.mozilla.com/en-US/kb/Support+Website+Forums]). These have an intro statement and the logo/searchform. The darker blue background extends further down the page to underly this additional content.
* "Normal pages" like, for example, this one. Here the darker background image is positioned higher on the page since the logo/searchform aren't present.

One theme - moz4.css - is the default, and its theme option, moz4intro.css, is for introductory pages such as the site index page. This way they can share any modified templates. (This is an update from the previous arrangement - see the page history for details.) The theme option is assigned to a category "Intro_pages" using the Template Manager (set on a category basis; my first idea was to set the theme option on an object basis but it seems this isn't possible, maybe due to an oversight when the theme options feature was added.)

SUMO currently uses some YUI ([http://developer.yahoo.com/yui/grids/]) methods to reset properties, etc. I'm not really familiar enough with those to implement them here, so have used the ways I know. Probably this can be adjusted if the SUMO people want to do that.

== Templates ==
My goal was to have as little template customization as possible, of course. But I think it's not possible to avoid that altogether. Already, to produce the fixed-width aspects of the pages, I modified tiki.tpl to move the end of div#main above the bottom-bar area so that #main can be narrowed and the footer can be full width.

<blockquote>Regarding: ''"I think it'll also be necessary to modify tiki.tpl to add divs for the bracket images that display above and below the content"'' luci says:

Ideas:

*IMHO you don't have to modify tiki.tpl. Just try to use the layoutshadows feature in Look & Feel
** gary replies: You're right, luci. I turned on the layoutshadows for the extra divs, and used them for the bracket images. Thanks.</blockquote>

I didn't get that far yet, but probably tiki-showpage.tpl will need to be modified also, along with forum tpls.

== Top menu ==
Still details to finish up, but Superfish does a good job replicating the original top menu appearance and function.

== Custom center column heading ==
We talked about this some time ago, and this is a perfect use case. I commit the change today (r21258), and replaced the related files at this site. So "Top pages" use this Look and Feel option. So far, there's just the HTML from the SUMO site pasted in (to produce the site index content), but the forum-top and other top pages (I haven't explored yet to find them) will need either their content pasted in, or maybe the L and F textarea should contain logic to load menupages or something, for the various pages that need the content.

== Footer ==
The L and F bottom bar custom content feature is used for the footer content. This displays the "Switch Language" module floated right and a menupage module (calling page "moz4_footer_menus") floated left, followed by the "about" and "powered by" lines in a div.

<blockquote>Regarding: ''"Aside regarding module names - not about this project - I'm having problems with module names in trunk, maybe due to the work going on with them now. At my wamp install (SVN-upped), the module name menupage works, but at this site I get an error (as can be seen). So looks like one way or another this site should get updated."'' luci says:

Ideas:

*Fixed here. It has to be lowercase "menupage", not "Menupage".</blockquote>

The module names are pretty chaotic right now in trunk IMO and should be systematized some way, I think. I got the switch-language module to work in a module wikiplugin by using the name "switchlang", but there's no indication on the module admin page that this is the name to use (it's listed there as "Switch Language").

== Columns ==
Only the center and right columns are used. I made "Firefox Support" a normal user module and put it at the top of the right column (its top item still needs styling).

== Breadcrumbs ==
The SUMO site uses breadcrumbs, so I turned this feature on here. A problem is that our breacrumbs (neglected feature) only produces links, and these should be in a div, so this should be corrected in the breadcrumb.lib code, for better white space. Also a method is needed to not have the breadcrumbs appear on certain pages. If every page's body tag could be given a class or id similar to every module's div.box tag, then CSS could be used for this.

== HomePage page title ==
Not just about this site, but also needed for this site, I've long thought that there should be an admin option to turn off the display of the text "HomePage". Displaying that is fine on an info wiki, but looks very 1990s on most other types of web sites. There are workarounds, like using page descriptions for page titles, but there should be a direct admin solution IMO.

Similarly, refreshing the page by clicking on the page title should be an option IMO, similar to "double-click page to edit", etc.

== Reimplementing SUMO interface parts ==
The wiki action icons, etc., are in a visually distinct box, so this will need to be done.

Please give your input, of course. :-)

2009-09-24T07:20:47Z

MarcLaporte: /* James */ some notes about sumo_only

Support/TikiUpstreamTriage

2009-09-24T06:27:24Z

MarcLaporte:

== Who ==
*Marc Laporte
*David Tenser
*You?

== What ==

Goal:

Go trough [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&component=Forum&component=General&component=Knowledge+Base+Software&component=Localization&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= all modifications] and categorize them.

This will take some time as there is a [https://bugzilla.mozilla.org/report.cgi?x_axis_field=component&y_axis_field=product&z_axis_field=resolution&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= huge list].

Categories will be described below

* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_triage]''': A new bug that needs to be triaged by TikiWiki to determine the actual tiki status
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_fixed&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_fixed]''': Stuff that is already fixed in upstream TikiWiki (just need to check in the fix is OK for SUMO for performance, etc.)
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=sumo_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= sumo_triage]''': Should be looked at by SUMO, and determined if sumo_only or tiki_triage
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_string&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_string]''': Pure string changes -> Need to be added here: http://dev.tikiwiki.org/pending+text+corrections
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_template&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_template]''': UI changes in templates
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_feature&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_feature]''': New/enhanced feature that should be upstreamed
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_bug&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_bug]''': Bug that should also be fixed in upstream TikiWiki
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=sumo_only&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= sumo_only]''': Stuff that is related to the administration/maintenance of the SUMO website that can't really be upstreamed

== When ==
Starting 2009-08-26

*1st run: go through the whole list, categorize (tag) each item. Refine tag list as needed.
*2nd run for further discussion/analysis of the more tricky ones. (merge challenges, etc.)
**Link to relevant wishlist item on dev.tikiwiki.org or code

== Features / enhancements that should go to Tiki==

As we add things on this list, we'll only mark one "meta-bug" with tiki_feature. We won't necessarily identify each commit/patch, as the code will be taken in final stage and ported/adapted to Tiki trunk for inclusion/discussion/abstraction of code in 4.x. The individual bugs for that main feature will be marked as sumo_only.

Please add/link to any & all relevant information to facilitate upstreaming meta-bug, PRD wiki page, user documentation, blog post, and who is the contact person, [http://viewvc.svn.mozilla.org/vc/projects/sumo/ link to actual code], etc. For now, don't spend time too much time to create information, just link to it. The goal for now is to get a better picture of what each feature does and to identify people in the Tiki community to coordinate with.

===Performance===
http://dev.tikiwiki.org/Performance

====Replication support====
[https://bugzilla.mozilla.org/show_bug.cgi?id=433341 Move database load from master to slaves]

====Memcache support====
http://dev.tikiwiki.org/wish2707

====CSS and JavaScript minification====
http://dev.tikiwiki.org/wish2706

Stéphane Casset wrote [http://thread.gmane.org/gmane.comp.cms.tiki.devel/13690/ I am planning to add this, ie kind of retake what SUMO did but in a little different way... ]

===i18n===
Alain Désilets wrote: "Marta Stojanovic and I might be able to help with some of the i18n related features, as long as it leaves us with some time to work on the forward looking features (integration of Machine Translation in particular)."

====Content====
http://doc.tikiwiki.org/Translating+Tiki+content
http://wiki-translation.com

=====Track l10 changes=====
(ie noticing when translations are out of date)

===== l10n dashboard =====
http://dev.tikiwiki.org/wish2709

====Interface====
http://doc.tikiwiki.org/Translating+Tiki+interface
http://dev.tikiwiki.org/wish1771

===== Upstreaming translations =====
SUMO has about 25 totally new translations. Tiki strings should be added directly (easy)
For existing languages, a merging process should be established (strings have been improved in parallel in Tiki community).

===== Figure out a sustainable upstream model =====
How to distinguish SUMO only translations? (and efficiently maintain locally)
How to regularly upstream translations for Tiki strings?

Related:
http://dev.tikiwiki.org/pending+text+corrections

===Metrics & logs===

====Data warehouse and metrics dashboard====
[[Support/MetricsDashboardPRD]]

====CSAT (Customer Satisfaction)====
[[Support:CSAT]]

===Wiki===

==== Screencast support ====
http://dev.tikiwiki.org/wish2711

==== Showfor plugin ====
http://dev.tikiwiki.org/wish2710

==== Staging & Approval ====
Various enhancements in general and to work with translations
http://dev.tikiwiki.org/Staging
http://doc.tikiwiki.org/Staging

=== Forum enhancements ===
* Adding fields for Firefox version, bundled plugins, etc.
* Facilitate anonymous posting
* Screenshot upload
* Even newer enhancements, to permit search before post.
*[[Support/KBForum:PRD]]
*[[Support/ForumUX/PRD]]
*[[Support/ForumUX/PRD/New_Question_Form]]

=== Other ===
* Many small performance, l10n, and UX improvements; bugfixes; etc.
** Improvements to email watches (inc locale specific watches)
* Also see http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla
* A [http://dev.tikiwiki.org/Support_Mozilla_com SUMO category was created on Tiki Wishlist]. It includes things above and also things discussed or presumed to be of interest to SUMO.

== Features / enhancements that need to be maintained separately ==
Here, we'll try to abstract as much as possible, and make it easy to maintain.

=== In product help ===
Press F1, and access online documentation, with an alternate template.
ex.: http://support.mozilla.com/en-US/kb/Mouse+shortcuts?style_mode=inproduct

=== Rewrite Rules ===
SUMO has specific Rewrite Rules.

=== Theme ===
luci & Gary have volunteered to port SUMO theme to Tiki 4 and to help with make SUMO theme-related enhancements generic. Work has already started and they have questions: http://sumo.ourwiki.net/Notes

Who is/are theme person/people for SUMO?

=== Glueware to other apps ===

==== Search ====
Full text search using Sphinx (which should become an abstraction layer for Search)

==== Live chat ====
Live chat integration: [[Support/Live_Chat/Web_Client_PRD]]

== Related ==
[[Support/InterestingTikiLinks]]

== Phone Meeting 2009-09-02 ==
*Update on http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla
*Zend Framework use (cache, etc.)
*Introduce [[Support/InterestingTikiLinks]]
*Progress on triage list above
*Adding SUMO devs to Tiki security list and get access to the Security Dashboard
*Adding Tikidevs to Bugzilla
*From http://dev.tikiwiki.org/SUMO+Upstream+Process, "SUMO will continue on [http://viewvc.svn.mozilla.org/vc/projects/sumo/ own svn] but will create some way for tiki devs to see what happens will be figured out. (e.g. a hook to send commits to Tiki commit mailing list, or a hook to automatically send commits into a tikiwiki SVN branch)". Please have it sent to: tikiwiki-cvs@lists.sourceforge.net (and let marclaporte@tikiwiki.org know what the from email is so an exception is added to the spam filter.
*Copy of SUMO data for test drive on Tiki 4.x
** It would be a quick way to demonstrate new/changed features for evaluation by SUMO. (change is OK for us, or no, we'll want to adapt, etc.). -> http://sumo.ourwiki.net/

==How to help==
The most important thing is to review the items in [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_triage] and to change to sumo_triage, tiki_feature, tiki_fixed, etc. as described above. And to add notes/links to anything relevant (item on tiki wishlist, commit on Tiki SVN, discussion on mailing list, wiki page, etc.)

To help with triage, and watch the various items, you need to have an account on Bugzilla.

#Create an account here : https://bugzilla.mozilla.org/createaccount.cgi
#You can then watch stuff by going in your bugzilla email preferences add the email addresses listed here: https://bugzilla.mozilla.org/describecomponents.cgi?product=support.mozilla.com to your "watch list". You will receive a lot of email. So you may just want to watch selective items.
#Inform Marc, David or Gavin of your login, so you are given "editbug capabilities". This will permit you to change status: sumo_triage, sumo_only, tiki_fixed, etc.

Support/TikiUpstreamTriage

2009-09-24T06:22:06Z

MarcLaporte: /* Features / new section

== Who ==
*Marc Laporte
*David Tenser
*You?

== What ==

Goal:

Go trough [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&component=Forum&component=General&component=Knowledge+Base+Software&component=Localization&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= all modifications] and categorize them.

This will take some time as there is a [https://bugzilla.mozilla.org/report.cgi?x_axis_field=component&y_axis_field=product&z_axis_field=resolution&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= huge list].

Categories will be described below

* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_triage]''': A new bug that needs to be triaged by TikiWiki to determine the actual tiki status
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_fixed&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_fixed]''': Stuff that is already fixed in upstream TikiWiki (just need to check in the fix is OK for SUMO for performance, etc.)
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=sumo_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= sumo_triage]''': Should be looked at by SUMO, and determined if sumo_only or tiki_triage
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_string&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_string]''': Pure string changes -> Need to be added here: http://dev.tikiwiki.org/pending+text+corrections
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_template&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_template]''': UI changes in templates
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_feature&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_feature]''': New/enhanced feature that should be upstreamed
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_bug&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_bug]''': Bug that should also be fixed in upstream TikiWiki
* '''[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=sumo_only&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= sumo_only]''': Stuff that is related to the administration/maintenance of the SUMO website that can't really be upstreamed

== When ==
Starting 2009-08-26

*1st run: go through the whole list, categorize (tag) each item. Refine tag list as needed.
*2nd run for further discussion/analysis of the more tricky ones. (merge challenges, etc.)
**Link to relevant wishlist item on dev.tikiwiki.org or code

== Features / enhancements that should go to Tiki==

As we add things on this list, we'll only mark one "meta-bug" with tiki_feature. We won't necessarily identify each commit/patch, as the code will be taken in final stage and ported/adapted to Tiki trunk for inclusion/discussion/abstraction of code in 4.x. The individual bugs for that main feature will be marked as sumo_only.

Please add/link to any & all relevant information to facilitate upstreaming meta-bug, PRD wiki page, user documentation, blog post, and who is the contact person, [http://viewvc.svn.mozilla.org/vc/projects/sumo/ link to actual code], etc. For now, don't spend time too much time to create information, just link to it. The goal for now is to get a better picture of what each feature does and to identify people in the Tiki community to coordinate with.

===Performance===
http://dev.tikiwiki.org/Performance

====Replication support====
[https://bugzilla.mozilla.org/show_bug.cgi?id=433341 Move database load from master to slaves]

====Memcache support====
http://dev.tikiwiki.org/wish2707

====CSS and JavaScript minification====
http://dev.tikiwiki.org/wish2706

Stéphane Casset wrote [http://thread.gmane.org/gmane.comp.cms.tiki.devel/13690/ I am planning to add this, ie kind of retake what SUMO did but in a little different way... ]

===i18n===
Alain Désilets wrote: "Marta Stojanovic and I might be able to help with some of the i18n related features, as long as it leaves us with some time to work on the forward looking features (integration of Machine Translation in particular)."

====Content====
http://doc.tikiwiki.org/Translating+Tiki+content
http://wiki-translation.com

=====Track l10 changes=====
(ie noticing when translations are out of date)

===== l10n dashboard =====
http://dev.tikiwiki.org/wish2709

====Interface====
http://doc.tikiwiki.org/Translating+Tiki+interface
http://dev.tikiwiki.org/wish1771

===== Upstreaming translations =====
SUMO has about 25 totally new translations. Tiki strings should be added directly (easy)
For existing languages, a merging process should be established (strings have been improved in parallel in Tiki community).

===== Figure out a sustainable upstream model =====
How to distinguish SUMO only translations? (and efficiently maintain locally)
How to regularly upstream translations for Tiki strings?

Related:
http://dev.tikiwiki.org/pending+text+corrections

===Metrics & logs===

====Data warehouse and metrics dashboard====
[[Support/MetricsDashboardPRD]]

====CSAT (Customer Satisfaction)====
[[Support:CSAT]]

===Wiki===

==== Screencast support ====
http://dev.tikiwiki.org/wish2711

==== Showfor plugin ====
http://dev.tikiwiki.org/wish2710

==== Staging & Approval ====
Various enhancements in general and to work with translations
http://dev.tikiwiki.org/Staging
http://doc.tikiwiki.org/Staging

=== Forum enhancements ===
* Adding fields for Firefox version, bundled plugins, etc.
* Facilitate anonymous posting
* Screenshot upload
* Even newer enhancements, to permit search before post.
*[[Support/KBForum:PRD]]
*[[Support/ForumUX/PRD]]
*[[Support/ForumUX/PRD/New_Question_Form]]

=== Other ===
* Many small performance, l10n, and UX improvements; bugfixes; etc.
** Improvements to email watches (inc locale specific watches)
* Also see http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla
* A [http://dev.tikiwiki.org/Support_Mozilla_com SUMO category was created on Tiki Wishlist]. It includes things above and also things discussed or presumed to be of interest to SUMO.

== Features / enhancements that need to be maintained separately ==
Here, we'll try to abstract as much as possible, and make it easy to maintain.

=== Rewrite Rules ===
SUMO has specific Rewrite Rules.

=== Theme ===
luci & Gary have volunteered to port SUMO theme to Tiki 4 and to help with make SUMO theme-related enhancements generic. Work has already started and they have questions: http://sumo.ourwiki.net/Notes

Who is/are theme person/people for SUMO?

=== Glueware to other apps ===

==== Search ====
Full text search using Sphinx (which should become an abstraction layer for Search)

==== Live chat ====
Live chat integration: [[Support/Live_Chat/Web_Client_PRD]]

=== In product help ===

== Related ==
[[Support/InterestingTikiLinks]]

== Phone Meeting 2009-09-02 ==
*Update on http://dev.tikiwiki.org/Architecture+Suggestions+From+Mozilla
*Zend Framework use (cache, etc.)
*Introduce [[Support/InterestingTikiLinks]]
*Progress on triage list above
*Adding SUMO devs to Tiki security list and get access to the Security Dashboard
*Adding Tikidevs to Bugzilla
*From http://dev.tikiwiki.org/SUMO+Upstream+Process, "SUMO will continue on [http://viewvc.svn.mozilla.org/vc/projects/sumo/ own svn] but will create some way for tiki devs to see what happens will be figured out. (e.g. a hook to send commits to Tiki commit mailing list, or a hook to automatically send commits into a tikiwiki SVN branch)". Please have it sent to: tikiwiki-cvs@lists.sourceforge.net (and let marclaporte@tikiwiki.org know what the from email is so an exception is added to the spam filter.
*Copy of SUMO data for test drive on Tiki 4.x
** It would be a quick way to demonstrate new/changed features for evaluation by SUMO. (change is OK for us, or no, we'll want to adapt, etc.). -> http://sumo.ourwiki.net/

==How to help==
The most important thing is to review the items in [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=casesubstring&status_whiteboard=tiki_triage&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= tiki_triage] and to change to sumo_triage, tiki_feature, tiki_fixed, etc. as described above. And to add notes/links to anything relevant (item on tiki wishlist, commit on Tiki SVN, discussion on mailing list, wiki page, etc.)

To help with triage, and watch the various items, you need to have an account on Bugzilla.

#Create an account here : https://bugzilla.mozilla.org/createaccount.cgi
#You can then watch stuff by going in your bugzilla email preferences add the email addresses listed here: https://bugzilla.mozilla.org/describecomponents.cgi?product=support.mozilla.com to your "watch list". You will receive a lot of email. So you may just want to watch selective items.
#Inform Marc, David or Gavin of your login, so you are given "editbug capabilities". This will permit you to change status: sumo_triage, sumo_only, tiki_fixed, etc.

Support/BenefitsOfUpgradingToTiki4

2009-09-24T05:29:06Z

MarcLaporte: /* Volunteers */

Started : 2009-08-30

This page is to list examples about David's question: "How much better things will be once we’re there?"

== Being in sync with the Tiki community (quick access to answers) ==

Now, it's tricky for Tiki community members to help because it's difficult to remember how the code was two years ago.

We can say that a problem doesn't exist in Tiki3 or Tiki4, but it's very difficult to share which exact commit or combination of commits solved an issue. And it's possible (probable) that some bugs are caused by the current "FrankenTiki". Difficult to tell.

=== Volunteers ===

Several Tiki community members have volunteered.

Gary & luci are working on porting theme to Tiki4.

test site: Ex.: http://sumo.ourwiki.net/
Notes: [[Support/UpgradeToTiki4/ThemeCoordination]]

== Making Tiki stronger ==

By upgrading and upstreaming, Tiki becomes stronger and can get more done, which will be available to SUMO.

== PDO ==
Now default in 4.0

== Database Upgrade revamped ==
Now easy to manage local database configuration patches
http://dev.tikiwiki.org/Database+Schema+Upgrade

== Profiles ==
Profiles permit to store and share different configurations, feature sets, permissions schemes and pre-made examples of some of the more complicated features. Profiles was released in Tiki3.

=== For configuration change management ===
Similar to database patches above, they can be used for SUMO to make sure a configuration change on Staging is not forgotten on production.

Same thing for the various sites Fennec, Thunderbird, etc. It makes it easy to deply a config change everywhere.

=== Open Source Support profile ===
We can make a [http://profiles.tikiwiki.org/Support_Mozilla_com SUMO profile] which is an adaption of the [http://profiles.tikiwiki.org/Software_Project Software Project] profile.

Thus, attract more developers and accelerate development.

== Plugin Alias ==
http://doc.tikiwiki.org/Plugin+Alias

http://support.mozilla.com/en-US/kb/Style+Guide

So :
{TAG(tag=kbd)}text{TAG} becomes {KBD()}text{KBD}
{DIV(class=button,type=>span)}text{DIV} becomes {BUTTON()}text{BUTTON}

== Page alias ==
http://doc.tikiwiki.org/alias
This permits redirects without creating artificial pages.

So alternate titles/keywords can be used for better "findability".

== i18n ==
Massive improvements, over this period. Here are some that come to mind.

*Changing the language of a page is still possible, but somewhat hidden because it was causing User issues (users accidentally changing the language of the page, when trying to translate)
*Users can set all (1 to n) the languages they understand in their user preferences.
*[http://wiki-translation.com/tiki-download_wiki_attachment.php?attId=5 Architecture document (pdf)]
*[http://wiki-translation.com/tiki-download_file.php?fileId=4 Cross Lingual Wiki Engine Paper (pdf)]
*http://doc.tikiwiki.org/tiki-index.php?page=TikiWiki+4.0#Machine_Translation

== Plugin UI ==
There is a pop-up helper, started in Tiki3, better in Tiki4

== Theme system totally revamped ==
In version 3, whole theme organization was revamped. (Tableless, etc). The good news is that new themes are easier to make, more accessible, etc.

Site identity has also progressed (Site title, subtitle, footer, etc.) that make it easy to put things as part of site preferences.

The only negative point is that the old themes do not survive the upgrade
http://themes.tikiwiki.org/Theme+Issues+when+Updating+to+Tiki3.0

For SUMO, luci & Gary have volunteered to port the theme. You can see their progress here: http://sumo.ourwiki.net

=== Theme options ===
Useful to have small adaptations to a theme without duplicating the whole css.

== jQuery ==
jQuery has been added as optional javascript framework, which allows many nice effects on several parts of Tiki. It is an experimental, optional feature of Tiki 3.0, and in 4.0 it will be the default, always on Javascript framework.

http://doc.tikiwiki.org/jQuery

== Workspaces ==
Ease of making sub-sections within a single instance of Tiki and make it easier to share information. If Fennec and Firefox have a lot of documentation in common, it would be easier to share. So perhaps Fennec support site could be a workspace within SUMO. Fennec may or may not be the appropriate use of Workspaces, but it will be useful for sure. Ex.: a workspace for documentor, a workspace for localizers. And each wiki page can be shared amongst many workspaces.

Please see http://dev.tikiwiki.org/Workspace+Roadmap

== Text Area editor improvements ==
Collaboration on initiatives such as:
https://wiki.mozilla.org/Support/Editor:PRD
http://ui.tikiwiki.org/Text+area+editing+helper

== More stability ==
1.10 was never released. It was renamed 2.0 and then released. Before each release, there are hundreds of bug fixes and minor tweaks.

SUMO should rather stay in stable zone. For example, start using 4.1 and upgrading to 5.1

Once a release goes .0, all future commits are reviewed by our http://dev.tikiwiki.org/Quality+Team, with 3 of our most experienced developers. We would like to invite a SUMO developer to the quality team and this insure that there will be no regressions for SUMO (and thus making keeping in sync easier).

== Tons of new features ==
Surely there are many things that SUMO could use :-)

# http://doc.tikiwiki.org/Tiki2
# http://doc.tikiwiki.org/Tiki3
# http://doc.tikiwiki.org/Tiki4
# http://dev.tikiwiki.org/Roadmap

== Zend Framework ==
Starting in 3.0, Tiki bundles Zend Framework and uses some of it.

http://dev.tikiwiki.org/Zend+Framework

== Other changes ==
Perhaps use inclusion of wiki pages, instead of dynamic content (need to make sure they are excluded from search results)

Support/BenefitsOfUpgradingToTiki4

2009-09-24T05:26:24Z

MarcLaporte: /* Being in sync with the Tiki community */

Started : 2009-08-30

This page is to list examples about David's question: "How much better things will be once we’re there?"

== Being in sync with the Tiki community (quick access to answers) ==

Now, it's tricky for Tiki community members to help because it's difficult to remember how the code was two years ago.

We can say that a problem doesn't exist in Tiki3 or Tiki4, but it's very difficult to share which exact commit or combination of commits solved an issue. And it's possible (probable) that some bugs are caused by the current "FrankenTiki". Difficult to tell.

=== Volunteers ===

Several Tiki community members have volunteered. Ex.: http://sumo.ourwiki.net/

== Making Tiki stronger ==

By upgrading and upstreaming, Tiki becomes stronger and can get more done, which will be available to SUMO.

== PDO ==
Now default in 4.0

== Database Upgrade revamped ==
Now easy to manage local database configuration patches
http://dev.tikiwiki.org/Database+Schema+Upgrade

== Profiles ==
Profiles permit to store and share different configurations, feature sets, permissions schemes and pre-made examples of some of the more complicated features. Profiles was released in Tiki3.

=== For configuration change management ===
Similar to database patches above, they can be used for SUMO to make sure a configuration change on Staging is not forgotten on production.

Same thing for the various sites Fennec, Thunderbird, etc. It makes it easy to deply a config change everywhere.

=== Open Source Support profile ===
We can make a [http://profiles.tikiwiki.org/Support_Mozilla_com SUMO profile] which is an adaption of the [http://profiles.tikiwiki.org/Software_Project Software Project] profile.

Thus, attract more developers and accelerate development.

== Plugin Alias ==
http://doc.tikiwiki.org/Plugin+Alias

http://support.mozilla.com/en-US/kb/Style+Guide

So :
{TAG(tag=kbd)}text{TAG} becomes {KBD()}text{KBD}
{DIV(class=button,type=>span)}text{DIV} becomes {BUTTON()}text{BUTTON}

== Page alias ==
http://doc.tikiwiki.org/alias
This permits redirects without creating artificial pages.

So alternate titles/keywords can be used for better "findability".

== i18n ==
Massive improvements, over this period. Here are some that come to mind.

*Changing the language of a page is still possible, but somewhat hidden because it was causing User issues (users accidentally changing the language of the page, when trying to translate)
*Users can set all (1 to n) the languages they understand in their user preferences.
*[http://wiki-translation.com/tiki-download_wiki_attachment.php?attId=5 Architecture document (pdf)]
*[http://wiki-translation.com/tiki-download_file.php?fileId=4 Cross Lingual Wiki Engine Paper (pdf)]
*http://doc.tikiwiki.org/tiki-index.php?page=TikiWiki+4.0#Machine_Translation

== Plugin UI ==
There is a pop-up helper, started in Tiki3, better in Tiki4

== Theme system totally revamped ==
In version 3, whole theme organization was revamped. (Tableless, etc). The good news is that new themes are easier to make, more accessible, etc.

Site identity has also progressed (Site title, subtitle, footer, etc.) that make it easy to put things as part of site preferences.

The only negative point is that the old themes do not survive the upgrade
http://themes.tikiwiki.org/Theme+Issues+when+Updating+to+Tiki3.0

For SUMO, luci & Gary have volunteered to port the theme. You can see their progress here: http://sumo.ourwiki.net

=== Theme options ===
Useful to have small adaptations to a theme without duplicating the whole css.

== jQuery ==
jQuery has been added as optional javascript framework, which allows many nice effects on several parts of Tiki. It is an experimental, optional feature of Tiki 3.0, and in 4.0 it will be the default, always on Javascript framework.

http://doc.tikiwiki.org/jQuery

== Workspaces ==
Ease of making sub-sections within a single instance of Tiki and make it easier to share information. If Fennec and Firefox have a lot of documentation in common, it would be easier to share. So perhaps Fennec support site could be a workspace within SUMO. Fennec may or may not be the appropriate use of Workspaces, but it will be useful for sure. Ex.: a workspace for documentor, a workspace for localizers. And each wiki page can be shared amongst many workspaces.

Please see http://dev.tikiwiki.org/Workspace+Roadmap

== Text Area editor improvements ==
Collaboration on initiatives such as:
https://wiki.mozilla.org/Support/Editor:PRD
http://ui.tikiwiki.org/Text+area+editing+helper

== More stability ==
1.10 was never released. It was renamed 2.0 and then released. Before each release, there are hundreds of bug fixes and minor tweaks.

SUMO should rather stay in stable zone. For example, start using 4.1 and upgrading to 5.1

Once a release goes .0, all future commits are reviewed by our http://dev.tikiwiki.org/Quality+Team, with 3 of our most experienced developers. We would like to invite a SUMO developer to the quality team and this insure that there will be no regressions for SUMO (and thus making keeping in sync easier).

== Tons of new features ==
Surely there are many things that SUMO could use :-)

# http://doc.tikiwiki.org/Tiki2
# http://doc.tikiwiki.org/Tiki3
# http://doc.tikiwiki.org/Tiki4
# http://dev.tikiwiki.org/Roadmap

== Zend Framework ==
Starting in 3.0, Tiki bundles Zend Framework and uses some of it.

http://dev.tikiwiki.org/Zend+Framework

== Other changes ==
Perhaps use inclusion of wiki pages, instead of dynamic content (need to make sure they are excluded from search results)