Support/TikiUpstreamTriage: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(/* Features / new section)
No edit summary
Line 121: Line 121:
== Features / enhancements that need to be maintained separately ==
== Features / enhancements that need to be maintained separately ==
Here, we'll try to abstract as much as possible, and make it easy to maintain.
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 ===
=== Rewrite Rules ===
Line 138: Line 142:
Live chat integration: [[Support/Live_Chat/Web_Client_PRD]]
Live chat integration: [[Support/Live_Chat/Web_Client_PRD]]


=== In product help ===


== Related ==
== Related ==

Revision as of 06:27, 24 September 2009

Who

  • Marc Laporte
  • David Tenser
  • You?

What

Goal:

Go trough all modifications and categorize them.

This will take some time as there is a huge list.


Categories will be described below

  • tiki_triage: A new bug that needs to be triaged by TikiWiki to determine the actual tiki status
  • tiki_fixed: Stuff that is already fixed in upstream TikiWiki (just need to check in the fix is OK for SUMO for performance, etc.)
  • sumo_triage: Should be looked at by SUMO, and determined if sumo_only or tiki_triage
  • tiki_string: Pure string changes -> Need to be added here: http://dev.tikiwiki.org/pending+text+corrections
  • tiki_template: UI changes in templates
  • tiki_feature: New/enhanced feature that should be upstreamed
  • tiki_bug: Bug that should also be fixed in upstream TikiWiki
  • 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, 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

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 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

Other


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 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 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.

  1. Create an account here : https://bugzilla.mozilla.org/createaccount.cgi
  2. 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.
  3. 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.